Decouple adding new static worker nodes from the installation process #2832
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
sig/cluster-management
Denotes a PR or issue as being assigned to SIG Cluster Management.
Milestone
Description of the feature you would like to add / User story
Adding a new static worker node initiates the whole cluster provisioning process. This means that it might upgrade packages on control plane nodes (such as containerd, crictl...) which might not be expected when adding a new worker node. I think adding new worker nodes should be a decoupled process that doesn't touch control plane nodes at all besides generating the needed kubeadm token.
Solution details
Alternative approaches
There's no alternative available to avoid touching control plane nodes when adding new static worker nodes
Use cases
The text was updated successfully, but these errors were encountered: