Update your deployment

You can add and modify most elements of the original Kubernetes cluster specification provided that they translate to valid transformations of the underlying Kubernetes resources (for example existing volume claims cannot be downsized). The ECK operator will attempt to apply your changes with minimal disruption to the existing cluster. You should ensure that the Kubernetes cluster has sufficient resources to accommodate the changes (extra storage space, sufficient memory and CPU resources to temporarily spin up new pods, and so on).

For example, you can grow the cluster to three Elasticsearch nodes from the deployed Elasticsearch cluster example by updating the count with apply:

cat <<EOF | kubectl apply -f -
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: quickstart
spec:
  version: 8.16.0
  nodeSets:
  - name: default
    count: 3
    config:
      node.store.allow_mmap: false
EOF

ECK will automatically schedule the requested update. Changes can be monitored with the ECK operator logs, events, and applicable product’s pod logs. These will either report successful application of changes or provide context for further troubleshooting. Kindly note, Kubernetes restricts some changes, for example refer to Updating Volume Claims.

This completes our quickstart guide for deploying an Elasticsearch cluster and Kibana instance with our ECK operator. We recommend continuing to Orchestrating Elastic Stack applications for more configuration options