Unable to deploy with no self signed certs
Summary
While deploying in a new namespace, pods are waiting for the wildcard self signed cert secret which is not generated.
There has been an update on the condition to create the self signed cert job but the condition for mounting the secret stayed the same.
Steps to reproduce
Deploy in a new namespace with a configuration that does not define global.ingress.tls
but does define gitlab.webservice.ingress.tls.secretName
(same with another component)
Configuration used
global:
ingress:
enabled: true
configureCertmanager: false
gitlab:
webservice:
ingress:
enabled: true
tls:
secretName: gitlab-ingress-tls
certmanager:
install: false
nginx-ingress:
enabled: false
Current behavior
The wildcard self signed cert is mounted on pods but not created by the self signed cert job.
Expected behavior
The wildcard self signed cert should not be mounted on pods.
Versions
- Chart: 6.11.9
- Platform:
- Self-hosted: Rancher RKE
- Kubernetes: (
kubectl version
)- Client: 1.25
- Server: 1.24
- Helm: (
helm version
)- Client: v3.11.2