# Issues with ECK and pvc-autoresizer

**URL:** <https://discuss.elastic.co/t/issues-with-eck-and-pvc-autoresizer/386804>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [June 10, 2026, 4:32pm UTC](https://discuss.elastic.co/t/issues-with-eck-and-pvc-autoresizer/386804 "2026-06-10T16:32:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sahendrikse](https://avatars.discourse-cdn.com/v4/letter/s/c0e974/32.png) [@sahendrikse](https://discuss.elastic.co/u/sahendrikse)\
**Post date:** [June 10, 2026, 4:32pm UTC](https://discuss.elastic.co/t/issues-with-eck-and-pvc-autoresizer/386804/1 "2026-06-10T16:32:35Z")

</div>

Hi all,

We're currently working with both ECK and pvc-autoresizer in our deployment, where our pvc-resizer annotations are defined with the volumeClaimTemplate as:

```auto
annotations = {
  "resize.topolvm.io/threshold" = "25%"
  "resize.topolvm.io/increase" = "10%"
  "resize.topolvm.io/storage_limit" = "1000Gi"
}

```

This deployed succesfully and worked as intended. Soon as we're reaching close to the storage\_limit set, we looked to increase the storage\_limit to 2000Gi. When applying this, we were met with the error:

```auto
 Error: API response status: Failure
│ 
│ with kubernetes_manifest.elasticsearch,
│ on elasticsearch.tf line 149, in resource "kubernetes_manifest" "elasticsearch":
│ 149: resource "kubernetes_manifest" "elasticsearch" {
│ 
│ admission webhook "elastic-es-validation-v1.k8s.elastic.co" denied the
│ request: Elasticsearch.elasticsearch.k8s.elastic.co "elasticsearch"
│ is invalid: spec.nodeSet[0].volumeClaimTemplates: Invalid value:
│ [{"metadata":{"name":"elasticsearch-data","annotations":{"resize.topolvm.io/increase":"10%","resize.topolvm.io/storage_limit":"2000Gi","resize.topolvm.io/threshold":"25%"}},"spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"256Gi"}},"storageClassName":"elasticsearch-es-storage-class"},"status":{}}]:
│ volume claim templates can only have their storage requests increased, if
│ the storage class allows volume expansion. Any other change is forbidden

```

Has anyone succesfully managed both ECK and pvc-autoresizer together? We'd prefer this way than manually increasing the resource request to 2TB, as the incremental (smaller) increases are more cost effective for us.

Thanks.