~/talk

Remote Control Planes With Konnectivity; What, Why And How?

speakerdeck:jnummelin
slides:none on file

Claim: Kubernetes control planes run remotely in a different datacenter while worker nodes stay local, using Konnectivity as the reference implementation of the egress selector/CAP-1281 model. Mechanism: a connectivity server plus agents create gRPC reverse tunnels over TLS so the API server proxies calls back into cluster networks (kubectl exec/logs, admission webhooks). Real deployments in Kubermatic and k0s handle hundreds to thousands of clusters in production. Tradeoffs: HA is an M×N complexity, debugging is harder, migration from VPNs requires machine replacement, and documentation is sparse.

AI-written summary · about

  1. 0:00Introduction to remote control
  2. 2:43Challenges of remote clusters
  3. 5:48Use cases for remote planes
  4. 10:05API server communication issues
  5. 12:07The egress selector solution
  6. 17:18Connectivity component design
  7. 19:54Real world implementation
  8. 25:32K0s integration
  9. 27:22Challenges and debugging
  10. 29:09Q&A and closing thoughts
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.