Oh, I get it. Reading the design document[0] helped greatly. Should've done more than skim the blogpost. The definition of what you want is specified as a custom resource that is cloud-agnostic. Then a set of cloud-specific custom controllers are installed on a K8s instance and they control which cloud is affected by your `kubectl apply`.

You have to set up your own k8s manually (there's no way to bootstrap), but then it's all fun and games.

Nice. Very clever.

0: https://docs.google.com/document/d/1whncqdUeU2cATGEJhHvzXWC9...