-
Notifications
You must be signed in to change notification settings - Fork 830
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
Istio Ambient support #2676
Projects
Comments
What are the components that need to change for this? Would the profile controller need to create waypoint proxies for each user's namespace? |
Waypoint proxies are automatically created when the Gateway resource gets created (so is a bit simpler than crafting deployments/services). You can configure it in such a way that there's 1 instance per namespace that handles all L7 traffic for that namespace. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Istio Ambient mode is a different deployment model from the “traditional” (sidecar) mode of Istio. The ambient mode (sidecar-less) doesn’t require injecting sidecars into the deployments.
Here are the high-level differences between the two modes:
The concerns handled by the sidecar proxy in the sidecar Istio are split into two components in Istio ambient:
Ztunnel (handles L4 concerns, mTLS, authorization policies without any HTTP)
Waypoint proxy (handles L7 concerns, i.e. traffic splitting, matching, header manipulation, etc., more or less everything that gets defined in the VirtualService)
Ingress gateway isn’t installed by default anymore when using profile=ambient
Kubernetes Gateway API is used for ingress (and waypoint proxy) deployments
Any L7 VirtualServices or AuthorizationPolicies must have a “targetRef” section that specifies which waypoint proxy handles the L7 configuration
Waypoint proxies
Any VirtualService or AuthorizationPolicy that uses HTTP concepts will require a waypoint proxy. Given that there are 3 namespaces (that I identified so far), I’d suggest a per-namespace deployment of a waypoint proxy.
In addition to the waypoint proxy, the resources will have to be updated to use the waypoint proxies:
Work items
Migrate to Kubernetes Gateway API
Move to the latest Istio (Ambient will be beta in the next release (1.22))
Move to Ambient mode
Identify components that need waypoint proxy
Deploy waypoint proxies
Switch the Istio profile from default → ambient (or have an option of doing one or the other) - since Ambient will still be Beta, we shouldn’t make it a default option
The text was updated successfully, but these errors were encountered: