When providing an ArgoCD Application for deploying a Helm chart, I also specify overriding values with spec.source.helm.parameters. But when the name of the parameter extends 70 chars it transforms into a block scaler.
Normally this would not be a direct issue, but it actually does for a specific one:
Providing an annotation for a Service of type LoadBalancer for deploying an Azure internal loadbalancer. It expect to see the following annotation before deploying the Azure internal loadbalancer:
Describe the bug
When providing an ArgoCD Application for deploying a Helm chart, I also specify overriding values with
spec.source.helm.parameters
. But when thename
of the parameterextends 70 chars
it transforms into a block scaler. Normally this would not be a direct issue, but it actually does for a specific one: Providing an annotation for aService
of typeLoadBalancer
for deploying an Azure internal loadbalancer. It expect to see the following annotation before deploying the Azure internal loadbalancer:Because of the transformation to a block scaler the end result in the live manifest for the service will be:
And this will not trigger the deployment of an Azure internal loadbalancer, which will cause the deployment to fail.
To Reproduce
Deploy the following ArgoCD application
Expected behavior
I expect to get the following end result in the live manifest:
But the actual end result in the live manifest is: