InfluxDB Clustered 3 - appinstances.kubecfg.dev CRD inclusion of empty arrays causes ArgoCD to behave as if the CRD is out of sync

In the appinstances.kubecfg.dev CRD there are three empty arrays, at lines 8, 11, and 15. When using ArgoCD to install InfluxDB Clustered 3, the CRD is always considered out of sync because the applied CRD will not have the empty arrays.

This makes InfluxDB 3 seem misconfigured or out of sync with it's gitops codebase.

Inspect the appinstances.kubecfg.dev CRD in the InfluxDB Clustered 3 chart, focusing on the empty arrays at lines 8, 11, and 15. Compare the rendered CRD with the CRD applied by Kubernetes during an ArgoCD installation. Done means the rendered resource omits those empty arrays and ArgoCD no longer reports the CRD as out of sync.

Written by the indexing model from the issue text.