-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS only configured if secretName is set #81
Comments
dozer75
pushed a commit
to dozer75/idsvr-helm
that referenced
this issue
Oct 30, 2024
To be able to add TLS to an ingress without having a secret (which is a fully valid option see curityio#81 for reasoning) this change adds the tlsEnabled flag, which will handle the TLS configuration correct. If the tlsEnabled is set to false, the legacy TLS logic applies.
dozer75
added a commit
to dozer75/idsvr-helm
that referenced
this issue
Oct 30, 2024
To be able to add TLS to an ingress without having a secret (which is a fully valid option see curityio#81 for reasoning) this change adds the tlsEnabled flag, which will handle the TLS configuration correct. If the tlsEnabled is set to false, the legacy TLS logic applies.
Added a PR for this today as it blocks our usage of the helm chart... |
Closed by #88 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: