-
Notifications
You must be signed in to change notification settings - Fork 267
Impossible to request certificate when ingress for path / exists #197
Comments
This shouldn't be the case - the 'longer' (aka more precise) path should be chosen when routing. What ingress controller are you using? |
We are using the nginx ingress controller. Why do you think the longer path should be chosen? This issue indicates behaviour in the case of having multiple ingresses for the same host is not defined by the kubernetes docs. Merging usually works fine, in the case I described above however it can become problematic. |
I think the nginx ingresses get priority by name in this case. I worked around this by naming my ingress to something alphabetically later than kube-lego-.... |
I reported a possibly similar issue in the ingress project for the nginx controller, if you are using rewrite-target you might be affected by this: kubernetes/ingress-nginx#495 |
@fascinatedcow That did not work for me. Did the deployment name also follow kube-lego-...? Can someone please educate me on how to tell or configure GCE vs Nginx ingress controllers? |
I am experiencing the same issue. I have the following ingress for my web (
that overrides the one that
When I try to access I tried renaming my web's ingress so that alphabetically is before |
Hi everyone,
we just faced the issue that it is impossible to request certificates with
kube-lego
when another ingress for the path/
already exists. The/.well-known/acme
path in the ingress created bykube lego
is then not reachable. I know this is somewhat a limitation of kubernets-ingress, I was just curious if you guys consider this as a problem or not. In theory it might be possible forkube-lego
to detect such situations and temporarily reconfigure the colliding ingress.Regards,
Tobi
The text was updated successfully, but these errors were encountered: