Adding Nodes to a Cluster fails with "skipped caching discovery info due to Get "https://<node_IP>:443/api?timeout=32s": dial tcp <node_IP>:443: connect: no route to host"
Problem
While adding nodes to the cluster you can see Nodes fail at step 11 with the following error
skipped caching discovery info due to Get "https://<node_IP>:443/api?timeout=32s": dial tcp <node_IP>:443: connect: no route to host"Environment
- Platform9 Managed Kubernetes - All Versions
Cause
This error usually points to a routing issue between the master nodes and the worker nodes. The nodes are unable to reach the Kube API Server which is required for a functioning cluster.
Resolution
- Verify that your environment satisfies all the Networking Prerequisites.
- If you are running a CentOs or RedHat distribution disable the firewalld service temporarily to verify if the required connections are being blocked -
systemctl stop firewalld
Do Not disable the Firewall in a Production Environment. If you are testing internally you can temporarily disable it to determine the root cause and continue to use the product.
For production and other sensitive workloads please work with your Networking team to fulfilll the Networking Prerequisites linked above.
Was this page helpful?