Deploying MicroK8s. Mac Cloud Hosting & Virtualization - Articles & Guides | MacStadium Blog The claim name (storage-claim here) uniquely identifies the specific claim within the current namespace and makes it available as a volume named persistent-volume here. Volume Persistent Microk8s [DP348V] # name: persistentVolume: ## If true, VerneMQ will create/use a Persistent Volume Claim ## If false, use local directory enabled: enable ## VerneMQ data Persistent Volume access modes ## Must match those of existing PV or dynamic provisioner ## Ref . Setup an NFS server 2. . Running the UniFi Network Application on Kubernetes MicroK8s Persist Volume Claim as the name sounds is basically a claim for Persistent Volume. A PersistentVolumeClaim (PVC) is a request for storage by a user. Create the Kubernetes namespaces and a secret for the MySQL password (main.yml) After you create the PersistentVolumeClaim, the Kubernetes control plane looks for a PersistentVolume that satisfies the claim's requirements. # Create PV --> it is static provisioning (set up manually . Step 5: Create a test Claim and Pod on Kubernetes. Microk8s Volume Persistent [T50LWX] How to setup MicroK8s with RBAC and Storage - igy.cx This is because the 'make deploy' step was . Retain - if pod is deleted, PV is still there + no other PVC will be given this PV, unless the content in PV are deleted (DEFAULT) but it fails for hostpath because 0 host_path deleter only support /tmp. When using Ubuntu, I'd prefer to stick with MicroK8s as it is set up as a snap install or an option when installing Ubuntu from a disk image. Next step. I am going to create an . NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-d23a629b-67e9-4cc1-b0b6-dde3a8c60ddf 1Gi RWO Delete Bound default/my-pvc microk8s-hostpath 5s [root@dlp ~]# microk8s kubectl get pvc You may also need to manually delete the "pending" PersistentVolumeClaims because I found that uninstalling the Helm chart which created them didn't clear the PVCs out.