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
The TLS section of the ingress is not configured unless a secretName is provided, however this is not always necessary. An NGINX ingress controller can have a default certificate configured using the default-ssl-certificate. In these cases the NGINX will always use the certificate configured here for TLS where this is not configured in the ingress.
The issue is here. The conditional setting should not use secretName only as a condition for enabling TLS in the ingress. It should also enable e.g. if tlsHost are set or maybe a new enableTLS flag.
The text was updated successfully, but these errors were encountered:
The TLS section of the ingress is not configured unless a
secretName
is provided, however this is not always necessary. An NGINX ingress controller can have a default certificate configured using thedefault-ssl-certificate
. In these cases the NGINX will always use the certificate configured here for TLS where this is not configured in the ingress.The issue is here. The conditional setting should not use
secretName
only as a condition for enabling TLS in the ingress. It should also enable e.g. iftlsHost
are set or maybe a newenableTLS
flag.The text was updated successfully, but these errors were encountered: