Cluster Scaling & Other Operations
This document describes steps to scale your K3s management cluster that is part of your self-hosted Private Cloud Director deployment.
Scale Up Management Cluster
Let's consider that we have 3 master nodes as part of your management cluster, with IP addresses 1.1.1.1, 2.2.2.2 `and` 3.3.3.3.
$ cat /opt/pf9/airctl/conf/k3s-bootstrap-config.yaml
...
masterNodes:
- nodeName: 1.1.1.1
- nodeName: 2.2.2.2
- nodeName: 3.3.3.3Lets say that you want to scale up the management cluster to 5 nodes, and that 4.4.4.4 & 5.5.5.5 are the IP addresses of the 2 new nodes to be added.
To scale up the number of cluster nodes to 5:
Configure the pre-requisites on the two new nodes.
Edit the cluster bootstrap configuration file
/opt/pf9/airctl/conf/k3s-bootstrap-config.yamland add the two new IP addresses to the section calledmasterNodesin the file.Finally, run the
airctlcommand shown below to scale up the cluster.
$ cat /opt/pf9/airctl/conf/k3s-bootstrap-config.yaml
...
masterNodes:
- nodeName: 1.1.1.1
- nodeName: 2.2.2.2
- nodeName: 3.3.3.3
- nodeName: 4.4.4.4
- nodeName: 5.5.5.5Now verify that the management cluster has scaled up by querying the cluster nodes.
Management Cluster Status
To check the status of your management cluster, run the following command:
Sample output:
Scale Down Management Cluster
Now let's assume that we want to remove nodes 2.2.2.2 and 3.3.3.3 from the management cluster. To scale down the cluster:
Edit the cluster bootstrap configuration file and remove the IP addresses of the two nodes.
Then run the
airctlcommand as shown below to scale down the cluster.
Cluster state post scale down operation completion:
Uninstall Self-Hosted Deployment
To uninstall the specific region of your self-hosted deployment, run the following command. If you want to uninstall all regions, just remove --region flag.
This command will uninstall and remove configured regions along with all infrastructure software like consul, vault, percona, k8sniff, etc.
If you plan to reuse the same nodes to deploy a new self-hosed Private Cloud Director environment, make sure to also run the following command on all nodes first.
Was this helpful?
