Building a sovereign, vendor-agnostic Cloud API
summary
A sovereign, vendor‑agnostic Cloud API implements a single declarative spec that deploys identical VM, networking, storage and cluster resources across stacks by using a provider‑owned translation layer; it runs on KCP with a Platform Mesh UI. Two controllers enforce correctness: a provider‑driven dependency controller (validating admission webhook) blocks VPC deletion when subnets/VMs reference it, and a consumption‑quota controller denies a second VM creation in the demo. Air‑gapped delivery uses OCM/CTF to package charts and images; the demo successfully provisions an AWS EC2 instance and enforces limits.
AI-written summary · about
chapters (12)
- 0:00Introduction to sovereign API
- 1:09Challenges with heterogeneous APIs
- 3:19Goals for the vendor-agnostic API
- 4:46Redefining service providers
- 5:49Foundation: KCP and Platform Mesh
- 8:45Vendor-agnostic API design
- 10:08Handling resource dependencies
- 13:01Resource consumption quotas
- 15:52Air-gapped environment challenges
- 18:01Live demo of the Cloud API
- 28:42Summary and open source projects
- 29:46Q&A session
related talks
17mSovereign Cloud Stack Technical Deep Dive
18mA Cloud-Native Tool for the mass
35mBuilding a Controller Manager for Your Cloud Platform
35mSimplified Experience Of Building Cluster API Provider In Multitenant Cloud
23mIntroduction to Crossplane and Simplifying Cloud Native Infrastructure Management
25mStandardizing Cloud Native Application Delivery Across Different Clouds
22mYour Cloud. Your Rules. Building a Sovereign Cloud with Open Technologies
40mPanel: Bringing The Cloud To Kubernetes - Moderated by: Nic Cope, Upbound