Issue while adding node in existing cluster from different cloud provider in kubernetes?

6/4/2019

We have a running kubernetes cluster with master and 3 worker nodes on azure cloud. Now we want to add a new node which is running on AWS cloud. When tried to add this node into existing cluster then we are getting error as.

Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

but if the node is existing on same cloud provider then it is working fine.

Please let me know if anyone faced the same issue.

-- TechChain
amazon-web-services
azure
azure-devops
docker
kubernetes

1 Answer

6/6/2019

As per documentation here.

Please select one of the tabs to see installation instructions for the respective third-party Pod Network Provider.

The network must be deployed before any applications. Also, CoreDNS will not start up before a network is installed. kubeadm only supports Container Network Interface (CNI) based networks (and does not support kubenet).

So please verify the "status" of your cluster:

kubectl get nodes -o wide
kubectl get pods --all-namespaces

For "Cross Cloud Kubernetes cluster" please take a look here

-- Hanx
Source: StackOverflow