* docs: add release v2.8.0 * docs: mention required AWS IAM permissions for upgrades --------- Co-authored-by: malt3 <malt3@users.noreply.github.com> Co-authored-by: Malte Poll <mp@edgeless.systems>
3.6 KiB
Scale your cluster
Constellation provides all features of a Kubernetes cluster including scaling and autoscaling.
Worker node scaling
Autoscaling
Constellation comes with autoscaling disabled by default. To enable autoscaling, find the scaling group of worker nodes:
worker_group=$(kubectl get scalinggroups -o json | jq -r '.items[].metadata.name | select(contains("worker"))')
echo "The name of your worker scaling group is '$worker_group'"
Then, patch the autoscaling
field of the scaling group resource to true
:
kubectl patch scalinggroups $worker_group --patch '{"spec":{"autoscaling": true}}' --type='merge'
kubectl get scalinggroup $worker_group -o jsonpath='{.spec}' | jq
The cluster autoscaler now automatically provisions additional worker nodes so that all pods have a place to run.
You can configure the minimum and maximum number of worker nodes in the scaling group by patching the min
or
max
fields of the scaling group resource:
kubectl patch scalinggroups $worker_group --patch '{"spec":{"max": 5}}' --type='merge'
kubectl get scalinggroup $worker_group -o jsonpath='{.spec}' | jq
The cluster autoscaler will now never provision more than 5 worker nodes.
If you want to see the autoscaling in action, try to add a deployment with a lot of replicas, like the following Nginx deployment. The number of replicas needed to trigger the autoscaling depends on the size of and count of your worker nodes. Wait for the rollout of the deployment to finish and compare the number of worker nodes before and after the deployment:
kubectl create deployment nginx --image=nginx --replicas 150
kubectl -n kube-system get nodes
kubectl rollout status deployment nginx
kubectl -n kube-system get nodes
Manual scaling
Alternatively, you can manually scale your cluster up or down:
- Find your Constellation resource group.
- Select the
scale-set-workers
. - Go to settings and scaling.
- Set the new instance count and save.
- In Compute Engine go to Instance Groups.
- Edit the worker instance group.
- Set the new number of instances and save.
- Go to Auto Scaling Groups and select the worker ASG to scale up.
- Click Edit
- Set the new (increased) Desired capacity and Update.
Control-plane node scaling
Control-plane nodes can only be scaled manually and only scaled up!
To increase the number of control-plane nodes, follow these steps:
- Find your Constellation resource group.
- Select the
scale-set-controlplanes
. - Go to settings and scaling.
- Set the new (increased) instance count and save.
- In Compute Engine go to Instance Groups.
- Edit the control-plane instance group.
- Set the new (increased) number of instances and save.
- Go to Auto Scaling Groups and select the control-plane ASG to scale up.
- Click Edit
- Set the new (increased) Desired capacity and Update.
If you scale down the number of control-planes nodes, the removed nodes won't be able to exit the etcd
cluster correctly. This will endanger the quorum that's required to run a stable Kubernetes control plane.