Helm GlobalConfiguration Argument

[Seneti42]

I'm a bit confused as to how the global configuration argument is being set by the Helm chart templates and would appreciate someone explaining to me how it works or if I'm doing something wrong.

When setting controller.globalConfiguration.create to true, the template creates a globalConfiguration custom resource with the contents of the controller.globalConfiguration.spec. The globalConfiguration resource it creates is named using the nginx-ingress.fullname value:

controller-globalconfiguration.yaml template

However when the argument -global-congfiguration is set during the deployment of the controller to tell the controller which globalConfiguration resource to use, it is using nginx-ingress.name:

controller-deployment.yaml template

When I then run the helm to deploy the controller with a globalConfiguration the argument is telling the controller to look for a globalConfiguration resource name that doesn't exist:

Helm created deployment

Helm created globalConfiguration

Apologies in advance I'm relatively new to Kubernetes and Helm, but is this by design, am I doing something wrong or is there an issue with the templates?

Thanks for your help.

[github-actions]

Hi @Seneti42 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!

[haywoodsh]

Hi @Seneti42, thank you for bringing in to our attention. I'm working on testing and confirming the behaviour you have reported. I will keep you updated once I have new information on this.

[haywoodsh]

I can confirm that there is currently a mismatch between the value in the command line argument generated by the helm chart and the name of the actual GlobalConfiguration created.

As a temporary fix, if you are using deployment, you can try to edit this line https://github.com/nginxinc/kubernetes-ingress/blob/v3.1.0/deployments/helm-chart/templates/controller-deployment.yaml#L256 from
- -global-configuration=$(POD_NAMESPACE)/{{ include "nginx-ingress.name" . }} to - -global-configuration=$(POD_NAMESPACE)/{{ include "nginx-ingress.fullname" . }};
before deploying it, following the documentation on installing using chart sources

We are currently looking at how to address this issue and will provide a fix soon.