root@sunbeam:~# sudo microk8s.kubectl get po -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-864597b5fd-zl5h5 0/1 Pending 0 37m
kube-system hostpath-provisioner-7df77bc496-w2mcd 0/1 Pending 0 32m
metallb-system controller-5f7bb57799-7jdmf 0/1 Pending 0 32m
root@sunbeam:~# sudo snap services microk8s
Service Startup Current Notes
microk8s.daemon-apiserver-kicker enabled active -
microk8s.daemon-apiserver-proxy enabled inactive -
microk8s.daemon-cluster-agent enabled active -
microk8s.daemon-containerd enabled active -
microk8s.daemon-etcd enabled inactive -
microk8s.daemon-flanneld enabled inactive -
microk8s.daemon-k8s-dqlite enabled active -
microk8s.daemon-kubelite enabled active -
I'm not aware of any blacklist on our proxy, so that shouldn't be an issue. The report is attached. I'm wondering if I should have "predicted" the ClusterIP (10.152.183.1) and added that to the no-proxy as well. In one of the previous attempts I *believe* I saw that it was added to no-proxy, but I'm not sure. I'm currently trying to tear it down with 'sunbeam cluster remove' but it's stuck as well. So maybe I'll need to rollback the snapshot.
root@sunbeam:~# sudo microk8s.kubectl get po -A 864597b5fd- zl5h5 0/1 Pending 0 37m provisioner- 7df77bc496- w2mcd 0/1 Pending 0 32m 5f7bb57799- 7jdmf 0/1 Pending 0 32m
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-
kube-system hostpath-
metallb-system controller-
root@sunbeam:~# sudo snap services microk8s daemon- apiserver- kicker enabled active - daemon- apiserver- proxy enabled inactive - daemon- cluster- agent enabled active - daemon- containerd enabled active - daemon- etcd enabled inactive - daemon- flanneld enabled inactive - daemon- k8s-dqlite enabled active - daemon- kubelite enabled active -
Service Startup Current Notes
microk8s.
microk8s.
microk8s.
microk8s.
microk8s.
microk8s.
microk8s.
microk8s.
I'm not aware of any blacklist on our proxy, so that shouldn't be an issue. The report is attached. I'm wondering if I should have "predicted" the ClusterIP (10.152.183.1) and added that to the no-proxy as well. In one of the previous attempts I *believe* I saw that it was added to no-proxy, but I'm not sure. I'm currently trying to tear it down with 'sunbeam cluster remove' but it's stuck as well. So maybe I'll need to rollback the snapshot.