Open polonel opened 6 years ago
I'm having similar issues when supplying custom ingress classes, works fine when not specifying default ingress class, supported ingress class and provider
I was having the same issue, and after much code trawling I finally found an annotation that's used to specify the ingress provider: "kubernetes.io/ingress.provider"
..which led me to: https://github.com/jetstack/kube-lego/issues/189#issuecomment-313139616
I added that annotation (with value "nginx" ) to my nginx ingress, and it started working. I haven't tried multiple ingress classes yet
Environment Tectonic Cluster 1.7.3-tectonic.3 Kubernetes 1.7.3+tectonic.3
When deploying Kube-Lego using
helm
with therbac.create=true
flag; I can see that the deployment is created and the role, role bindings, and service accounts are created with the create permissions.However the kube-lego pod never seems to create the required service or update the ingresses. Thus filling the kube-lego with...
The
helm
command used to deploy kube-lego is as follows:I'm not sure if I'm over looking something, as there is not much information on getting this to work with a tectonic cluster. Any insight?