Guest post originally published on Istio’s blog by John Howard and Lin Sun
Istio ambient service mesh was launched in Sept 2022 in an experimental branch, introducing a new data plane mode for Istio without sidecars. Through collaboration with the Istio community, across Google, Solo.io, Microsoft, Intel, Aviatrix, Huawei, IBM and others, we are excited to announce that Istio ambient mesh has graduated from the experimental branch and merged to Istio’s main branch! This is a significant milestone for ambient mesh, paving the way for releasing ambient in Istio 1.18 and installing it by default in Istio’s future releases.
Major Changes from the Initial Launch
Ambient mesh is designed for simplified operations, broader application compatibility, and reduced infrastructure cost. The ultimate goal of ambient is to be transparent to your applications and we have made a few changes to make the ztunnel and waypoint components simpler and lightweight.
- The ztunnel component has been rewritten from the ground up to be fast, secure, and lightweight. Refer to Introducing Rust-Based Ztunnel for Istio Ambient Service Mesh for more information.
- We made significant changes to simplify waypoint proxy’s configuration to improve its debuggability and performance. We’ll cover this in a future blog soon.
- Added the
istioctl x waypointcommand to help you conveniently deploy waypoint proxies, along with
istioctl pc workloadto help you view workload information.
- We gave users the ability to explicitly bind Istio policies such as AuthorizationPolicy to waypoint proxies vs selecting the destination workload.
Follow our getting started guide to try the ambient pre-alpha build today. We’d love to hear from you! To learn more about ambient: