Charts: [stable/nginx-ingress] configmap name bug

[mumubin]

• install cmd:

helm install stable/nginx-ingress --tiller-namespace cdp-qa --namespace cdp-qa -n ingress-cdp-qa

• log

I1003 02:29:03.205342       6 main.go:227] Running in Kubernetes cluster version v1.15 (v1.15.0) - git (clean) commit e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529 - platform linux/amd64
I1003 02:29:03.210056       6 main.go:91] Validated cdp-qa/ingress-cdp-qa-nginx-ingress-default-backend as the default backend.
I1003 02:29:03.618958       6 main.go:102] Created fake certificate with PemFileName: /etc/ingress-controller/ssl/default-fake-certificate.pem
W1003 02:29:03.684855       6 store.go:616] Unexpected error reading configuration configmap: configmaps "ingress-cdp-qa-nginx-ingress-controller" not found

• query configmap

~ ᐅ kubectl get configmap -n cdp-qa
NAME                              DATA   AGE
ingress-cdp-qa.v1                 1      4m21s
ingress-controller-leader-nginx   0      4m14s

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.

[bodom0015]

Was this ever addressed? I just ran into this same problem, which required manually editing the deployment to resolve.

Deployment YAML included the following:

  containers:
  - args:
    - /nginx-ingress-controller
    - --default-backend-service=support/support-nginx-ingress-default-backend
    - --election-id=ingress-controller-leader
    - --ingress-class=nginx
    - --configmap=support/support-nginx-ingress-controller

but the ConfigMap was actually supposed to be named:

$ kubectl get cm -n support
NAME                                      DATA   AGE
ingress-controller-leader-nginx           4      21m

This points to some problem in the logic of the templates named nginx-ingress.controller.fullname or nginx-ingress.fullname.

Relevant versions:

• Kubernetes: v1.14.2
• Chart version: nginx-ingress-1.26.1
• NGINX Ingress Controller version: 0.26.1

[rquackenbush]

I'm seeing the same thing in version 1.28.2 of the chart (helm version 3.0.0):

helm install building-clarity-api-ingress stable/nginx-ingress `
    --namespace building-clarity `
    --set controller.replicaCount=2 `
    --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux `
    --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux `
    --set controller.service.loadBalancerIP="XXX.XXX.XXX.XXX" `
    --set controller.ingressClass="nginx-building-clarity-api" 

W0113 17:03:00.382853       7 store.go:635] Unexpected error reading configuration configmap: configmaps "building-clarity-api-ingress-nginx-ingress-controller" not found

kubectl get cm --namespace building-clarity
NAME                                                   DATA   AGE
ingress-controller-leader-nginx                        0      3d2h
ingress-controller-leader-nginx-building-clarity-api   0      64m

[palko444]

I supose issue is with configMap creation, for me its working when some option is added, e.g.

# Will add custom configuration options to Nginx https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
  config:
    client-header-buffer-size: 1k