You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
@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 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?
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: