Pattern is found but solution not works. cezary@ubuntu64:~$ juju ssh kubernetes-worker/0 -- journalctl --no-pager -o cat -u snap.kubelet.daemon | grep "Failed to start ContainerManager" | wc Connection to 10.251.0.85 closed. 319 12122 103675 After "juju config kubernetes-worker kubelet-extra-config='{protectKernelDefaults: false}'". Errors "Failed to start ContainerManager" removed but it not works again with strange messages. Ubuntu is restarted before test. 0309 17:32:29.088367 12174 kubelet.go:1368] Failed to start ContainerManager [invalid kernel flag: vm/overcommit_memory, expected value: 1, actual value: 0, invalid kernel flag: kernel/panic, expected value: 10, actual value: 0, invalid kernel flag: kernel/panic_on_oops, expected value: 1, actual value: 0] Connection to 10.251.0.85 closed. cezary@ubuntu64:~$ date -u wto, 9 mar 2021, 17:40:13 UTC Strange messages is: "Waiting for 2 kube-system pods to start" only on one master. Full screen: cezary@ubuntu64:~$ juju status Model Controller Cloud/Region Version SLA Timestamp kubernetes localhost-localhost localhost/localhost 2.8.9 unsupported 18:44:17+01:00 App Version Status Scale Charm Store Rev OS Notes containerd 1.3.3 active 5 containerd jujucharms 102 ubuntu easyrsa 3.0.1 active 1 easyrsa jujucharms 345 ubuntu etcd 3.4.5 active 3 etcd jujucharms 553 ubuntu flannel 0.11.0 active 5 flannel jujucharms 518 ubuntu kubeapi-load-balancer 1.18.0 active 1 kubeapi-load-balancer jujucharms 757 ubuntu exposed kubernetes-master 1.20.4 waiting 2 kubernetes-master jujucharms 955 ubuntu kubernetes-worker 1.20.4 active 3 kubernetes-worker jujucharms 726 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0* active idle 0 10.251.0.162 Certificate Authority connected. etcd/0* active idle 1 10.251.0.160 2379/tcp Healthy with 3 known peers etcd/1 active idle 2 10.251.0.124 2379/tcp Healthy with 3 known peers etcd/2 active idle 3 10.251.0.203 2379/tcp Healthy with 3 known peers kubeapi-load-balancer/0* active idle 4 10.251.0.126 443/tcp Loadbalancer ready. kubernetes-master/0* waiting idle 5 10.251.0.74 6443/tcp Waiting for 2 kube-system pods to start containerd/2 active idle 10.251.0.74 Container runtime available flannel/2 active idle 10.251.0.74 Flannel subnet 10.1.77.1/24 kubernetes-master/1 active idle 6 10.251.0.86 6443/tcp Kubernetes master running. containerd/3 active idle 10.251.0.86 Container runtime available flannel/3 active idle 10.251.0.86 Flannel subnet 10.1.88.1/24 kubernetes-worker/0 active idle 7 10.251.0.85 80/tcp,443/tcp Kubernetes worker running. containerd/0* active idle 10.251.0.85 Container runtime available flannel/0* active idle 10.251.0.85 Flannel subnet 10.1.64.1/24 kubernetes-worker/1* active idle 8 10.251.0.19 80/tcp,443/tcp Kubernetes worker running. containerd/4 active idle 10.251.0.19 Container runtime available flannel/4 active idle 10.251.0.19 Flannel subnet 10.1.52.1/24 kubernetes-worker/2 active idle 9 10.251.0.16 80/tcp,443/tcp Kubernetes worker running. containerd/1 active idle 10.251.0.16 Container runtime available flannel/1 active idle 10.251.0.16 Flannel subnet 10.1.92.1/24