-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: allow TLS to be disabled for gateways #1030
Open
willswire
wants to merge
5
commits into
main
Choose a base branch
from
optional-tls-istio
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+662
−1
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
willswire
force-pushed
the
optional-tls-istio
branch
2 times, most recently
from
November 20, 2024 21:55
a310342
to
0fb3183
Compare
willswire
changed the title
allow TLS as optional for gateways
allow TLS to be disabled for gateways
Nov 20, 2024
willswire
changed the title
allow TLS to be disabled for gateways
feat: allow TLS to be disabled for gateways
Nov 20, 2024
willswire
force-pushed
the
optional-tls-istio
branch
from
November 20, 2024 22:03
0fb3183
to
e4f274d
Compare
mjnagel
reviewed
Nov 20, 2024
willswire
commented
Nov 21, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implemented TLS configuration validation via a Helm chart hook.
willswire
force-pushed
the
optional-tls-istio
branch
from
November 21, 2024 16:15
d491e05
to
6295e19
Compare
mjnagel
requested changes
Nov 21, 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.
Description
When deploying UDS Core Base to EKS, we can use annotations to populate certificates from Amazon’s AWS Certificate Manager (ACM) on the ELBs provisioned by Istio (see here and here).
Unfortunately, this does not work if an entry in the Gateway's
servers
spec containstls
-- likely a result of the conflicting certs provided for*.uds.dev
.By exposing the option of enabling/disable TLS via a variable, we can opt to disable it, and therefore enable annotation-based cert management.
Type of change
Checklist before merging