Ubuntu

calico is blocked since ignore-loose-rpf config is in conflict with rp_filter value

Asked by Kwami Sossoe

Hello,

I installed charmed distribution of kubernetes on lxd cluster with juju on Ubuntu OS
In the status, I found that calico is blocked since ignore-loose-rpf config is in conflict with rp_filter value.
I searched on the internet but not find correct way to fixe my issue.
I am looking for how to solve this issue

App Version Status Scale Charm Channel Rev Exposed Message
calico 3.21.4 blocked 5 calico candidate 70 no ignore-loose-rpf config is in conflict with rp_filter value

Below the relations between calico and kubernertes components:

Relation provider Requirer Interface Type Message
etcd:db calico:etcd etcd regular
kubernetes-control-plane:cni calico:cni kubernetes-cni subordinate
kubernetes-worker:cni calico:cni kubernetes-cni subordinate

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Kwami Sossoe
Solved:
Last query:
Last reply:
Revision history for this message
Bernard Stafford (bernard010) said : 		#1

calico is not in the Ubuntu packaging or Debian packaging.
Try removing the package. That may solve the conflict with Kubernetes.

Revision history for this message
Kwami Sossoe (kwamiss) said : 		#3

Thank you @bernard010 for your response.

Calico is integrated in the kubernetes charmed bundle from the version 1.24.
I check ; It replaces Flannel in 1.24; 1.25 and 1.26

So by removing the Calico, the blocked problem is not anymore.
I deployed flannel and related it to etcd, kubernetes-control-plane and kubernetes-worker

I find new issues :

kubernetes-control-plane 1.25.6 waiting 3 kubernetes-control-plane 1.25/stable 219 no Waiting for kubelet,kube-proxy to start.

kubernetes-worker 1.25.6 waiting 3 kubernetes-worker 1.25/stable 77 yes Waiting for kubelet,kube-proxy to start.

I try
juju ssh kubernetes-worker/0
ubuntu@juju-ab78de-7:~$ sudo snap list|grep kubelet
kubelet 1.25.6 2814 1.25/stable canonical** classic,in-cohort

Try to start kubelet, but somehow it seeems some packages are missing
The service kubelet is not available.

I have these above issues on 1.24, 1.25 and 1.26 of charmed-kubernetes
since I deployed by the command

juju deploy charmed-kubernetes --channel 1.26/stable

juju deploy charmed-kubernetes --channel 1.25/stable

juju deploy charmed-kubernetes --channel 1.24/stable

But I am wondering why calico would not worked but it is included in the new version of the kubernetes bundle.

The 1.23 which contains flannel is not maintained by Canonical
❯ juju deploy charmed-kubernetes --channel 1.23/stable
ERROR selecting releases: charm or bundle not found for channel "1.23/stable", platform "amd64"

Revision history for this message
Bernard Stafford (bernard010) said : 		#4

https://komodor.com/learn/kubernetes-troubleshooting-the-complete-guide/

https://kubernetes.io/docs/tasks/debug/debug-cluster/

Revision history for this message
Kwami Sossoe (kwamiss) said : 		#6

I downgraded my juju client from 3.0.3 to 2.9.38
Recreate the cluster Kubernetes by the
juju deploy charmed-kubernetes --channel 1.24/stable

Remove Calico bundle which is installed by default from Kubernetes version 1.24+
And Install another CNI : Canal --channel 1.24/stable

And voilà