[Bug]: Some CRDs need preserveUnknownFields: false

[D1StrX]

Version

edge

What Kubernetes platforms are you running on?

Other

Steps to reproduce

Deploying Nginx Inc. controller with ArgoCD shows on some CRDs OutOfSync. ArgoCD wants to add preserveUnknownFields: false on these CRDs:

• apdoslogconfs.appprotectdos.f5.com
• apdospolicies.appprotectdos.f5.com
• aplogconfs.appprotect.f5.com
• appolicies.appprotect.f5.com
• apusersigs.appprotect.f5.com

I think adding preserveUnknownFields: false could resolve this, as described in kubernetes docs?

[github-actions]

Hi @D1StrX thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[pdabelf5]

Hi @D1StrX the preserveUnknownFields appears to be set to false already in https://github.com/nginx/kubernetes-ingress/blob/main/deploy/crds-nap-waf.yaml

[D1StrX]

That's weird, ArgoCD still says it wants to add it.

[pdabelf5]

Okay, when the CRD is applied Kubernetes must trim this field as when I get the CRD back the field is missing

kubectl get crd appolicies.appprotect.f5.com -o json | jq .spec.preserveUnknownFields
null

[danielnginx]

@mkingst should we investigate this case further?

[AlexFenlon]

Hi @D1StrX ,

Is this issue resolved?

[D1StrX]

I still see preserveUnknownFields: false after the latest update

[D1StrX]

@AlexFenlon I just see that Nginx.org and Kubernetes Ingress got mixed. I have to create an issue in the other repo.

Details can be found in: nginx/nginx-ingress-helm-operator#595