sigs.k8s.io/cluster-api@v1.7.1/docs/book/src/tasks/automated-machine-management/scaling.md (about)

     1  # Scaling Nodes
     2  
     3  This section applies only to worker Machines. You can add or remove compute capacity for your cluster workloads by creating or removing Machines. A Machine expresses intent to have a Node with a defined form factor.
     4  
     5  Machines can be owned by scalable resources i.e. MachineSet and MachineDeployments.
     6  
     7  You can scale MachineSets and MachineDeployments in or out by expressing intent via `.spec.replicas` or updating the scale subresource e.g `kubectl scale machinedeployment foo --replicas=5`.
     8  
     9  When you delete a Machine directly or by scaling down, the same process takes place in the same order:
    10  - The Node backed by that Machine will try to be drained indefinitely and will wait for any volume to be detached from the Node unless you specify a `.spec.nodeDrainTimeout`.
    11    - CAPI uses default [kubectl draining implementation](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) with `-–ignore-daemonsets=true`. If you needed to ensure DaemonSets eviction you'd need to do so manually by also adding proper taints to avoid rescheduling.
    12  - The infrastructure backing that Node will try to be deleted indefinitely.
    13  - Only when the infrastructure is gone, the Node will try to be deleted indefinitely unless you specify `.spec.nodeDeletionTimeout`.