Zero-ops scaling Kubernetes storage with MicroK8s and OpenEBS Mayastor ... If you are using Ubuntu, the quickest way to get started is to install MicroK8s directly from the snap store by clicking the "Install" button. Setup an NFS server 2. Early versions of MicroK8s do not support Storage when RBAC is enabled. You can do this by first finding a list of names: kubectl get pvc --all-namespaces MicroK8s is a Kubernetes distribution from Canonical. $ microk8s .kubectl describe -n kube-system pod/hostpath-provisioner- 7 b 9 cb 5 cdb 4 -q 5 jh 9 Name : hostpath-provisioner- 7 b 9 cb 5 cdb 4 -q 5 jh 9 Namespace : kube-system Priority : 0 Node : . Edit your persistent volume claim using kubectl edit pvc -n and increase the value found for storage: to the value needed. Kubernetes (5) Local Persistent Volumes - A Step-by-Step Tutorial Search: Microk8s Persistent Volume. 15 are quotas for ephemeral storage, extended data sources for persistent volume claims, dynamic persistent volume resizing, and more. A cluster administrator creates a PersistentVolume that is backed by physical storage. This means that the data that lives in the persistent volume will not be lost if a pod fails for some reason, and then needs to be spun up again by the Kubernetes controller. Step 5: Create a test Claim and Pod on Kubernetes. Ubuntu 20.04 LTS : MicroK8s : Enable Storage : Server World For more information, refer to the Dynamic provisioning section in the Red Hat OpenShift documentation. On MicroK8s you have to enable the OpenEBS Add-on so claims will be bound to storage. Create the Kubernetes namespaces and a secret for the MySQL password (main.yml) Pods can request specific levels of resources (CPU and Memory). This is where Persistent Volumes and Persistent Volume Claims come in. MicroK8s. For these steps we are using the latest Ubuntu 21.10 Server and AWX-Operator 0.15.0. . Persistent Volume Microk8s [8H7B34] It is similar to a Pod. This is because the 'make deploy' step was . Dynamic Persistent Volumes with OpenEBS Pods consume node resources and PVCs consume PV resources. Persistent-Volume.yaml. They request the storage resources that your deployment needs. It runs on Ubuntu and is advertised as a lightweight Kubernetes distribution, offering high availability and automatic updates. CentOS 8 : MicroK8s : Enable Storage : Server World $ vim ceph-rbd-claim.yml kind: PersistentVolumeClaim apiVersion: v1 metadata: name: ceph-rbd-claim1 spec: accessModes: - ReadWriteOnce storageClassName: ceph-rbd resources: requests: storage: 1Gi . PVs are volume plugins like Volumes, but have a lifecycle independent of any individual Pod that uses the PV. Look again at the PersistentVolume: kubectl get pv task-pv-volume Storage is abstracted as PersistentVolumes (a volume that is provisioned in the underlying infrastructure) and PersistentVolumeClaims (a claim for a pod that uses a persistent volume) resources. microk8s.enable storage You'll need to delete your deployment and start again. I will now create a simple nginx pod with a persistent volume claim that should be automatically allocated storage from my zfspool. Create a StorageClass for NFS 4. it is likely that it is failing to get a persistent volume claim. PV (Persistent Volume) capacity is less than PVC (Persistent Volume Claim) Total number of PVC (Persistent Volume Claim) is higher than PV (Persistent Volume) nodeAffinity of the PV is missing Clean up the OLD PV (Persistent Volume) and PVC (Persistent Volume Claim) How to identify the issue?