Who actually controls the cloud?
Keeping data in Frankfurt means little if someone outside your jurisdiction controls the keys needed to decrypt it.
Solving the hard parts of cloud control planes
Kubernetes and the infrastructure beneath it often operate as separate systems. I'm building the control plane that connects them into a working cloud platform.
Three problems I keep running into
From machines to Kubernetes nodes
Kubernetes expects a node. An infrastructure platform provides a machine, network interfaces, volumes and routes. Making those resources work together as one Kubernetes node is the hard part.
When an operation times out
A missing response doesn't tell you whether the operation failed or completed successfully. Retry a machine creation request without checking, and you might end up with two machines instead of one.
Writing
How the pieces fit and where they fail
Sovereignty is a control plane property
Data residency tells you where bytes are stored. It does not tell you who controls identity, keys, audit evidence and recovery, or whether the operator can move the platform elsewhere.
Speaking
Selected talks
- Sovereignty is a control plane property, not a data-residency checkbox
- Why a VM API isn't enough for Kubernetes
- Idempotency is more than "safe to retry"