-
Notifications
You must be signed in to change notification settings - Fork 24
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
Conversation
a310342
to
0fb3183
Compare
0fb3183
to
e4f274d
Compare
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.
d491e05
to
6295e19
Compare
@willswire just to check on this one - I think we determined that we would close this out due to some of the complexity/issues with non-tls traffic in the loop here? |
Yep! We're good to close this one out. |
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