Adding Nodes to a Cluster fails with "skipped caching discovery info due to Get "https://<node_IP>:4
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
PreviousKubernetes Resource Quota Not Updating
NextNodes Fluctuating Between Ready and NotReady State Due to Kernel Memory Leak Issue
Last updated
