![Unable to progress further. Error was observed after issuing the command `kubea . . . - Kubernetes-Slack Discussions - KodeKloud - DevOps Learning Community Unable to progress further. Error was observed after issuing the command `kubea . . . - Kubernetes-Slack Discussions - KodeKloud - DevOps Learning Community](https://kodekloud.com/uploads/db1265/original/2X/a/adbeb9f7c6ef39d8d44970390c7972a0eb94b472.png)
Unable to progress further. Error was observed after issuing the command `kubea . . . - Kubernetes-Slack Discussions - KodeKloud - DevOps Learning Community
![Kubernetes : Spin Up Highly Available Kubernetes Cluster using kubeadm & Setup CNI | Part 3 | by Sarasa Gunawardhana | FAUN — Developer Community 🐾 Kubernetes : Spin Up Highly Available Kubernetes Cluster using kubeadm & Setup CNI | Part 3 | by Sarasa Gunawardhana | FAUN — Developer Community 🐾](https://miro.medium.com/v2/resize:fit:1400/1*RUMhJKM9sxp616Mrp4FTLw.png)
Kubernetes : Spin Up Highly Available Kubernetes Cluster using kubeadm & Setup CNI | Part 3 | by Sarasa Gunawardhana | FAUN — Developer Community 🐾
![Calico periodically has issues initializing due to "dial tcp 172.18.0.1:443: connect: connection refused" errors - Open Source Calico Help - Discuss Calico Calico periodically has issues initializing due to "dial tcp 172.18.0.1:443: connect: connection refused" errors - Open Source Calico Help - Discuss Calico](https://global.discourse-cdn.com/standard10/uploads/calico/original/1X/52410e97d0bf1e8098dcd3fce5d99e428c40be04.png)
Calico periodically has issues initializing due to "dial tcp 172.18.0.1:443: connect: connection refused" errors - Open Source Calico Help - Discuss Calico
![I set my master with "kubeadm init --pod-network-cidr=10.244.0.0/16", flannel is also set with that. Worker pods are being set with "10.244.1.0/16" and they have no network interaction with master pods :/ : I set my master with "kubeadm init --pod-network-cidr=10.244.0.0/16", flannel is also set with that. Worker pods are being set with "10.244.1.0/16" and they have no network interaction with master pods :/ :](https://preview.redd.it/i-set-my-master-with-kubeadm-init-pod-network-cidr-10-244-0-v0-g7sd54bt6a791.png?width=406&format=png&auto=webp&s=f0ca1901934643819681d7c689ad6c942ee0009d)
I set my master with "kubeadm init --pod-network-cidr=10.244.0.0/16", flannel is also set with that. Worker pods are being set with "10.244.1.0/16" and they have no network interaction with master pods :/ :
K8S: convert “kubeadm init” command-line arguments to “–config” YAML-file equivalent · Issue #1825 · kubernetes/kubeadm · GitHub
![Install and configure Kubernetes cluster worker nodes using kubeadm - Part 3 | vGeek - Tales from real IT system Administration environment Install and configure Kubernetes cluster worker nodes using kubeadm - Part 3 | vGeek - Tales from real IT system Administration environment](http://vcloud-lab.com/files/resized/700278/1170;1050;f7f150a4ffeda24f5867a67887bc43e68a7209ee.jpg)