New and notableedit

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

Support for Elastic Agentedit

Elastic Agent provides a unified way to monitor logs, metrics, and other types of data from your Kubernetes infrastructure quickly and easily. You can use a single Elastic Agent deployment to replace multiple Beats deployments that were previously required to collect the different types of data you want to monitor. ECK 1.4.0 introduces experimental support for Elastic Agent in standalone mode as a technology preview.

Known issuesedit

On Kubernetes versions 1.16 or higher, if the operator is installed using Helm and if the validating webhook is enabled, you may be prevented from increasing the storage size of Elasticsearch volumeClaimTemplates even if the underlying storage class allows expansion. This is due to a change in how admissionregistration.k8s.io/v1 resources match update requests to validating webhook endpoints. You can work around this problem by patching the validating webhook as follows:

# If you installed using the Helm defaults, the name of the webhook would be elastic-operator.elastic-system.k8s.elastic.co
# If the operator name or namespace was changed during the installation, the name would reflect those changes.
WEBHOOK=$(kubectl get validatingwebhookconfiguration --no-headers -o custom-columns=NAME:.metadata.name | grep 'k8s.elastic.co')
kubectl patch validatingwebhookconfiguration "$WEBHOOK" \
    --patch='{"webhooks": [{"name": "elastic-es-validation-v1.k8s.elastic.co", "matchPolicy": "Exact"}, {"name": "elastic-es-validation-v1beta1.k8s.elastic.co", "matchPolicy": "Exact"}]}'