K8S Master CoreDNS pods CrashLoopBackOff with Calico CNI

Bug #1939386 reported by Alexey Tsitsin
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Calico Charm
New
Undecided
Unassigned

Bug Description

Running:
calico 812
kubernetes-master 1034
kubernetes-worker 788

kubernetes 1.21.3

juju deploy charmed-kubernetes --overlay calico-overlay.yml

calioco-overlay.yml

description: Charmed Kubernetes overlay to add Calico CNI.
applications:
  calico:
    annotations:
      gui-x: '480'
      gui-y: '750'
    charm: cs:~containers/calico
    options:
      cidr: 10.150.0.0/16
  flannel:
relations:
- - calico:etcd
  - etcd:db
- - calico:cni
  - kubernetes-master:cni
- - calico:cni
  - kubernetes-worker:cni

All charmes are running. Hower calico won't show the version:

App Version Status Scale Charm Store Channel Rev OS Message
calico active 5 calico charmstore stable 812 ubuntu Calico is active
containerd go1.13.8 active 5 containerd charmstore stable 146 ubuntu Container runtime available
easyrsa 3.0.1 active 1 easyrsa charmstore stable 395 ubuntu Certificate Authority connected.
etcd 3.4.5 active 3 etcd charmstore stable 607 ubuntu Healthy with 3 known peers
kubeapi-load-balancer 1.18.0 active 1 kubeapi-load-balancer charmstore stable 814 ubuntu Loadbalancer ready.
kubernetes-master 1.21.3 active 2 kubernetes-master charmstore stable 1034 ubuntu Kubernetes master running.
kubernetes-worker 1.21.3 active 3 kubernetes-worker charmstore stable 788 ubuntu Kubernetes worker running.

$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
ingress-nginx-kubernetes-worker default-http-backend-kubernetes-worker-cd9b77777-gsvlg 1/1 Running 0 12h
ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-nstrd 1/1 Running 0 12h
ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-shqtk 1/1 Running 0 12h
ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-v5wvb 1/1 Running 0 12h
kube-system calico-kube-controllers-865b566cc7-vs7wc 1/1 Running 0 12h
kube-system coredns-6f867cd986-lc8n9 0/1 CrashLoopBackOff 135 12h
kube-system kube-state-metrics-7799879d89-jqdjq 0/1 CrashLoopBackOff 238 12h
kube-system metrics-server-v0.3.6-7d66499544-8vc7q 1/2 CrashLoopBackOff 143 12h
kubernetes-dashboard dashboard-metrics-scraper-8458d7fdf6-vzdrz 1/1 Running 0 12h
kubernetes-dashboard kubernetes-dashboard-5784589f96-brg4w 0/1 CrashLoopBackOff 147 12h

Warning FailedCreatePodSandBox 26m kubelet Failed to create pod sandbox: rpc error: code = Unknown des
c = failed to setup network for sandbox "55196a9be8653c48e315c0bacbdd31d8acef322eb6ad6296d8fab1298ff62415": namespaces "kube-system"
is forbidden: User "system:node:juju-a3aebe-k8s-8" cannot get resource "namespaces" in API group "" in the namespace "kube-system"

Warning Unhealthy 45m (x759 over 11h) kubelet Readiness probe failed: Get "http://10.150.95.132:8181/ready": dial tcp 10.150.95.132:8181: connect: connection refused

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.