You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created my cluster several times in microk8s but after 2 or 3 weeks the master node stops working well, only the service does not start and neither do the nodes, it works fine for a while, I have made the tarball and I have inspected it but I cannot find nothing specific:
1.- microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.
4.- microk8s.inspect (all is running):
Inspecting system
Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-kubelite is running
Service snap.microk8s.daemon-k8s-dqlite is running
Service snap.microk8s.daemon-apiserver-kicker is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
Copy processes list to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy openSSL information to the final report tarball
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy current linux distribution to the final report tarball
Copy asnycio usage and limits to the final report tarball
Copy inotify max_user_instances and max_user_watches to the final report tarball
Copy network configuration to the final report tarball
Inspecting kubernetes cluster
Inspect kubernetes cluster
Inspecting dqlite
Inspect dqlite
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have created my cluster several times in microk8s but after 2 or 3 weeks the master node stops working well, only the service does not start and neither do the nodes, it works fine for a while, I have made the tarball and I have inspected it but I cannot find nothing specific:
1.- microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.
2.- error: Get “https://127.0.0.1:16443/api/v1/namespaces/kube-system/services?labelSelector=kubernetes.io%2Fcluster-service%3Dtrue”: dial tcp 127.0.0.1:16443: connect: connection refused - error from a previous attempt: unexpected EOF
3.- microk8s kubectl logs -n kube-system -l component=kube-apiserver
error: Get “https://127.0.0.1:16443/api/v1/namespaces/kube-system/pods?labelSelector=component%3Dkube-apiserver”: dial tcp 127.0.0.1:16443: connect: connection refused - error from a previous attempt: unexpected EOF
4.- microk8s.inspect (all is running):
Inspecting system
Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-kubelite is running
Service snap.microk8s.daemon-k8s-dqlite is running
Service snap.microk8s.daemon-apiserver-kicker is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
Copy processes list to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy openSSL information to the final report tarball
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy current linux distribution to the final report tarball
Copy asnycio usage and limits to the final report tarball
Copy inotify max_user_instances and max_user_watches to the final report tarball
Copy network configuration to the final report tarball
Inspecting kubernetes cluster
Inspect kubernetes cluster
Inspecting dqlite
Inspect dqlite
inspection-report.zip
The text was updated successfully, but these errors were encountered: