Lightning Talk: Designing for Exit: Why Portability Is a Sovereignty Requirement
summary
Portability is a hard requirement for sovereign cloud: if workloads cannot move, control and sovereignty vanish. The talk claims sovereignty depends on three layers (ownership, control, enforcement) and five pillars (data, legal, operational, security, portability) and argues design for exit from day one. Practical steps: containerization, Kubernetes API for standard deployment, infrastructure abstraction and avoiding vendor lock‑in, using CNCF tools like Argo and OpenTofu to keep workloads movable.
AI-written summary · about
related talks
08mLightning Talk: Principles of Portability for Multi-Cloud Applications
40mSovereign Cloud - From Mirage to Epiphany
26mWhen and Why Does Portability Matter? Exploring Multi-cloud, Open Source and Cloud Switching Costs
06mLightning Talk: Cloud Native Design Patterns
16mOf Ports and Portability in the Public Cloud
31mSponsored Session: Freedom to Build: Open Source Foundations for Sovereign Cloud Infrastructure
43m5 tips on creating modern, cloud native applications
45mWhat We Need Are Standards in the Cloud