We're currently on Calico 3.18, which supports Kubernetes 1.18 - 1.20. As of writing, the latest Calico version, 3.21, supports 1.20 - 1.22. We should upgrade Calico before upgrading to Kubernetes 1.21.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| kubeadm: Upgrade Calico to v3.21.0 | operations/puppet | production | +681 -110 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T327025 Upgrade Toolforge Kubernetes to version 1.26 | |||
| Open | None | T316107 Upgrade Toolforge Kubernetes to version 1.25 | |||
| Open | None | T307651 Upgrade Toolforge Kubernetes to version 1.24 | |||
| Resolved | taavi | T298005 Upgrade Toolforge Kubernetes to version 1.23 | |||
| Resolved | taavi | T286856 Upgrade Toolforge Kubernetes to latest 1.22 | |||
| Resolved | rook | T308172 Upgrade PAWS to Kubernetes 1.21 | |||
| Resolved | taavi | T282942 Upgrade Toolforge Kubernetes to latest 1.21 | |||
| Resolved | taavi | T292698 Upgrade calico to 3.21 |
Event Timeline
Comment Actions
Change 738179 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] kubeadm: Upgrade Calico to v3.21.0
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2021-11-16T12:31:48Z] <majavah> uploading calico 3.21.0 to the internal docker registry T292698
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2021-11-16T12:37:47Z] <majavah> testing calico 3.21 upgrade T292698
Comment Actions
I tested this on toolsbeta and it works fine (after remembering to upgrade the required hiera value). As before, there's no interruption to existing traffic flows.
Comment Actions
Change 738179 merged by Arturo Borrero Gonzalez:
[operations/puppet@production] kubeadm: Upgrade Calico to v3.21.0
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2021-12-20T18:01:37Z] <majavah> deploying calico v3.21.0 (T292698)
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2021-12-20T18:20:07Z] <majavah> deploying calico v3.21.0 (T292698)