You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kops version are you running? use kops version
Version 1.8.0-alpha.2 (master)
What Kubernetes version are you running? use kubectl version
1.6.7
What cloud provider are you using?
aws
What commands did you execute (Please provide cluster manifest kops get --name my.example.com, if available) and what happened after commands executed?
What you expected to happen:
A working cluster, masters never come online.
How can we to reproduce it (as minimally and precisely as possible):
kops create command above, the cluster never comes online.
Anything else do we need to know:
Looks like calico is configured, api server, kube-scheduler, etcd, kube-proxy and protokube all start. Calico cni and calico node both start up but kubelet is still flooding with errors:
Oct 24 12:47:55 ip-10-25-49-17 kubelet[4401]: W1024 12:47:55.106178 4401 cni.go:157] Unable to update cni config: No networks found in /etc/cni/net.d/
Oct 24 12:47:55 ip-10-25-49-17 kubelet[4401]: E1024 12:47:55.107313 4401 kubelet.go:2067] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized```
root@ip-10-25-49-17:/var/log# ls -lah /etc/cni/net.d/
total 16K
drw-r--r-- 2 root root 4.0K Oct 24 12:35 .
drwxr-xr-x 3 root root 4.0K Oct 24 12:33 ..
-rw-rw-r-- 1 root root 1.5K Oct 24 12:35 10-calico.conflist
-rw-r--r-- 1 root root 273 Oct 24 12:35 calico-kubeconfig
mikesplain
changed the title
cni config uninitialized in k8s 1.6.7 and kops master
calico cni config uninitialized in k8s 1.6.7 and kops master
Oct 24, 2017
Thanks for submitting an issue!
-------------BUG REPORT --------------------
Fill in as much of the template below as you can.
What kops version are you running? use
kops version
Version 1.8.0-alpha.2 (master)
What Kubernetes version are you running? use
kubectl version
1.6.7
What cloud provider are you using?
aws
What commands did you execute (Please provide cluster manifest
kops get --name my.example.com
, if available) and what happened after commands executed?A working cluster, masters never come online.
kops create command above, the cluster never comes online.
Looks like calico is configured, api server, kube-scheduler, etcd, kube-proxy and protokube all start. Calico cni and calico node both start up but kubelet is still flooding with errors:
The text was updated successfully, but these errors were encountered: