# Unknown field \\"spec.nodeSets\[0\].volumeClaimTemplates\[0\]

**URL:** <https://discuss.elastic.co/t/unknown-field-spec-nodesets-0-volumeclaimtemplates-0/381119>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 18, 2025, 6:46pm UTC](https://discuss.elastic.co/t/unknown-field-spec-nodesets-0-volumeclaimtemplates-0/381119 "2025-08-18T18:46:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DanielR1](https://avatars.discourse-cdn.com/v4/letter/d/54ee81/32.png) [@DanielR1](https://discuss.elastic.co/u/DanielR1)\
**Post date:** [August 18, 2025, 6:46pm UTC](https://discuss.elastic.co/t/unknown-field-spec-nodesets-0-volumeclaimtemplates-0/381119/1 "2025-08-18T18:46:37Z")

</div>

Hello!

I have deployed using Argo the eck-operator v 3.1 in a k8s cluster

```auto
    - repoURL: https://helm.elastic.co
      chart: eck-operator
      targetRevision: 3.1.0
      helm:
        skipCrds: false

```

Before that we had 2.16.1 operator version. I keep getting these infos

```auto
{"log.level":"info","@timestamp":"2025-08-18T18:22:47.741Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.http.service.metadata.creationTimestamp\""
{"log.level":"info","@timestamp":"2025-08-18T18:22:47.741Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].metadata.creationTimestamp\"","service.version":"3.1
{"log.level":"info","@timestamp":"2025-08-18T18:22:47.741Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].status\""
{"log.level":"info","@timestamp":"2025-08-18T18:22:47.741Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].metadata.creationTimestamp\""
{"log.level":"info","@timestamp":"2025-08-18T18:22:47.741Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].status\""

```

I’ve tried to clean up the CR by deleting the last applied configuration and the creationTimestamp fields, and I even deleted the crd which also deletes the cr and I’ve recreated the cluster thinking that the crd was not upgraded when I did upgrade the operator (the uptime on the crd was like 5 months and on the operator much less since its been just upgraded), but this did not help  
On a cluster where I did not upgrade the operator there are no such errors  
Why would that keep poping up and how can I get rid of these?  
I think the cluster works fine even with this info warnings, but I am afraid that in a future operator upgrade I could get in trouble because of these crd fields

Thank you!

---

<div class="post-metadata">

**Author:** ![DanielR1](https://avatars.discourse-cdn.com/v4/letter/d/54ee81/32.png) [@DanielR1](https://discuss.elastic.co/u/DanielR1)\
**Post date:** [August 19, 2025, 12:59pm UTC](https://discuss.elastic.co/t/unknown-field-spec-nodesets-0-volumeclaimtemplates-0/381119/2 "2025-08-19T12:59:48Z")

</div>

Did a bit more checking, and this is only happening on version 3.0.0 and 3.1.0, doesnt occur on 2.16.1 . Not sure but I assume those fields are added anyways when I deploy the cluster with helm upgrade, so could this could be a known issue with the operator after 3.x?