this is what our workspace structure looks like to start with - :root:operators:mounts and :root:providers:mounts are used in the pr, so we didn't fuck with that, and :root:consumer is where we're gonna put our clusters
Comments
Log in with your Bluesky account to leave a comment
our "operator" sees the new workspace, and starts setting up a kind cluster and the necessary resources (see the script for what it's doing) to then mount the kind cluster in kcp
so yeah, kcp is pretty fucking dope. in production, we'd have an actual operator creating capi clusters and sorting that shit out, and run kcp itself in a multi-regional setup, and you kind of quite quickly get to a multi-region, multi-cluster management system???
Comments
it's pretty fucking cool
but, another next step for us is to work out how to present apis into the mounted clusters, ideally without some sort of sync component
note: we haven't fucked with the kubeconfig or anything in between, this is all via the same endpoint