You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just upgraded from Helm chart version 100.2402.0 to 100.2406.1. After the upgrade, I noticed that Argo CD still had a diff between desired state and live state, and it never goes away:
In the new CRD TridentConfigurator, there is a list additionalPrinterColumns where objects may set the field priority. Some elements in the list has priority: 0 according to the CRD applied by the Helm chart:
It seems like they get modified, I'm guessing by the Trident operator, so the priority field gets removed if its value is 0. This causes a constant diff in tools like Argo CD. In the particular case of Argo CD, it is possible to ignore changes to certain object attributes, but I think this diff is probably unintentional and should be fixed.
Environment
Provide accurate information about the environment to help us reproduce the issue.
Trident version: 24.06.1
Trident installation flags used: helm template --include-crds trident -n trident trident/trident-operator --set 'tridentLogFormat=json' --version 100.2406.1 (this is similar to what Argo CD with Kustomize executes in my case)
Container runtime: containerd
Kubernetes version: 1.28.11
Kubernetes orchestrator: Rancher v2.8.5
Kubernetes enabled feature gates: default for RKE2.
OS: RHEL 9.2
NetApp backend types: ONTAP NAS
Other: null
To Reproduce
Install the Helm chart version 100.2406.1
kubectl get crd TridentConfigurator -o yaml and see that priority: 0 is unset.
Expected behavior
There should be no diff after apply.
Additional context
If I sync Argo CD so the priority field gets set, the trident-operator produces this log: trident-operator.log
The text was updated successfully, but these errors were encountered:
Describe the bug
I just upgraded from Helm chart version 100.2402.0 to 100.2406.1. After the upgrade, I noticed that Argo CD still had a diff between desired state and live state, and it never goes away:
In the new CRD
TridentConfigurator
, there is a listadditionalPrinterColumns
where objects may set the fieldpriority
. Some elements in the list haspriority: 0
according to the CRD applied by the Helm chart:trident/helm/trident-operator/crds/tridentconfigurators.yaml
Lines 17 to 42 in 722e7ef
It seems like they get modified, I'm guessing by the Trident operator, so the
priority
field gets removed if its value is0
. This causes a constant diff in tools like Argo CD. In the particular case of Argo CD, it is possible to ignore changes to certain object attributes, but I think this diff is probably unintentional and should be fixed.Environment
Provide accurate information about the environment to help us reproduce the issue.
helm template --include-crds trident -n trident trident/trident-operator --set 'tridentLogFormat=json' --version 100.2406.1
(this is similar to what Argo CD with Kustomize executes in my case)To Reproduce
kubectl get crd TridentConfigurator -o yaml
and see thatpriority: 0
is unset.Expected behavior
There should be no diff after apply.
Additional context
If I sync Argo CD so the
priority
field gets set, thetrident-operator
produces this log: trident-operator.logThe text was updated successfully, but these errors were encountered: