Guest cluster deployment fails with Kubelet error: "cni plugin not initialized"
search cancel

Guest cluster deployment fails with Kubelet error: "cni plugin not initialized"

book

Article ID: 424526

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

  • Creating a new guest cluster gets stuck with one control plane node in "Provisioned" state and no further control plane nodes being deployed.

  • Verifying the kubelet service on the control plane node, following errors are noticed :

    "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"

  • Following components on the control plane node are in running state : kube-proxy, kube-vip, kube-controller-manager, etcd, kube-apiserver, and kube-scheduler.

Environment

vSphere Kubernetes Service

Cause

The Cluster API components (CAPI and CAPV) are unable to communicate with the new workload cluster. 

Resolution

Allow port 6443 communication from the load balancer service to the guest cluster in the firewall configuration. 

Powered by Wolken Software