Open shundezhang opened 1 week ago
As per internal discussion, this change will happen in version 1.32 as per the PR https://github.com/canonical/microk8s/pull/4638
Is there a quick way to trigger this bug in order to verify if upgrading the Calico version and updating permissions effectively resolves the issue?
Summary
A bug is found in Calico 3.25 and is believed to be fixed in 3.26. Since microk8s 1.28/1.29/1.30 are still using calico 3.25, a user hit this bug after running microk8s 1.28 for 120 days.
What Should Happen Instead?
Microk8s 1.28 should bundle with calico 3.26. Also as suggested in calico page, microk8s 1.29 should bundle with calico 3.27 [1], and microk8s 1.30 should bundle with calico 3.28 [2].
[1] https://docs.tigera.io/calico/3.27/getting-started/kubernetes/requirements [2] https://docs.tigera.io/calico/latest/getting-started/kubernetes/requirements
Reproduction Steps
Introspection Report
Can you suggest a fix?
Upgrade calico to 3.26.5.
Are you interested in contributing with a fix?
Update /var/snap/microk8s/current/args/cni-network/cni.yaml file, change calico image version from 3.25.1 to 3.26.5, and add a new SA/role/rolebinding:
Update an existing clusterrole
Apply the yaml file
microk8s kubectl apply -f /var/snap/microk8s/current/args/cni-network/cni.yaml