storage enabled but no persistent volume found in cluster

v1.12.2

inspection-report-20181115_174033.tar.gz

I have enabled storage microk8s.enable storage however, microk8s.kubectl get pv shows “No resources found”. As a result, all the PVCs are in pending state. Please advise. THanks!

[ktsakalozos]

Hi @khteh ,

microk8s.enable storage will set a default storage class as you can see here (get pv is expected to be empty):

> microk8s.kubectl get sc
NAME                          PROVISIONER            AGE
microk8s-hostpath (default)   microk8s.io/hostpath   62s

Can you make sure that microk8s.kubectl get all -n kube-system reports back a deployment.apps/hostpath-provisioner and a corresponding pod? For some reason the microk8s.inspect report you attached does not include the kubectl get all output as if your api server is not running.

Here is a PVC we use during our testing https://github.com/ubuntu/microk8s/blob/master/tests/templates/pvc.yaml

Would would you like to share a minimal PVC that is failing for you?

Thank you for using microk8s and for opening this issue.

[ktsakalozos]

@khteh, first restart microk8s to make sure all services are up:

sudo snap disable microk8s
sudo snap enable microk8s

Wait a few seconds so that all services have initialized and try a microk8s.kubectl get all --all-namespaces to get the status of all pods services deployments running on your microk8s. Do also a microk8s.kubectl get no to see if your node has registered with the apiserver.

microk8s.inspect will run through all the services and tell you if anyone is failing.

Could you share the full set of manifests you are applying or at least a complete minimal example of a setup that is failing?

Finally, you should know that microk8s is using most of the upstream kubernetes binaries found in https://github.com/kubernetes/kubernetes. And I agree with your point that kubernetes by itself is hard to setup; this is exactly what microk8s solves.