Missing values in CRDs interferes with ArgoCD sync

[pierluigilenoci]

To explain this issue better, I'll give you an example.

The CRD of chaosengines.litmuschaos.io (for example) is missing everywhere allowEmptyValue: false, and ArgoCD goes in constant reconciliations. Could you please add this value explicitly to the CRDs?

Ref: argoproj/argo-cd#16757

[pierluigilenoci]

@Jonsy13 @ispeakc0de @jongwooo, could you please take a look?

[younsl]

Hi, folks. Is there anything in progress?

litmus-core 3.18.0 chart is always showing OutOfSync in ArgoCD for me. This happens because two settings (chaosengines.litmuschaos.io and chaosexperiments.litmuschaos.io) don't have allowEmptyValue: false. Because this is missing, ArgoCD keeps trying to sync them over and over. Even adding ServerSideApply=true to the ArgoCD Application's sync settings didn't fix it.

This diff should be fixed because the people running the cluster might think there's a real problem if they always see the "OutOfSync" message.

[pierluigilenoci]

[pierluigilenoci]

@Jonsy13 @ispeakc0de I've submitted PR #481 to fix this.

The root cause is that allowEmptyValue is not a valid OpenAPI v3 JSON Schema field for Kubernetes CRDs. The API server strips it on apply, causing ArgoCD to see a perpetual diff → OutOfSync.

The fix removes all allowEmptyValue: false occurrences across all 6 affected charts (7 files). The existing minLength: 1 constraints already provide the same validation.

cc @younsl

[younsl]

@pierluigilenoci Thanks for the fix!