Upgrade Calico charm to support Calico CNI version v3.19
Bug #1950050 reported by
Pedro Victor Lourenço Fragola
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Calico Charm |
Fix Released
|
Medium
|
George Kraft | ||
Bug Description
Currently, the charm has a version of Calico that is more than 2 years old:
calicoctl version
Client Version: v3.10.1
Git commit: 4aaff8e9
Cluster Version: v3.10.1
Cluster Type: k8s
rocks.canonical
Customer reported the need to use new features available in the new versions:
security updates, exposing Service CIDR via BGP, etc.
There is already a PR to upgrade to version 3.19 => https:/
The latest version is 3.20 => https:/
Revision history for this message
| George Kraft (cynerva) wrote | #1 |
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #2 |
| Changed in charm-calico: | |
| status: | New → Fix Committed |
| importance: | Undecided → Medium |
| assignee: | nobody → George Kraft (cynerva) |
| milestone: | none → 1.24 |
| Changed in charm-calico: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is on our roadmap, we're working on it. It's not as simple as merging the existing Calico 3.19 PR. In order to support VXLAN on newer versions of Calico, kubernetes-master units will need to run kubelet and participate as Nodes within the Kubernetes cluster. This is a significant architectural change but we think we can do it safely, and once it's done, we should be able to update Calico, and we should be better able to stay on top of Calico updates in the future.