ArgoCD installation results in "Failed to unmarshal "values.yaml": <nil>" about ingress-nginx

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/remove-kind bug

Please attempt an install with helm and report status

/triage needs-information

[avilesj]

Direct helm installation works.

[longwuyuan]

• ok thanks for that update
• that means we need data on what is wrong with the controller or the values file and its integration with ArgoCD
• the project ci does not test installation with ArgoCD.
• there are many users who deployed with ArgoCD so wait and see if a change in chart v4.10 is causing this for others too

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[D1StrX]

Minio tenant of the Minio Operator is also a perfect example of a Helm values.yaml that Argocd cannot parse. The issue in this one are all the 'exotic' tokens (e.g: `__ and ###) https://github.com/minio/operator/blob/master/helm/tenant/values.yaml

[longwuyuan]

@D1StrX thanks for the update.

With this info, I guess we can be certain that the problem is parsing.

The project maintains the chart for helm usage and no problem is detected on helm usage.

Since the fields containing tokens or extraArgs or raw yaml work with helm and seem to break when ArgoCD parses it, I think its better to approach the ArgoCD developers for comments. I don't think there are resources available on this project to test and debug ArgoCD integration for parsers/parsing values file content.

[D1StrX]

Minio tenant of the Minio Operator is also a perfect example of a Helm values.yaml that Argocd cannot parse. The issue in this one are all the 'exotic' tokens (e.g: `__ and ###) https://github.com/minio/operator/blob/master/helm/tenant/values.yaml

Was able to narrow it down to the KES config part in the Minio tenant values.yaml.
So, my suggestion would be; Try stripping down the values.yaml for your nginx Helm deployment and then push it to Git to let ArgoCD apply the changes.

I also tried the apps-of-apps pattern for the Kubernetes-nginx controllers, and I'm not experiencing any issues at all. I'm using the default values.yaml file with basic value changes in the default keys.