K8s start Service Kube calico start reports the following error
Skipping datastore connection test
ERROR: Unable to access datastore to query node configuration
Terminating
Calico node failed to start
Solution:
The main reason for this problem is that the firewall of the primary node is turned on. Just turn off the firewall of the primary node (that is, the server where etcd is installed)
systemctl stop firewalld
Other possible errors
1. The address of etcd in calico configuration file is written incorrectly
2. Etcd service is not started
Read More:
- K8s initializing the master & worker node error [How to Solve]
- How to Solve kubelet starts error (k8s Cluster Restarted)
- [Solved] Ubuntu 20.04 LTS Install k8s Error: The connection to the server localhost:8080 was refused
- How to Solve k8s Nodal issues: /sys/fs/cgroup/memory/docker: no space left on device\““: unknown.
- [Solved] k8s kubeadmin init Error: http://localhost:10248/healthz‘ failed
- [Solved] K8s Initialize Error: failed with error: Get “http://localhost:10248/healthz“
- K8S Master Initialize Error: [ERROR CRI]: container runtime is not running: output: E0812
- K8s Install Error: Error: unknown flag: –experimental-upload-certs
- [Solved] k8s Error: Back-off restarting failed container
- [Solved] Rabbitmq Server Error: unable to perform an operation on node ‘rabbit@nscczzms‘. P
- K8s ❉ Error: cannot be handled as a** [How to Solve]
- k8s kubernetes ingress error: endpoints “default-http-backend“ not found
- [Solved] Error: unable to perform an operation on node ‘rabbit@DESKTOP-xxx‘. Please see diagnostics informa
- [Solved] K8s cluster build error: error: kubectl get csr No resources found.
- [Solved] VScode powershell Run ts-node Error: Unable to load file xxxx…
- [Solved] k8s error retrieving resource lock default/fuseim.pri-ifs: Unauthorized
- K8s cluster initialization error: Port 6443 is in use [Solved]
- Kubernetes Error: Error in configuration: unable to read client-cert* unable to read client-key*
- fatal: unable to access”: The requested URL returned error: 500
- [Solved] Upstream connect error or disconnect occurs after the k8s istio virtual machine is restarted