[BUG] Extra fields in CRDs trigger OutOfSync on ArgoCD

[SkalaNetworks]

Kube-OVN Version

v1.13-v1.14

Kubernetes Version

1.31

Operation-system/Kernel Version

/

Description

ArgoCD shows a desync between the LiveManifest and the desired manifest.

The VPC NAT GW CRD has a bunch of fields like this in the properties:

 x-kubernetes-patch-merge-key: key
 x-kubernetes-patch-strategy: merge

Is there a reason for the presence of these fields? They don't seem to exist in CR definitions anymore (at least in my version of K8S)

Steps To Reproduce

1. Deploy Kube-OVN using Helm/ArgoCD
2. Witness the desync on VPC NAT GWs

Current Behavior

Out of Sync on VPC NAT GWs CRDs

Expected Behavior

Synced VPC NAT GWs CRDs

[dosubot]

The x-kubernetes-patch-merge-key and x-kubernetes-patch-strategy annotations in the Kube-OVN CRDs are used to define how Kubernetes should handle strategic merge patches. These annotations are typically used to specify how lists should be merged when applying patches, which is particularly useful for managing complex configurations in Kubernetes.

In the Kube-OVN project, these fields are indeed present in the VPC NAT Gateway CRDs, specifically under properties like matchExpressions in the podAffinity, podAntiAffinity, and nodeAffinity sections ^[1].

The issue you're encountering with ArgoCD showing a desync might be due to differences in how these annotations are handled or expected between different versions of Kubernetes or ArgoCD. If these fields are not present in your version of Kubernetes CRD definitions, it could be causing the discrepancy.

To resolve this, you might consider:

1. Verifying if your Kubernetes version supports these annotations. If not, you may need to adjust the CRDs to align with your Kubernetes version's expectations.
2. Checking if there are any updates or patches in the Kube-OVN repository that address compatibility with Kubernetes 1.31 or ArgoCD, as this might be a known issue that has been resolved in newer versions or patches.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[github-actions]

Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.