Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When a node joins the Kubernetes cluster, there is a pod reporting an error:calico/node is not ready: felix is not ready: readiness probe reporting 503 #9753

Open
zhang1788 opened this issue Jan 24, 2025 · 5 comments

Comments

@zhang1788
Copy link

Expected Behavior

The node can successfully communicate with the Kubernetes cluster, and Calico is working properly.

Current Behavior

kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-564985c589-cb6sh 1/1 Running 0 14m
kube-system calico-node-jkmjz 0/1 Running 0 8m57s
kube-system calico-node-nk2vp 1/1 Running 0 14m
kube-system coredns-55cb58b774-lm8pr 1/1 Running 0 81m
kube-system coredns-55cb58b774-m7f6m 1/1 Running 0 81m
kube-system etcd-k8s-master 1/1 Running 0 81m
kube-system kube-apiserver-k8s-master 1/1 Running 0 81m
kube-system kube-controller-manager-k8s-master 1/1 Running 0 81m
kube-system kube-proxy-2ttzx 1/1 Running 0 81m
kube-system kube-proxy-dzlss 1/1 Running 0 52m
kube-system kube-scheduler-k8s-master 1/1 Running 0 81m

kubectl describe pod calico-node-jkmjz -n kube-system
Image

kubectl logs calico-node-jkmjz -n kube-system
Image

Possible Solution

Steps to Reproduce (for bugs)

1.Initialize the Kubernetes cluster.
sudo kubeadm init --apiserver-advertise-address=172.31.30.54 --control-plane-endpoint=node1 --kubernetes-version=v1.30.1 --service-cidr=10.50.0.0/16 --pod-network-cidr=10.60.0.0/16 --cri-socket=unix:///run/containerd/containerd.sock
2.Install the Calico plugin.
kubeflow apply -f calico.yaml
3.The node joins the cluster.

Context

Your Environment

  • Calico version

Image

  • Calico dataplane (iptables, windows etc.)

  • Orchestrator version (e.g. kubernetes, mesos, rkt):
    kubectl version
    Image

  • Operating System and version:

Image

  • Link to your project (optional):
@mazdakn
Copy link
Member

mazdakn commented Jan 28, 2025

@zhang1788 it seems you are getting an error with ipset list. Is there any ipset with "cali" prefix on the nodes?

@tomastigera
Copy link
Contributor

@zhang1788 it seems that there is an incompatibility between the ipset usitility dstributed with calico-node and the API in your system, Ubuntu 20.04 is fairly old, would you be able to upgrade your system?

@zhang1788
Copy link
Author

@zhang1788 it seems that there is an incompatibility between the ipset usitility dstributed with calico-node and the API in your system, Ubuntu 20.04 is fairly old, would you be able to upgrade your system?

Which version do I need to upgrade to? Are there any other ways to solve this problem?

@zhang1788
Copy link
Author

@zhang1788 it seems you are getting an error with ipset list. Is there any ipset with "cali" prefix on the nodes?

Image

@zhang1788
Copy link
Author

I have found that my hobot node cannot load ipip and ip_set modules. Could the problem be here?

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants