Elastic Stack Kubernetes Helm Charts
These Helm charts are designed to be a lightweight way to configure Elastic official Docker images.
Warning
When it comes to running the Elastic on Kubernetes infrastructure, we
recommend Elastic Cloud on Kubernetes (ECK) as the best way to run and manage
the Elastic Stack.
ECK offers many operational benefits for both our basic-tier and our enterprise-tier customers, such as spinning up cluster nodes that were lost on failed infrastructure, seamless upgrades, rolling cluster changes, and much much more.
With the release of the Elastic Stack Helm charts for Elastic version 8.5.1, we are handing over the ongoing maintenance of our Elastic Stack Helm charts to the community and contributors. This repository will finally be archived after 6 months time. Elastic Stacks deployed on Kubernetes through Helm charts will still be fully supported under EOL limitations.
Since we want to provide an even better experience for our customers by running the Elastic Stack on Kubernetes, we will continue maintaining the Helm charts applicable to ECK Custom Resources. These charts can be found in the ECK repository.
Helm charts will currently be maintained for ECK Enterprise-tier customers, however, we encourage the community to engage with the existing Helm charts for the Elastic Stack and continue supporting their ongoing maintenance.
See #1731 for more details.
Supported Configurations
We recommend that the Helm chart version is aligned to the version of the product you want to deploy, when a chart release exists for the given stack version. This will ensure that you are using a chart version that has been tested against the corresponding production version. This will also ensure that the documentation and examples for the chart will work with the version of the product, you are installing.
For example, if you want to deploy an Elasticsearch 7.7.1 cluster, use the
corresponding 7.7.1 tag.
However, we don't expect to release new charts versions, so if a chart for the
latest patch version doesn't exist, you can use the latest chart with the same
MAJOR.MINOR version and override the Docker image tag to the latest patch
version with the imageTag value.
For example, if you want to deploy an Elasticsearch 7.17.5 cluster, use the
corresponding 7.17.3 tag, with imageTag=7.17.5 value.
Stack Versions
| Chart | Latest 8 Version | Latest 7 Version | Latest 6 Version |
|---|---|---|---|
| APM Server | 8.5.1 (Beta since 7.7.0) |
7.17.3 (Beta since 7.7.0) |
6.8.22 (Alpha) |
| Elasticsearch | 8.5.1 (GA since 7.7.0) |
7.17.3 (GA since 7.7.0) |
6.8.22 (Beta) |
| Filebeat | 8.5.1 (GA since 7.7.0) |
7.17.3 (GA since 7.7.0) |
6.8.22 (Beta) |
| Kibana | 8.5.1 (GA since 7.7.0) |
7.17.3 (GA since 7.7.0) |
6.8.22 (Beta) |
| Logstash | 8.5.1 (Beta since 7.5.0) |
7.17.3 (Beta since 7.5.0) |
6.8.22 (Beta) |
| Metricbeat | 8.5.1 (GA since 7.7.0) |
7.17.3 (GA since 7.7.0) |
6.8.22 (Beta) |
Kubernetes Versions
The charts are currently tested against all GKE versions available. The
exact versions are defined under KUBERNETES_VERSIONS in
helpers/matrix.yml.
Helm Versions
While we are checking backward compatibility, the charts are only tested with Helm version mentioned in helm-tester Dockerfile (currently 3.10.2).