2.14.0 release highlights

Users who have defined a custom readiness probe for Elasticsearch 8.2.0 or later will have to either remove the custom readiness probe before upgrading to 2.14 or if that is not possible have adjust the readiness probe script as follows after the upgrade:

podTemplate:
  spec:
    containers:
    - name: elasticsearch
      readinessProbe:
         exec:
           command:
           - bash
           - -c
           - /mnt/elastic-internal/scripts/readiness-port-script.sh

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

Starting with ECK 2.14.0 it becomes possible to fully delegate the transport certificate management for Elasticsearch to a third party component. When used in conjunction with the cert-manager operator and its CSI driver it also improves the scalability of node sets. Refer to the Issue node transport certificates with third-party tools for a complete example.

The Elasticsearch containers are now configured to use the Elasticsearch TCP readiness port. This change also improves cluster upgrade stability by fixing a bug in the upgrade process.

The ECK operator can now detect when a remote service is deployed in Elastic Cloud Serverless. This allows the use of the Connect to external Elastic resources feature to connect a ECK managed resource to your serverless project.