# Elastic Search, not able to modify the settings

**URL:** <https://discuss.elastic.co/t/elastic-search-not-able-to-modify-the-settings/265129>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 22, 2021, 10:19pm UTC](https://discuss.elastic.co/t/elastic-search-not-able-to-modify-the-settings/265129 "2021-02-22T22:19:22Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![charith-elastic](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@charith-elastic](https://discuss.elastic.co/u/charith-elastic)\
**Post date:** [February 25, 2021, 7:48am UTC](https://discuss.elastic.co/t/elastic-search-not-able-to-modify-the-settings/265129/5 "2021-02-25T07:48:16Z")

</div>

1.16.15 looks like your Kubernetes version. Assuming you installed ECK using the Helm chart and you are running ECK 1.4.0 (you can check this by running `helm list --all-namespaces | grep eck-operator`) you could be running into a known issue with the validating webhook.

If the above assumptions are correct (ECK 1.4.0 installed using Helm), you can try patching the validating webhook as follows before retrying the volume expansion operation.

```auto
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"}]}'

```

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-not-able-to-modify-the-settings/265129)._