logstash.k8s.elastic.co/v1alpha1
editlogstash.k8s.elastic.co/v1alpha1
editPackage v1alpha1 contains API Schema definitions for the logstash v1alpha1 API group
Resource Types
ElasticsearchCluster
editElasticsearchCluster is a named reference to an Elasticsearch cluster which can be used in a Logstash pipeline.
Field | Description |
---|---|
|
|
|
ClusterName is an alias for the cluster to be used to refer to the Elasticsearch cluster in Logstash configuration files, and will be used to identify "named clusters" in Logstash |
Logstash
editLogstash is the Schema for the logstashes API
Field | Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
|
|
LogstashService
editField | Description |
---|---|
|
|
|
Service defines the template for the associated Kubernetes Service object. |
|
TLS defines options for configuring TLS for HTTP. |
LogstashSpec
editLogstashSpec defines the desired state of Logstash
Field | Description |
---|---|
|
Version of the Logstash. |
|
|
|
Image is the Logstash Docker image to deploy. Version and Type have to match the Logstash in the image. |
|
ElasticsearchRefs are references to Elasticsearch clusters running in the same Kubernetes cluster. |
|
Config holds the Logstash configuration. At most one of [ |
|
ConfigRef contains a reference to an existing Kubernetes Secret holding the Logstash configuration. Logstash settings must be specified as yaml, under a single "logstash.yml" entry. At most one of [ |
|
Pipelines holds the Logstash Pipelines. At most one of [ |
|
PipelinesRef contains a reference to an existing Kubernetes Secret holding the Logstash Pipelines. Logstash pipelines must be specified as yaml, under a single "pipelines.yml" entry. At most one of [ |
|
Services contains details of services that Logstash should expose - similar to the HTTP layer configuration for the rest of the stack, but also applicable for more use cases than the metrics API, as logstash may need to be opened up for other services: Beats, TCP, UDP, etc, inputs. |
|
Monitoring enables you to collect and ship log and monitoring data of this Logstash. Metricbeat and Filebeat are deployed in the same Pod as sidecars and each one sends data to one or two different Elasticsearch monitoring clusters running in the same Kubernetes cluster. |
|
PodTemplate provides customisation options for the Logstash pods. |
|
RevisionHistoryLimit is the number of revisions to retain to allow rollback in the underlying StatefulSet. |
|
SecureSettings is a list of references to Kubernetes Secrets containing sensitive configuration options for the Logstash. Secrets data can be then referenced in the Logstash config using the Secret’s keys or as specified in |
|
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. |
|
VolumeClaimTemplates is a list of persistent volume claims to be used by each Pod. Every claim in this list must have a matching volumeMount in one of the containers defined in the PodTemplate. Items defined here take precedence over any default claims added by the operator with the same name. |
LogstashStatus
editLogstashStatus defines the observed state of Logstash
Field | Description |
---|---|
|
Version of the stack resource currently running. During version upgrades, multiple versions may run in parallel: this value specifies the lowest version currently running. |
|
|
|
|
|
ObservedGeneration is the most recent generation observed for this Logstash instance. It corresponds to the metadata generation, which is updated on mutation by the API Server. If the generation observed in status diverges from the generation in metadata, the Logstash controller has not yet processed the changes contained in the Logstash specification. |
|