1.9.0 release highlights
edit1.9.0 release highlights
editNew and notable
editNew and notable changes in version 1.9.0 of Elastic Cloud on Kubernetes. See Elastic Cloud on Kubernetes version 1.9.0 for the full list of changes.
VMware Tanzu Kubernetes Grid support
editECK 1.9.0 introduces official support for VMware Tanzu Kubernetes Grid starting with version 1.4.
Pod suspension for Elasticsearch troubleshooting
editSome debugging operations, like using the elasticsearch-node tool, require access to the Pod before the Elasticsearch process starts. Starting with ECK 1.9.0, this functionality is provided by the operator. Check the documentation for more details.
New and improved diagnostic tool
editTo provide more functionalities and better user experience we are moving away from script based diagnostic capture towards a dedicated binary. Check the ECK diagnostic tool repository for more details.
Elastic Cloud on Kubernetes moves to Elastic License v2
editFollowing the Elastic Stack licensing changes in 7.11.0, ECK 1.9.0 moves to Elastic License v2. For more details, check this blog post.
Known issues
edit-
On Openshift versions 4.6 and below, when installing or upgrading to 1.9.[0,1], the operator will be stuck in a state of
Installingwithin the Openshift UI, and found in aCrashLoopBackoffwithin Kubernetes because of Webhook certificate location mismatches. More information and work-around can be found in this issue. -
When using the
elasticsearchRefmechanism with Elastic Agent in version 7.17 and later its Pods will enter aCrashLoopBackoff. The issue will be fixed in ECK 2.0 for Elasticsearch versions 8.0 and above. A workaround is described in this issue.