🛠️Istio 1.31 Ditches Google Cloud for AWS
Istio is leaving Google Cloud for AWS, and you need to migrate
TL;DR
Istio 1.31 moves its infrastructure from Google Cloud to AWS, requiring teams to migrate before the October 13 outage test. Agentgateway, a Rust data plane, is now a Layer 7 waypoint proxy.
Istio 1.31 marks a significant shift as it moves its entire infrastructure from Google Cloud to AWS, impacting teams using gcr.io/istio-release, registry.istio.io, or the Google-hosted Helm repository. You need to migrate before the next outage test on October 13. This release also introduces agentgateway, a Rust data plane, as a Layer 7 waypoint proxy, enhancing protocol handling and traffic management. Istio 1.31 supports Kubernetes 1.32 to 1.36 and includes security fixes and new features like zone-aware load balancing and improved compliance settings.
Key Points
Istio 1.31 was released on August 31, supporting Kubernetes 1.32 to 1.36.
Teams must migrate from Google Cloud to AWS before the October 13 outage test.
Agentgateway, a Rust data plane, handles protocols like Model Context Protocol and ordinary HTTP.
Istio 1.31 includes security fixes and corrects ALLOW_ANY_DYNAMIC_DNS forwarding in IPv6-only clusters.
New zoneAwareLbSetting field on DestinationRule and MeshConfig lets Envoy route to endpoints in the downstream proxy's availability zone.
Why It Matters
If you're running Istio on Kubernetes, the move from Google Cloud to AWS means you need to migrate your infrastructure before the October 13 outage test. Agentgateway, a Rust data plane, introduces new features like Layer 7 waypoint proxy capabilities, enhancing traffic management and protocol handling. This impacts teams using gcr.io/istio-release, registry.istio.io, or the Google-hosted Helm repository.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,567 builders reading daily.