-
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
Add ztunnel/cni components to Istio #1033
Comments
#699 includes a draft of this work, although not all images are the correct versions or flavors at this point. |
This may require working #1027 |
Got the base ztunnel/cni components wired in and tested locally, going to do the same tests for injection and ambient packages on k3s, rke2, and eks to make sure we're not breaking anything |
Ran into this bug when testing out Istio CNI on k3s:
Fix is merged but waiting on new release of istio with the fix in it. |
Waiting for the new Istio release to test out on k3s, in the meantime considering what it would take to have 2 functional layers for Base, one with Ambient and one with Sidecar. This could potentially be least disruptive but could also be difficult to make all the layers compatible with both istio deployments and be more maintenance. Investigating what that looks like. |
Figuring out how to do L7 routing with Waypoints. Need the following:
|
Related to #681
In order to incrementally work towards ambient mesh we should add the ztunnel and cni components to our istio setup. Ideally these should all be on v1.24.0 (when ambient was GA-ed). Definition of done here:
The scope of this issue does not require any workloads to be switched to ambient, or any support of ambient in the operator - but if those changes are necessary/helpful to validate ztunnel functionality they can be worked here.
The text was updated successfully, but these errors were encountered: