How To Create A Management Kubernetes Cluster For Crossplane

Crossplane runs inside a Kubernetes cluster. We can use it to manage everything, but what should we use to create that initial cluster? It's "the chicken or the egg" problem. We use Crossplane to create Kubernetes clusters, yet we need a Kubernetes cluster to run Crossplane.
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
➡ Gist with the commands: gist.github.com/269d2e963f285...

[@dorwardtechnologies4451]

I wish crosspane provides a cli that will detect the local os, create a local cluster with crossplane, and do whatever you explained in this video, without duplicating manifests.

[@Upbound]

That would indeed be nice. I'll discuss it with the team.

[@mrops]

hey Victor, another nice one. Thanks. What I wonder is, will there be any configuration drift etc in case that I run cluster-autoscaler and scale up the node pool when it is needed by my app? How would Crossplane reacts to this scenario?

[@Upbound]

In those cases, you should specify the min and max number of nodes.

[@elroyhaw]

Great video! I have one question regarding the demo, why was the ready state marked as true when the number of nodes have yet to increase to 5?

[@Upbound]

Sorry for not responding earlier. Let me double check it and get back to you. I'm currently on holidays without the access to the work computer.

[@debkr]

Hello Victor. How can I deploy a self/crossplane managed kubernetes cluster on AWS. I am looking to provision self-managed k8s cluster and not EKS. On your other video on Cluster API, we had some discussion. As you suggested, after going through the entire documentation and so far, I am liking the core concept of Crossplane.

[@eamonnmccudden1070]

How would the process of a cluster upgrade work? If you changed the version and applied the yaml (or via flux/argocd/manually) would I have a new control plane or completely updated cluster (including workers) If the answer is just to create a blue green and canary it, can you do a demo how that would work for something with stateful? Like an app polling internal k8 database or something?

[@Upbound]

Most managed k8s clusters are using rolling updates when upgrading. It would work on one node at the time and the cluster would be available at all times. I'll add that to the TODO list for upcoming videos

[@holgerwinkelmann6219]

hey, what about jet-rancher as payload cluster ,-)

[@holgerwinkelmann6219]

why not putting external name into the Status?

[@countbrapcula-espana]

Buenas tardes Victor. In theory, on the local K3D cluster (bootstrap cluster) you also could have used the option to add config to Crossplane to apply a ProviderConfig for Helm (after installing the helm provider plugin for Crossplane) and a Release config that pointed to the Crossplane helm chart repository vs entering the helm install commands at the terminal, right?