Connecting Applications Across the Hybrid Cloud
summary
Claim: open‑source Skupper provides application‑layer connectivity across hybrid clouds using MQP over TLS, so services keep their local DNS names while traffic routes across clusters. Demo builds two identical backends in separate Kubernetes clusters, a front end, and a scupper mesh (operator or CLI/Ansible automation); when the AWS backend is killed traffic transparently fails over to Google and back when recovered. Requires a shared token; operator needs admin rights; no code changes.
AI-written summary · about
chapters (14)
- 0:00Introduction to hybrid cloud
- 3:13Connectivity challenges explained
- 7:07Solutions for cloud connectivity
- 10:42How Scapper works
- 17:40Live demo setup
- 21:12First Scapper deployment
- 25:30Automatic failover demo
- 27:40Cleaning up demo
- 28:42Automating with Ansible
- 31:52Cross-cloud database demo
- 36:32Key benefits of Scapper
- 39:00Portability in hybrid cloud
- 43:40Security and tokens
- 46:15Q&A session
related talks
25mInterconnecting Cloud Applications with Skupper
37mConnecting the Dots: Skupper.io as an application modernization Enabler
29mCloud-Edge InCloud-Edge Interconnect: Doing It Right With The Skupper project
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
33mHybrid architecture solutions with Kubernetes and the cloud native stack
32mSolving Multi-Cluster Network Connectivity With Submariner
18mConnecting Kubernetes clusters with Submariner
34mDistributed applications and Kubernetes