-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
@zhang1788 it seems you are getting an error with |
@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 if you are using IPIP overlay, and ipip module cannot be loaded, then it's an issue. Are you using overlay? |
The latest LTS version of Ubuntu is 24.04, so at either 24.04 or 22.04. |
@zhang1788 the ipset issue should be irrelevant of IPIP module. But please try with to fix the IPIP module, and also a newer version of Ubuntu, and let us know if it helped. |
Expected Behavior
The node can successfully communicate with the Kubernetes cluster, and Calico is working properly.
Current Behavior
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 dataplane (iptables, windows etc.)
Orchestrator version (e.g. kubernetes, mesos, rkt):

kubectl version
Operating System and version:
The text was updated successfully, but these errors were encountered: