Open thechubbypanda opened 1 week ago
Reproduction steps:
minikube start
minikube node add
minikube addons enable dashboard
watch kubectl get -n kubernetes-dashboard -o wide pod
There is also an error when adding the second node:
Cluster was created without any CNI, adding a node to it might cause broken networking.
However the minikube start command logs:
minikube start command
Configuring bridge CNI (Container Networking Interface) ...
which implies that a CNI has been setup (albeit a bridge one).
bridge
Alternatively using minikube start --cni kindnet, we still get told that:
minikube start --cni kindnet
Configuring CNI (Container Networking Interface) ..
however when adding another node we still get:
despite the fact that the node now works perfectly and the dashboard comes up.
log.txt
ArchLinux (reproducible in fresh installation with default networking in VM)
Docker
What Happened?
Reproduction steps:
minikube start
minikube node add
minikube addons enable dashboard
watch kubectl get -n kubernetes-dashboard -o wide pod
There is also an error when adding the second node:
However the
minikube start command
logs:which implies that a CNI has been setup (albeit a
bridge
one).Alternatively using
minikube start --cni kindnet
, we still get told that:however when adding another node we still get:
despite the fact that the node now works perfectly and the dashboard comes up.
Solution Suggestions
Attach the log file
log.txt
Operating System
ArchLinux (reproducible in fresh installation with default networking in VM)
Driver
Docker