Einstein gave us E=MC². We discovered OSS=(MC)² - where Open Source Software emerges from Multi-Cloud Multi-Cluster capabilities squared.
Most teams are trapped in single-cloud architectures, paying premium prices for basic portability. Meanwhile, the cloud giants enjoy unlimited infrastructure flexibility because they built their own platforms. But what if that same capability was democratically available?
Using CAPI for cluster provisioning, Sveltos for day-2 operations, and a carefully assembled stack of CNCF projects, we built Multi-Cloud Multi-Cluster infrastructure that deploys anywhere—AWS, Azure, bare metal, your laptop—with identical workflows.
This talk covers the technical architecture, deployment patterns, and the physics of why (MC)² only becomes a reality when powered by open source.
The (MC)² approach demonstrates how CNCF projects can be composed into enterprise-grade infrastructure platforms. By documenting both successes and failures, we accelerate adoption of tools like CAPI, Sveltos, and the broader cloud-native ecosystem.
Teams gain infrastructure portability without vendor premium pricing. The open source multiplier effect means improvements benefit everyone—bug fixes, feature additions, and operational knowledge become community assets rather than proprietary secrets.
This blueprint enables smaller teams to build infrastructure capabilities previously available only to large enterprises. Every implementation strengthens the open source infrastructure ecosystem and proves that vendor independence is achievable through community collaboration.
The real equation: better tools for everyone = stronger open source community = genuine infrastructure freedom.
This is an implementation talk on k8s not something suited to elevating/empowering/showcasing the FOSS ecosystem. Just a cool case study of stuff implemented on k8s. Speaker isn't a maintainer of sveltos
The reviewers found that while the topic is technically interesting, it was perceived more as an implementation-focused case study on Kubernetes rather than a talk that elevates and empowers the FOSS ecosystem. A key point of feedback was that the speaker is not a maintainer of the open-source project Sveltos, which was a central theme of the talk. The committee prioritizes talks that highlight projects created or significantly contributed to by the speakers themselves.