Kuberneters in Hybrid Environments Using Cloud Interconnect
summary
F5 Container Connector runs as a Kubernetes ingress controller on GKE and uses the BIG-IP REST API to create virtual servers in colo (demo uses Equinix) that route North–South traffic over IPSec VPN to Google Cloud; works similarly with AWS, Azure and Oracle. It auto-populates pools via nodePort or Calico+BGP using actual pod IPs, honors Kubernetes health probes so only healthy pods get traffic, and the demo shows live request traces and 100% success rate on a basic app.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:48Multicloud definition
- 2:40Multicloud drivers
- 3:37Common deployments
- 5:22F5 Container Connector
- 9:06Demo
related talks
41mKubernetes in Action: Examples from Google Container Engine
27mElastic cloud bursting with Virtual Kubelet and KIP
27mExtending Kubernetes - Lessons Learned From an L4 Ingress Implementation
15mSimplify Kubernetes Connectivity
27mKubernetes Everywhere: Lessons Learned From Going Multi-Cloud
38mBuilding Hybrid Clouds with Istio
33mHybrid architecture solutions with Kubernetes and the cloud native stack
42mCo-Evolution of Kubernetes and GCP Networking