Install ECK

ECK

Elastic Cloud on Kubernetes (ECK) is a Kubernetes operator that helps you deploy and manage Elastic applications on Kubernetes, including Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash.

ECK relies on a set of Custom Resource Definitions (CRDs) to define how applications are deployed. CRDs are global resources, shared across the entire Kubernetes cluster, so installing them requires specific permissions.

ECK can be installed in two modes, depending on the namespaces the operator is allowed to manage:

Cluster-wide installation: Allows the operator to orchestrate applications in all namespaces of the Kubernetes cluster. This is the default installation method.
Namespace-restricted installation: Limited to specific, pre-defined namespaces. Use the namespaces configuration flag to limit the namespaces in which the operator is allowed to work.

Note

You can install multiple instances of ECK in the same Kubernetes cluster, but only if the CRDs are compatible across all operator instances (e.g., by ensuring they run the same version). If running multiple instances, you must also disable cluster-wide features like the validating webhook.

Warning

Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators.

For a list of supported Kubernetes versions refer to Elastic Cloud on Kubernetes > Supported versions

Installation methods

ECK supports multiple installation methods. Choose the one that best fits your infrastructure:

For air-gapped environments, refer to Air gapped install to understand the requirements and installation considerations.

Refer to Required RBAC permissions for a complete list of the permissions needed by the operator.

Note

To upgrade ECK, refer to Upgrade Elastic Cloud on Kubernetes.