1.3.0 release highlights

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

ECK 1.3.0 introduces an official Helm chart for deploying the operator. This provides a more flexible way of installing the operator customized to the environment and the desired use case. Existing installations can be easily migrated to Helm as well.

Elasticsearch volumes can be now dynamically expanded. A single edit to the resource YAML manifest is enough to grow the volumes. In many cases (dependent on the underlying storage provider), this can be done without even restarting the pod and so expansions complete in seconds.

Elasticsearch can be configured to be aware of the underlying Kubernetes node it is running on, and use this knowledge when deciding where to place replica shards. This prevents an issue with a single Kubernetes node from affecting both primary and replica shards. In previous ECK releases, this behavior required additional configuration by the user. With ECK 1.3.0, this configuration is the default.

With changes around how IP addresses are handled, ECK is now compatible with IPv6-only Kubernetes environments.

To enable ECK becoming Red Hat OpenShift Certified Operator, ECK image is now based on Universal Base Image - ubi-minimal. For customers using ECK on Openshift, we now have a certified operator on OperatorHub.

All supported resources can have their init containers modified. Starting with ECK 1.3.0, modifications to built-in init containers will be merged with the defaults.