Draft: fix: use kubernetes.io/ingress.class when present
It is possible to have an up-to-date cluster, but an outdated ingress controller. This means that the API networking.k8s.io/v1/Ingress is available, but no valid ingressClassName exists in the cluster.
This proposes to
- make
ingress.className
optional - use only the
kubernetes.io/ingress.class
annotation when it is present (skippingingressClassName
) - otherwise, set either the annotation or
ingressClassName
, depending on the cluster's capabilities, usingingress.className | default "nginx" | quote
See #206 (closed)
Edited by Hordur Freyr Yngvason