Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Facing microk8s is not running issue.No resources found in default namespace showing for microk8s.kubectl get nodes

See original GitHub issue

I am trying to set up microk8s multi-node cluster on my Centos machine. But when i run microk8s.status it’s showing microk8s is not running. Use microk8s inspect for a deeper inspection and For microk8s.kubectl get nodes is showing No resources found in default namespace. The output of microk8s inspect is

Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-flanneld is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd 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 snap list to the final report tarball
  Copy VM name (or none) 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 current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster

 WARNING:  IPtables FORWARD policy is DROP. Consider enabling traffic forwarding with: sudo iptables -P FORWARD ACCEPT
The change can be made persistent with: sudo apt-get install iptables-persistent
Building the report tarball

snap    2.45.3.1-1.el7
snapd   2.45.3.1-1.el7
series  16
centos  7
kernel  3.10.0-1062.12.1.el7.x86_64

I am using microk8s v1.18.8 1609 1.18/stable canonical✓ classic

Attaching microk8s.inspect tarball inspection-report-20200915_045010.tar.gz

Issue Analytics

State:
Created 3 years ago
Comments:17 (4 by maintainers)

Top GitHub Comments

5reactions

TerminalFincommented, Dec 30, 2020

Thanks a lot @ktsakalozos . That worked. I have reformatted the directory /var/snap and cluster is up now … by the way i did the same on one of my node and node is able to join the cluster now .
NAME    STATUS   ROLES    AGE   VERSION
appz2   Ready    <none>   76m   v1.19.0-34+09a4aa08bb9e93
appz1   Ready    <none>   97m   v1.19.0-34+09a4aa08bb9e93

@ppratheesh What exactly did you do to “reformat” the /var/snap directory? I am having the same problem and want to see if this resolves my issues.

1reaction

ppratheeshcommented, Sep 16, 2020

Thanks a lot @ktsakalozos . That worked. I have reformatted the directory /var/snap and cluster is up now … by the way i did the same on one of my node and node is able to join the cluster now .

NAME    STATUS   ROLES    AGE   VERSION
appz2   Ready    <none>   76m   v1.19.0-34+09a4aa08bb9e93
appz1   Ready    <none>   97m   v1.19.0-34+09a4aa08bb9e93

Top Results From Across the Web

Facing microk8s is not running issue.No resources found in ...

I am trying to set up microk8s multi-node cluster on my Centos machine. But when i run microk8s.status it's showing microk8s is not...

Troubleshooting - MicroK8s

First determine the resource identifier for the pod: microk8s kubectl get pods ... If the problem you are experiencing indicates a problem with...

ibm cloud private - Kubectl : No resource found - Stack Overflow

In the default installation of ICP4D, there are no pods deployed on 'default' namespace and hence you get "no resources found" cause if...

Learn Kubernetes 101 - Part 1 - Using Namespaces

microk8s kubectl get pods. You should get the message "No resources found in default namespace." Change the namespace from default to production.

How to Setup Prometheus Monitoring On Kubernetes Cluster

First, we will create a Kubernetes namespace for all our monitoring components. If you don't create a dedicated namespace, all the Prometheus kubernetes...