1.7.0 release highlights

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

Starting with this release, the CustomResourceDefinitions (CRD) and the ValidatingWebhookConfiguration resources are available in version v1. The resources definitions and the operator are now provided in two separate files, the all-in-one.yaml file is no longer available. Check the installation guide or the upgrade notes for more information.

In this release, the Elasticsearch and Kibana resources have been enhanced to let you specify a reference to a monitoring cluster. When specified, sidecar containers are automatically setup by ECK to ship logs and metrics to the referenced Elasticsearch cluster. Refer to the Stack Monitoring documentation for more details.

The /scale subresource is now enabled for Kibana, Enterprise Search, Elastic Maps Server, and APM Server. The number of replicas for these resources can be managed automatically by the Horizontal Pod Autoscaler (HPA).

In this release, the Agent CRD has been enhanced to introduce support for Fleet mode and Fleet Server. The agents configuration can be managed from Kibana, while an agent can be run in server mode to update policies across a fleet of Elastic Agents.

After installing ECK 1.7.0 on Kubernetes versions 1.16/1.17 using Helm or the YAML manifests, deploying Elasticsearch may fail with the following error:

error: SchemaError(co.elastic.k8s.elasticsearch.v1.Elasticsearch.spec.nodeSets.volumeClaimTemplates): array should have exactly one sub-item

This is due to a validation issue in kubectl that has been addressed in the Kubernetes API server as of versions 1.18.13, 1.19.5 and 1.20. To work around this issue patch the Elasticsearch CRD as follows:

kubectl patch crd elasticsearches.elasticsearch.k8s.elastic.co --type json -p='[{"op": "remove", "path": "/spec/versions/0/schema/openAPIV3Schema/properties/spec/properties/nodeSets/items/properties/volumeClaimTemplates/x-kubernetes-preserve-unknown-fields"}]'

More details about the issue and available workarounds are documented in this bug report.