CIDR change fails

General Discussions microk8s
1

Hey all,

I’ve been trying to change the cidr of my microk8s instance to 192.168.0.0/16. (Our internal network uses 10.0.0.0/8.) But when I get to the point of checking that it’s worked, well, it hasn’t worked.

I’m following the official docs here: MicroK8s - Changing the pods CIDR in a MicroK8s cluster

This is on a Ubuntu 18.04 server. I’m trying to change directly after installing microk8s for the first time.

Here’s a pastebin of my output: failedcidrchange - Pastebin.com

Any ideas?

Thanks in advance!

2

I don’t get it. I tried 172.16.30.0/24 on a different node. It worked.

systemuser@microk8snode2:~$ microk8s kubectl get po -A -o wide
NAMESPACE     NAME                                         READY   STATUS    RESTARTS   AGE     IP              NODE              NOMINATED NODE   READINESS GATES
kube-system   calico-node-w6tc2                            1/1     Running   0          2m11s   10.225.225.8    microk8snode2   <none>           <none>
kube-system   metrics-server-8bbfb4bdb-546db               1/1     Running   0          2m10s   172.16.30.129   microk8snode2   <none>           <none>
kube-system   calico-kube-controllers-f7868dd95-2b8wg      1/1     Running   0          2m10s   172.16.30.133   microk8snode2   <none>           <none>
kube-system   dashboard-metrics-scraper-78d7698477-hbhpn   1/1     Running   0          2m10s   172.16.30.130   microk8snode2   <none>           <none>
kube-system   kubernetes-dashboard-85fd7f45cb-f8pzj        1/1     Running   0          2m10s   172.16.30.131   microk8snode2   <none>           <none>
kube-system   coredns-7f9c69c78c-9hdfv                     1/1     Running   0          2m10s   172.16.30.132   microk8snode2   <none>           <none>

Any idea why?