Agent Sandbox on GKE is generally available and runs on any supported GKE

## Feature Feature Agent Sandbox on GKE is generally available and runs on any supported GKE version. Agent Sandbox on GKE is optimized for running isolated, stateful, single-replica workloads, such as AI agents, at no additional cost. You can install Agent Sandbox on GKE by using the[open source Agent Sandbox installation](https://github.com/kubernetes-sigs/agent-sandbox/#standard-install-core--extensions). For more information, see[About Agent Sandbox on GKE](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/machine-learning/agent-sandbox)and [Install Agent Sandbox on GKE](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/how-install-agent-sandbox). ## Feature Feature Agent Gateway for GKE is now available in Preview in the Rapid channel on clusters running GKE version 1.37.2-gke.1042000 or later. Agent Gateway provides a centralized management layer to control traffic flowing to, from, and between your agents on GKE. This feature is supported in the following regions: * `europe-west1` * `us-central1` For more information, see [Agent Gateway for GKE](https://cloud.google.com/gemini-enterprise-agent-platform/govern/gateways/gke-overview). ## Change Change In GKE version 1.35.1-gke.1516000 or later, GKE Dataplane V2 clusters use a unified `cilium-cni` configuration instead of a chained CNI setup. With this change, Cilium configures the Pod default gateway by using its node-local virtual router interface (`cilium_host`), which has the statically assigned link-local IP address `169.254.4.6`. As a result, node-local `kubelet` health checks (`kube-probe` for liveness, readiness, and startup probes) and NodeLocal DNSCache traffic now originate from`169.254.4.6` instead of the `.1` address of the node's Pod CIDR range (for example, `10.x.x.1`). If your workloads only accept traffic from specific IP address ranges, for example through application-level IP allowlists or web server ACLs, allow traffic from `169.254.4.6/32` before you upgrade. Otherwise, health checks for these workloads might fail. For more information, see[Using GKE Dataplane V2](https://cloud.google.com/kubernetes-engine/docs/how-to/dataplane-v2#health-check-source-ip).