While trying to use kube-lego with an ingress class different than nginx and gce, I was not able to retrieve certificates from Let's Encrypt, even though the class was considered as supported.
Kube-Lego was simply skipping the ingress resources due to the ingress class name not matching the kube-lego provider name.
To fix that I replaced the provider and class name matching with the ingress class settings checks (Ingress.Ignore() method), ignoring only the ingress resources that do not match the supported class names and applying the valid resources to every registered provider.
I'm also submitting #194 that enables customizing the desired providers, to avoid any weird cases that may appear by applying the same ingress resources on both providers.
While trying to use kube-lego with an ingress class different than
nginx
andgce
, I was not able to retrieve certificates from Let's Encrypt, even though the class was considered as supported. Kube-Lego was simply skipping the ingress resources due to the ingress class name not matching the kube-lego provider name.To fix that I replaced the provider and class name matching with the ingress class settings checks (
Ingress.Ignore()
method), ignoring only the ingress resources that do not match the supported class names and applying the valid resources to every registered provider.I'm also submitting #194 that enables customizing the desired providers, to avoid any weird cases that may appear by applying the same ingress resources on both providers.
Related to #189