...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
# As usual, run the command from the "kubespray" folder $ ansible-playbook -i inventory/mycluster/hosts.yaml --become --become-user=root b upgrade-cluster.yml |
The difference lies in the playbook used, of course. Components are upgraded in the order in which they were installed in the Ansible playbook. The order of component installation is as follows:
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
# Current repo tag $ git describe --tagstag v2.13.1-115-g68d18daf # List of all tags $ git tag ... v2.13.1 # current version v2.13.2 v2.13.3 v2.13.4 v2.14.0 v2.14.1 v2.14.2 v2.15.0 # final version # Edit the tag $ git checkout v2.13.2 Previous HEAD position was a923f4e7 Update kube_version_min_required and cleanup hashes for release (#7160) HEAD is now at 3d6b9d6c Update hashes and set default to 1.17.7 (#6286) |
Therefore, update the cluster with the command at the beginning of the page, based on starting with the v2.13.2 tag and so on up to the v2.15.0 tag. It It is inevitable that in the updating phase, from time to time, small manual interventions may be necessary.