...
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:
- Docker
- etcd
- kubelet and kube-proxy
- network_plugin (such as Calico or Weave)
- kube-apiserver, kube-scheduler, and kube-controller-manager
- Add-ons (such as KubeDNS)
Anyway, before launching the update, let's see a handful of parameters that can be changed and what to do in order not to run into versioning problems.
...
The main files to be analyzed and modified for the configuration of our cluster are:
- inventory/mycluster/group_vars/all/all.yml;
- inventory/mycluster/group_vars/k8s-cluster/addons.yml;
- inventory/mycluster/group_vars/k8s-cluster/k8s-cluster.yml;
- inventory/mycluster/group_vars/k8s-cluster/k8s-net-<cni_chosen>.yml.
In particular, the second on the list allows you to find applications such as Helm, Metrics Server, Nginx ingress controller, etc. already installed in the cluster.
Multiple upgrades
| Warning | ||
|---|---|---|
| ||
Attempting to upgrade from an older release straight to the latest release is unsupported and likely to break something: do not skip releases when upgrading, but by one tag at a time. |
...