Release
Introducing ambient networking for GKE
Cloud Blog · By Chris Crall ·
The Brief
- Google announced general availability of ambient networking for Google Kubernetes Engine (GKE).
- The feature is a sidecarless service mesh, removing per-pod network sidecars.
- Network sidecars are criticized for high resource consumption and management overhead.
Why it matters
Teams running a service mesh on GKE may be able to avoid the resource cost and operational burden of sidecar proxies in every pod.
Who’s affected
- GKE users running or considering a service mesh
- #kubernetes
- #gke
- #service-mesh
- #networking
- #sidecarless
Network sidecars have a deserved reputation for excessive resource consumption and increased management overhead, especially in a service mesh environment. Today, we are announcing the general availability of ambient networking for Google Kubernetes Engine (GKE). This milestone…