Installing with own ingress and cert-manager only requests a single certificate - documentation issue?
I just installed gitlab via helm to a cluster that has nginx-ingress and cert-manager already set up.
The first problem I ran into is #615 (closed), but after using helm fetch and removing the offending line from NOTES.txt, the whole thing installed.
What I noticed is that minio, the first service to be up and running, got a certificate from letsencrypt just fine. The other 2 services with ingress; gitlab-unicorn and gitlab-registry, did not.
The reason for this, as far as I can see, is that all 3 ingresses were deployed with the following setting;
tls.secretName: gitlab-wildcard-tls
The documentation states that the default value for global.ingress.tls.secretName is none and the default values for the various secretNames is some unique default value. I was able to circumvent this problem by actually setting the service-specific secretName values in my values.yaml to the suggested defaults. The documentation on this subject is clearly wrong and might need updating.