Beat is the Schema for the Beats API.
5 top-level fields · unchanged since eck-operator 1.2.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
BeatSpec defines the desired state of a Beat.
Config holds the Beat configuration. At most one of [`Config`, `ConfigRef`] can be specified.
ConfigRef contains a reference to an existing Kubernetes Secret holding the Beat configuration. Beat settings must be specified as yaml, under a single "beat.yml" entry. At most one of [`Config`, `ConfigRef`] can be specified.
SecretName is the name of the secret.
DaemonSet specifies the Beat should be deployed as a DaemonSet, and allows providing its spec. Cannot be used along with `deployment`. If both are absent a default for the Type is used.
Deployment specifies the Beat should be deployed as a Deployment, and allows providing its spec. Cannot be used along with `daemonSet`. If both are absent a default for the Type is used.
ElasticsearchRef is a reference to an Elasticsearch cluster running in the same Kubernetes cluster.
Name of the Kubernetes object.
Namespace of the Kubernetes object. If empty, defaults to the current namespace.
Image is the Beat Docker image to deploy. Version and Type have to match the Beat in the image.
KibanaRef is a reference to a Kibana instance running in the same Kubernetes cluster. It allows automatic setup of dashboards and visualizations.
Name of the Kubernetes object.
Namespace of the Kubernetes object. If empty, defaults to the current namespace.
SecureSettings is a list of references to Kubernetes Secrets containing sensitive configuration options for the Beat. Secrets data can be then referenced in the Beat config using the Secret's keys or as specified in `Entries` field of each SecureSetting.
Entries define how to project each key-value pair in the secret to filesystem paths. If not defined, all keys will be projected to similarly named paths in the filesystem. If defined, only the specified keys will be projected to the corresponding paths.
Key is the key contained in the secret.
Path is the relative file path to map the key to. Path must not be an absolute file path and must not contain any ".." components.
SecretName is the name of the secret.
ServiceAccountName is used to check access from the current resource to Elasticsearch resource in a different namespace. Can only be used if ECK is enforcing RBAC on references.
Type is the type of the Beat to deploy (filebeat, metricbeat, heartbeat, auditbeat, journalbeat, packetbeat, etc.). Any string can be used, but well-known types will have the image field defaulted and have the appropriate Elasticsearch roles created automatically. It also allows for dashboard setup when combined with a `KibanaRef`.
Version of the Beat.
BeatStatus defines the observed state of a Beat.
AssociationStatus is the status of an association resource.
AssociationStatus is the status of an association resource.
Source: all-crds.yaml
Changes to Beat (beat.k8s.elastic.co/v1beta1) in each eck-operator version, compared to the version before it.
Beat was first seen on this version of eck-operator
Released · View Beat in 1.2.0
No examples of Beat yet. Contribute one on GitHub.
kubespec.dev