New and notableedit
New and notable changes in version 2.2.0 of Elastic Cloud on Kubernetes. Check Elastic Cloud on Kubernetes version 2.2.0 for the full list of changes.
Associations with external Elastic Stack componentsedit
ECK offers a convenient way to associate Elastic Stack resources together, but it requires them to be all managed by ECK in the same Kubernetes cluster. ECK 2.2.0 makes it possible to associate with external Elastic resources not managed by ECK using a custom Secret containing the connection information to this external resource.
For example, you can now use an Elastic Cloud Elasticsearch cluster to monitor Elasticsearch clusters and Kibana instances managed by ECK by combining Stack Monitoring and this new feature.
spec: monitoring: metrics: elasticsearchRefs: - secretName: external-cloud-es-monitoring-ref --- apiVersion: v1 kind: Secret metadata: name: external-cloud-es-monitoring-ref stringData: url: https://monitoring.es.abc-0.xyz.com:1234 username: monitoring-user password: REDACTED
ERU report and calculationedit
To avoid some confusion, the Enterprise Resource Units (ERU) are reported in raw bytes and in Gibibyte (GiB) instead of Gigabyte (GB). The ERU calculation has been aligned so that 1 ERU equals to 64 GiB.
Service Accounts for Kibana and Fleet Serveredit
ECK supports Service Accounts to secure the connection between Kibana or Fleet Server and Elasticsearch.
Elasticsearch Self Stack Monitoringedit
The Stack Monitoring feature is fully operational to be used for Elasticsearch self-monitoring.
- The migration to service account tokens can lead to unavailability of Kibana and Fleet Server which is especially noticeable on larger Elasticsearch clusters with many nodes. ECK 2.3 enables a migration without downtime. It is recommended to upgrade to ECK 2.3 to avoid this issue or to quickly restore availability on already affected installations. More details can be found in the linked GitHub 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.