ECK Operator 3.0/3.1 - unknown field \"spec.http.service.metadata.creationTimestamp\"

[danielrinzis]

Hello! I have noticed on the logs for the ECK operator v3.1.0 these kind of info messages:
"log.level":"info","@timestamp":"2025-08-19T21:05:59.149Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.http.service.metadata.creationTimestamp\"","service.version":"3.1.0+9fc9bb06","service.type":"eck","ecs.version":"1.4.0" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.149Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].metadata.creationTimestamp\"","service.version":"3.1.0+9fc9bb06" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.149Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].status\"","service.version":"3.1.0+9fc9bb06" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.150Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].metadata.creationTimestamp\"","service.version":"3.1.0+9fc9bb06" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.150Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].status\"","service.version":"3.1.0+9fc9bb06" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.150Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.podDisruptionBudget.metadata.creationTimestamp\"","service.version":"3.1.0+9fc9bb06" {"log.level":"info","@timestamp":"2025-08-19T21:05:59.150Z","log.logger":"manager.eck-operator","message":"unknown field \"spec.transport.service.metadata.creationTimestamp\"","service.version":"3.1.0+9fc9bb06"

For the v3.0.0 version I have noticed in the logs similarly:
{"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.http.service.metadata.creationTimestamp\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].metadata.creationTimestamp\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.nodeSets[0].volumeClaimTemplates[0].status\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].metadata.creationTimestamp\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.nodeSets[1].volumeClaimTemplates[0].status\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.podDisruptionBudget.metadata.creationTimestamp\"","service.version":"3.0.0+89a41511" {"log.level":"info","@timestamp":"2025-08-19T12:00:24.763Z","log.logger":"KubeAPIWarningLogger","message":"unknown field \"spec.transport.service.metadata.creationTimestamp\"","service.version":"3.0.0+89a41511"

For the operator v2.16.1 there are no such info messages

The Elasticsearch version is 8.17.3 and the cluster is deployed using helm install/upgrade
The reconciliation seems to work without a problem, also the operator seems to work fine, I can add/remove nodes without issues in the cluster

Is this messages a reason for concerns? From what I understand these fields are not recognized by the operator and these fields are added to the CR when using the helm upgrade

Even tried to clean up the fields from the CR and reapply it and reinstall the CRDs but did not help

Thank you