This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« 2.1.0 release highlights 1.9.1 release highlights »
Elastic Docs ›Elastic Cloud on Kubernetes [master] ›Release highlights

2.0.0 release highlights

edit

2.0.0 release highlights

edit

New and notable

edit

New and notable changes in version 2.0.0 of Elastic Cloud on Kubernetes. See Elastic Cloud on Kubernetes version 2.0.0 for the full list of changes.

Removal of legacy v1beta1 Custom Resource Definitions

edit

ECK 2.0.0 removes support for legacy versions of Kubernetes and no longer ships with a v1beta1 version of its custom resource definitions. ECK can therefore no longer be installed in versions of Kubernetes <1.16. Please note however that the lowest supported version according to the ECK support policy is 1.19.

Improved support for topology aware Elasticsearch clusters

edit

Starting with ECK 2.0 the operator can make Kubernetes Node labels available as Pod annotations. This can be used to make information, such as logical failure domains, available in a running Pod. Combined with Elasticsearch shard allocation awareness and Kubernetes topology spread constraints, this makes it much easier than before to create availability zone-aware Elasticsearch clusters.

Smoother cluster operations using node lifecycle APIs

edit

When orchestrating Elasticsearch version 7.15.2 or later ECK will use the new node lifecycle APIs to orchestrate rolling upgrades and scale downs to make Elasticsearch aware of impending temporary or permanent shutdown of nodes.

Known issues

edit
  • When using the Red Hat certified version of the operator, automatic upgrades from previous versions of ECK do not work. To upgrade uninstall the old ECK operator and install the new version manually. Because CRDs remain in place after uninstalling, this operation should not negatively affect existing Elastic Stack deployments managed by ECK.
  • When using the elasticsearchRef mechanism with Elastic Agent in version 7.17 its Pods will enter a CrashLoopBackoff. A workaround is described in this issue.
  • Under certain circumstances the operator will keep terminating and restarting Elasticsearch Pods seemingly at random. The underlying issue is fixed in ECK 2.4.0 and an upgrade is highly recommended.
« 2.1.0 release highlights 1.9.1 release highlights »