kube-lego
kube-lego copied to clipboard
kube-lego-nginx ingress ends up in wrong namespace
- I have pretty much the example deployment, version 0.1.3
- Recently I noticed that I had two ingresses called kube-lego-nginx.
- One of them (a old one) in the kube-lego namespace
- Another new one in the default namespace. This one's age indicates it appeared on the same day I upgraded to 0.1.3.
- The result was a) "duplicate routes" warnings by the nginx ingress controller and b) the cert validation failing, because the wrong route took effect, and it was pointing to a kube-lego service that didn't exist in the default namespace.
My deployment file, like in the example, used to say:
- name: LEGO_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
I changed it to point to "kube-lego" explicitly. That fixed it.
I am having the same issue but I cannot find out why. The pod is configured correctly (the same as in the GCE example) but the metadata.namespace and the status.podIP are not being picked up on.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to jetstack.
/lifecycle stale