Proxy Service: A New Network Traffic Abstraction in Kubernetes
summary
Kubernetes replaces brittle SSH tunnels with a gRPC-based proxy service that adds a proxy server plus per-node agents, already implemented as a reference repo on GitHub. It supports HTTP CONNECT for simple TCP-over-HTTP, a gRPC bi-directional stream for multiplexed TCP/UDP, and mTLS authentication. Connections are resumable across stream resets, agents can load-balance to multiple endpoints, and the API server configures connectivity via a YAML object. Core features work; advanced auditing, fair-queueing and label-based routing are planned.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:32SSH Tunnels
- 4:48API Server
- 5:20Admission Webhooks
- 6:07Proxy Service Example
- 7:08Technical Details
- 15:27Reference Implementation
- 17:17Direct Connect
- 19:20Network Context
- 21:06Future Possibilities
- 25:27Contribute
related talks
28mProxy Service: A New Network Traffic Abstraction in Kubernetes
15mSimplify Kubernetes Connectivity
48mProxies, Gateways, and Service Mesh. Why Are Words so Confusing?
35mgRPC Load Balancing on Kubernetes - Jan Tattermusch, Google
30mgRPC & Kubernetes
18mHigh Performance Service Meshes with gRPC Proxyless
21mProduction-Ready gRPC: How Service Meshes Simplify Security, Routing, and Observability
30mMaking Kubernetes Networking Ready for Service Providers