-
Notifications
You must be signed in to change notification settings - Fork 8.1k
handle custom sni in bootstrap clusters #26684
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
Conversation
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
In response to a cherrypick label: new pull request created: #26685 |
@@ -138,7 +138,7 @@ func tlsContextConvert(tls *networkingAPI.ClientTLSSettings, sniName string, met | |||
// No TLS. | |||
return nil | |||
} | |||
if len(sniName) > 0 { | |||
if len(tls.Sni) == 0 && tls.Mode == networkingAPI.ClientTLSSettings_ISTIO_MUTUAL { |
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.
why do we not set SNI for mutual or simple?
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.
for ISTIO_MUTUAL we default it to "tracer" , "envoy_metrics_service" if tls.Sni
is not specified - that was the existing behaviour.
For Simple and Mutual we set it only if it is specified in TLS settings (because we do not know what to default to).
Are you suggesting we should not default for ISTIO_MUTUAL as well and only set if user sets it?
The TLS SNI check was in handled in correctly in PR #25070 for bootstrap clusters. This PR fixes it.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.