Deploy OpenEBS storage for Kubernetes on Azure Cobalt 100
Introduction
Explore OpenEBS storage for Kubernetes on Azure Cobalt 100
Create an Arm64 virtual machine powered by Azure Cobalt 100
Deploy OpenEBS on an Arm-based virtual machine
Validate OpenEBS storage on an Arm VM
Allow access to the OpenEBS application on Azure
Next Steps
Deploy OpenEBS storage for Kubernetes on Azure Cobalt 100
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Run
helm search repo openebs/openebs --versions to list available chart versions, then add --version <version> to the provided helm install command. Without this option, you install the latest available chart.Expose the NGINX deployment as a NodePort service and run
kubectl get svc to see the assigned port. Then add an inbound rule for that NodePort in the VM’s Network Security Group.Use
storageClassName: openebs-hostpath and accessModes: ReadWriteOnce as shown in the PersistentVolumeClaim manifest. This configuration targets OpenEBS LocalPV for dynamic provisioning.Write data to the mounted volume in the NGINX pod, delete the pod, and let it recreate. If the data is still present after the pod comes back, the volume is persisting as expected.
No. Use a lightweight single-node Kubernetes cluster with K3s on the VM.