Service Networking Within Air-Gapped Environments: Deployment Strategies and Operat...
summary
Google Distributed Cloud air‑gapped deploys an Istio service mesh with Envoy sidecars and in‑cluster ingress/egress gateways to remove per‑service networking toil, supporting a fleet of 45+ services with ~10 microservices each. Deploys use a primary‑remote multi‑network topology across bare‑metal and KubeVirt clusters, integrate MetalLB, Cilium/Hubble, cert‑manager, Prometheus/Cortex, OpenTelemetry/Fluentbit and Grafana, and use Envoy filter API/Lua/WASM for missing features. Operational pain points: XDS growth, noisy proxy debug logs, coordinated control‑plane/data‑plane upgrades, and gateway autoscaling under constrained on‑prem resources.
AI-written summary · about
chapters (14)
- 0:00Air-gapped service networking intro
- 1:24Air-gapped private cloud
- 3:10Typical application requirements in air-gapped environments
- 4:56Service networking with Istio
- 6:45Istio in air-gapped clusters
- 8:33Istio gateways for edge traffic
- 11:39Istio sidecars security
- 14:05Traffic management use cases
- 15:51Extending Istio with Envoy
- 17:34Managing Istio lifecycle
- 20:02Istio dependencies
- 21:04Istio operational challenges
- 26:59Istio scalability hurdles
- 28:02Q&A
related talks
25mApplication Networking on Kubernetes, where are we now?
36mBuilding a Multi Cluster/Env Service Mesh at Airbnb
40mReimagining Application Networking and Security
21mIteratively Implementing Istio: Zero to Service Mesh with No Downtime
41mService Mesh beyond single clusters
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
31mEffective building blocks for securing...
28mDeploying hybrid topologies with k8s & Envoy: a look at service discovery