You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for submitting the bug. This will not affect configurations in Kong, and you can still use this ingress. We will fix it in #3719, which is expected to be included in KIC 2.9.
Is there an existing issue for this?
Current Behavior
Ingresses don't get an IP, when
spec.tls[].secretName
is missing.No apparent error is logged regarding this.
But when spec.tls[].secretName is defined, the ingress get an IP assigned.
Expected Behavior
Ingresses do not require
spec.tls[].secretName
to be defined.Prior to 2.8.x, it was possible to use the default certificate by defining following to Kong (tested in 2.7.0)
And then we didn't need to define
spec.tls[].secretName
in all ingresses.Steps To Reproduce
spec.tls[].hosts[] = host
, like:spec.tls[].secretName = secretName
, likeKong Ingress Controller version
Kubernetes version
1.24
Anything else?
No response
The text was updated successfully, but these errors were encountered: