-
Notifications
You must be signed in to change notification settings - Fork 338
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
Rethink building SNI for multizone MeshService #10469
Comments
xref #10918 |
@jakubdyszkiewicz does this cover the implem of MADR-59? |
yes, it's basically implem of https://github.com/kumahq/kuma/blob/master/docs/madr/decisions/059-sni-in-the-resource.md |
Do we agree that we decided to not do splits? |
Also we agree that the format is agreed on and this change would be just to remove the zone CP to "make up" the format for remote access to services? In other words this is an improvement but there wouldn't be a breaking change in implementing this (just if the SNI is in the MeshService object use this instead) |
Yes, we do not do splits anymore |
The code for computing the SNI is in: kuma/pkg/core/resources/apis/meshservice/api/v1alpha1/helpers.go Lines 74 to 95 in 4d8c12d
|
Description
The current way is a bit hacky
#10451 (comment)
While it works, we should consider something more robust.
Options that come to my mind:
xref #10435
The text was updated successfully, but these errors were encountered: