Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

calico cni config uninitialized in k8s 1.6.7 and kops master #3694

Closed
mikesplain opened this issue Oct 24, 2017 · 1 comment
Closed

calico cni config uninitialized in k8s 1.6.7 and kops master #3694

mikesplain opened this issue Oct 24, 2017 · 1 comment

Comments

@mikesplain
Copy link
Contributor

mikesplain commented Oct 24, 2017

Thanks for submitting an issue!

-------------BUG REPORT --------------------

  1. Fill in as much of the template below as you can.

  2. What kops version are you running? use kops version
    Version 1.8.0-alpha.2 (master)

  3. What Kubernetes version are you running? use kubectl version
    1.6.7

  4. What cloud provider are you using?
    aws

  5. What commands did you execute (Please provide cluster manifest kops get --name my.example.com, if available) and what happened after commands executed?

kops create cluster \
        --zones us-east-1a \
        --master-zones us-east-1a \
        --networking calico \
        --name ${CLUSTER_NAME} \
        --node-size m4.large \
        --master-size m4.large \
        --ssh-public-key ~/.ssh/key.pub \
        --network-cidr 10.25.0.0/16 \
        --kubernetes-version=1.6.7
  1. What you expected to happen:
    A working cluster, masters never come online.
  2. How can we to reproduce it (as minimally and precisely as possible):
    kops create command above, the cluster never comes online.
  3. 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
root@ip-10-25-49-17:/var/log# cat /etc/cni/net.d/10-calico.conflist
{
  "name": "k8s-pod-network",
  "cniVersion": "0.3.0",
  "plugins": [
    {
      "type": "calico",
      "etcd_endpoints": "http://etcd-a.internal.kops.dev.redacted.com:4001",
      "log_level": "info",
      "ipam": {
        "type": "calico-ipam"
      },
      "policy": {
        "type": "k8s",
        "k8s_api_root": "https://redacted:443",
        "k8s_auth_token": "redacted"
      },
      "kubernetes": {
        "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"
      }
    },
    {
      "type": "portmap",
      "snat": true,
      "capabilities": {"portMappings": true}
    }
  ]
}
@mikesplain 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
@mikesplain
Copy link
Contributor Author

This is fixed in the beta so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant