The clusterctl generate cluster
command returns a YAML template for creating a workload cluster. It generates a YAML file named my-cluster.yaml
with a predefined list of Cluster API objects ( Cluster
, Machines
, MachineDeployments
, etc.) to be deployed in the current namespace.
With the --target-namespace
flag, you can specify a different target namespace.
Run the clusterctl generate cluster --help
command for more information.
Please note that ready-to-use Kubernetes configurations, production-ready node images, kubeadm configuration, cluster add-ons like CNI, and similar services need to be separately prepared or acquired to ensure a comprehensive and secure Kubernetes deployment. This is where Syself Autopilot comes into play, taking on these challenges to offer you a seamless, worry-free Kubernetes experience. Feel free to contact us via e-mail: [email protected] .
The following command applies the configuration of the workload cluster:
The cluster will now start provisioning. You can check status with:
You can also view the cluster and its resources at a glance by running:
To verify the first control plane is up, use the following command:
The control plane won’t be ready
until we install a CNI in the next step.
After the first control plane node is up and running, we can retrieve the kubeconfig of the workload cluster with:
Cilium is used as a CNI solution in this guide. The following command deploys it to your cluster:
You can, of course, also install an alternative CNI, e.g., calico.
There is a bug in Ubuntu that requires the older version of Cilium for this quickstart guide.
The following make
command will install the CCM in your workload cluster:
make install-ccm-in-wl-cluster PRIVATE_NETWORK=false
For a cluster without a private network, use the following command:
Delete the workload cluster and remove all of the components by using:
IMPORTANT : In order to ensure a proper clean-up of your infrastructure, you must always delete the cluster object. Deleting the entire cluster template with the
kubectl delete -f capi-quickstart.yaml
command might lead to pending resources that have to be cleaned up manually.
Delete management cluster with the following command: