Add tlsEnabled flag for ingress TLS handling #88
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
anestos
approved these changes
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To be able to add TLS to an ingress without having a secret (which is a fully valid option see #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.