# ECK Statefulset currentRevision not updated

**URL:** <https://discuss.elastic.co/t/eck-statefulset-currentrevision-not-updated/263155>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 3, 2021, 5:29pm UTC](https://discuss.elastic.co/t/eck-statefulset-currentrevision-not-updated/263155 "2021-02-03T17:29:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Apen-Sadler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simon_apen-sadler/32/83301_2.png) [@Simon\_Apen-Sadler](https://discuss.elastic.co/u/Simon_Apen-Sadler)\
**Post date:** [February 3, 2021, 5:29pm UTC](https://discuss.elastic.co/t/eck-statefulset-currentrevision-not-updated/263155/1 "2021-02-03T17:29:46Z")

</div>

I'm currently using [a prometheus statefulset down rule](https://awesome-prometheus-alerts.grep.to/rules.html#rule-kubernetes-12) to monitor our statefulsets and have noticed the alert is firing incorrectly for the elasticsearch statefulsets managed by ECK. It seems to be caused by updates. The [statefulset currentRevision is not being updated because the OnDelete updateStrategy is used](https://github.com/kubernetes/kube-state-metrics/issues/1324#issuecomment-765404006), which causes kube-state-metrics to return the wrong result.

Should the ECK operator update the current revision of its statefulsets once it has restarted all pods within it?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:23am UTC](https://discuss.elastic.co/t/eck-statefulset-currentrevision-not-updated/263155/2 "2022-11-04T08:23:16Z")

</div>