chore: add upgrade script and docs for it #1341
Conversation
This change adds an upgrade script which will follow the node upgrade process allowing operators to run a more controlled upgrade experience. Signed-off-by: Kevin Carter <[email protected]>
| ansible-playbook playbooks/facts.yml --become | ||
|
|
||
| echo "Upgrading cluster to Kubernetes version ${VERSION_NUMBER}" | ||
| ansible-playbook upgrade-cluster.yml --become -e kube_version${VERSION_NUMBER} --limit "kube_control_plane:etcd" |
There was a problem hiding this comment.
If we pass the k8s desired version here, will the playbook ignore whats in group_vars/k8s_cluster?
There was a problem hiding this comment.
yes. but the script updates the group vars as soon as the upgrade is complete.
| ansible-playbook playbooks/facts.yml --become | ||
|
|
||
| echo "Upgrading cluster to Kubernetes version ${VERSION_NUMBER}" | ||
| ansible-playbook upgrade-cluster.yml --become -e kube_version${VERSION_NUMBER} --limit "kube_control_plane:etcd" |
There was a problem hiding this comment.
We discussed upgrade-cluster.yml will attempt to drain the node(s) vs cluster.yml with the -e var will not. What's the preference?
The documentation mentions that "components will be upgraded in the same order they were installed", which does present an issue with kubelet being upgraded prior to kube-apiserver. Kubelet does still run on these control plane nodes, so I wonder if there is some logic that could be added to the playbooks to ensure ordering or a validation that kube-apiserver is >= new kubelet prior to upgrade.
There was a problem hiding this comment.
we should look into that.
3 participants
This change adds an upgrade script which will follow the node upgrade process allowing operators to run a more controlled upgrade experience.