Merge pull request #3335 from odidev/openebs

Deploy OpenEBS on Azure Cobalt 100 Arm64 virtual machines for Kubernetes-native persistent storage

Author: pareenaverma

content/learning-paths/servers-and-cloud-computing/openebs-cobalt/_index.md

@@ -0,0 +1,73 @@
+---
+title: Deploy OpenEBS on Azure Cobalt 100 Arm64 virtual machines for Kubernetes-native persistent storage
+
+draft: true
+cascade:
+    draft: true
+
+description: Learn how to install and configure OpenEBS LocalPV on an Azure Cobalt 100 Arm64 virtual machine using K3s Kubernetes, provision persistent storage dynamically, deploy stateful applications, and validate persistent storage functionality.
+   
+minutes_to_complete: 60
+
+who_is_this_for: This is an introductory topic for DevOps engineers, platform engineers, cloud-native developers, and Kubernetes administrators who want to deploy lightweight Kubernetes-native persistent storage on Arm-based cloud infrastructure.
+
+learning_objectives:
+    - Install and configure K3s Kubernetes on Azure Cobalt 100 Arm64 virtual machines
+    - Deploy OpenEBS LocalPV using Helm
+    - Configure Kubernetes storage classes and Persistent Volume Claims (PVCs)
+    - Deploy and validate stateful Kubernetes workloads with persistent storage
+
+prerequisites:
+  - A [Microsoft Azure account](https://azure.microsoft.com/) with access to Cobalt 100 based instances (Dpsv6)
+  - Basic knowledge of Linux command-line operations
+  - Familiarity with SSH and remote server access
+  - Basic understanding of Kubernetes concepts and containerized applications
+
+author: Pareena Verma
+
+### Tags
+skilllevels: Introductory
+subjects: Containers and Virtualization
+cloud_service_providers:
+  - Microsoft Azure
+
+armips:
+    - Neoverse
+
+tools_software_languages:
+    - Kubernetes
+    - K3s
+    - OpenEBS
+    - Helm
+
+operatingsystems:
+    - Linux
+
+further_reading:
+  - resource:
+      title: OpenEBS Official Website
+      link: https://openebs.io/
+      type: website
+  - resource:
+      title: OpenEBS Documentation
+      link: https://openebs.io/docs
+      type: documentation
+  - resource:
+      title: K3s Documentation
+      link: https://docs.k3s.io/
+      type: documentation
+  - resource:
+      title: Kubernetes Documentation
+      link: https://kubernetes.io/docs/
+      type: documentation
+  - resource:
+      title: Azure Cobalt 100 processors
+      link: https://techcommunity.microsoft.com/blog/azurecompute/announcing-the-preview-of-new-azure-vms-based-on-the-azure-cobalt-100-processor/4146353
+      type: documentation
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1
+layout: "learningpathall"
+learning_path_main_page: "yes"
+---

content/learning-paths/servers-and-cloud-computing/openebs-cobalt/_next-steps.md

@@ -0,0 +1,8 @@
+---
+# ================================================================================
+#       FIXED, DO NOT MODIFY THIS FILE
+# ================================================================================
+weight: 21                  # Set to always be larger than the content in this path to be at the end of the navigation.
+title: "Next Steps"         # Always the same, html page title.
+layout: "learningpathall"   # All files under learning paths have this same wrapper for Hugo processing.
+---

content/learning-paths/servers-and-cloud-computing/openebs-cobalt/background.md

@@ -0,0 +1,66 @@
+---
+title: Understand OpenEBS on Azure Cobalt 100
+weight: 2
+
+layout: "learningpathall"
+---
+
+## Why run OpenEBS on Azure Cobalt 100
+
+OpenEBS on Arm-based Azure Cobalt 100 processors provides lightweight, Kubernetes-native persistent storage for cloud-native workloads. Azure Cobalt 100 processors deliver dedicated physical cores per vCPU, enabling consistent and predictable performance for Kubernetes storage operations and stateful applications.
+
+OpenEBS integrates directly with Kubernetes and dynamically provisions Persistent Volumes for applications using Container Storage Interface (CSI) drivers and storage engines. Running OpenEBS on Azure Cobalt 100 enables efficient Arm64-native Kubernetes storage deployments optimized for lightweight cloud-native environments.
+
+## Azure Cobalt 100 Arm-based processor
+
+Azure’s Cobalt 100 is Microsoft’s first-generation, in-house Arm-based processor. Built on Arm Neoverse N2, Cobalt 100 is a 64-bit CPU that delivers strong performance and energy efficiency for cloud-native, scale-out Linux workloads. These workloads include web and application servers, data analytics, open-source databases, and caching systems. Running at 3.4 GHz, Cobalt 100 allocates a dedicated physical core for each vCPU, ensuring consistent and predictable performance.
+
+To learn more, see the Microsoft blog [Announcing the preview of new Azure VMs based on the Azure Cobalt 100 processor](https://techcommunity.microsoft.com/blog/azurecompute/announcing-the-preview-of-new-azure-vms-based-on-the-azure-cobalt-100-processor/4146353).
+
+## How OpenEBS improves Kubernetes storage
+
+OpenEBS is an open-source, Kubernetes-native storage platform designed for stateful workloads running inside Kubernetes clusters. Unlike traditional external storage systems, OpenEBS runs completely inside Kubernetes and dynamically provisions storage volumes directly through Kubernetes APIs.
+
+OpenEBS enables applications to retain persistent data even after pods restart, reschedule, or recreate. This makes OpenEBS ideal for databases, analytics platforms, message queues, and other stateful cloud-native applications.
+
+To learn more, see the official [OpenEBS documentation](https://openebs.io/docs).
+
+OpenEBS provides key capabilities for Kubernetes-native storage management:
+
+- Dynamic Provisioning: Automatically creates Persistent Volumes using Kubernetes Persistent Volume Claims (PVCs).
+- Kubernetes-native Architecture: Runs entirely inside Kubernetes without requiring external storage appliances.
+- Lightweight Local Storage: OpenEBS LocalPV uses node-local storage optimized for lightweight Kubernetes environments.
+- CSI Integration: Integrates with Kubernetes Container Storage Interface (CSI) drivers for standard storage management.
+- Stateful Workload Support: Enables persistent storage for databases, web applications, and distributed systems.
+
+## Why OpenEBS LocalPV for this learning path
+
+This learning path uses OpenEBS LocalPV because it is optimized for:
+
+- Single-node Kubernetes clusters
+- Arm64 environments
+- Lightweight Kubernetes deployments
+- Development and learning environments
+- High-performance local storage provisioning
+
+Advanced replicated storage engines such as Mayastor are designed for multi-node production environments and are intentionally excluded from this setup.
+
+## Learning path overview
+
+In this Learning Path, you'll deploy OpenEBS LocalPV on an Azure Cobalt 100 Arm64 virtual machine using a lightweight K3s Kubernetes cluster.
+
+You'll learn how to:
+
+- Install Kubernetes using K3s
+- Deploy OpenEBS LocalPV
+- Configure Kubernetes storage classes
+- Create Persistent Volume Claims (PVCs)
+- Deploy stateful applications
+- Validate persistent storage functionality
+- Expose Kubernetes applications externally using Azure networking
+
+## What you've learned and what's next
+
+You now understand why Azure Cobalt 100 and OpenEBS are a strong combination for lightweight Kubernetes-native persistent storage on Arm64 infrastructure.
+
+Next, you'll configure Azure networking to allow external access to the Kubernetes application deployed with OpenEBS persistent storage.

content/learning-paths/servers-and-cloud-computing/openebs-cobalt/firewall.md

@@ -0,0 +1,73 @@
+---
+title: Allow access to the OpenEBS application on Azure
+weight: 5
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+## Configure external traffic for the OpenEBS application
+
+To allow external traffic to the Kubernetes application running with OpenEBS persistent storage on an Azure virtual machine, open the Kubernetes NodePort in the Network Security Group (NSG).
+
+The NSG can be attached to the virtual machine's network interface or subnet.
+
+{{% notice Note %}}For more information about Azure setup, see [Getting started with Microsoft Azure Platform](/learning-paths/servers-and-cloud-computing/csp/azure/).{{% /notice %}}
+
+## Verify the Kubernetes service
+
+Check the Kubernetes service to identify the exposed NodePort:
+
+```bash
+kubectl get svc
+```
+
+The output is similar to:
+
+```output
+NAME            TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)
+nginx-openebs   NodePort    10.x.x.x        <none>        80:31635/TCP
+```
+
+In this example, the NodePort exposed externally is  `31635`.
+
+### Add an inbound firewall rule in Azure
+
+To expose the Kubernetes NodePort externally, create a firewall rule.
+
+1. Navigate to the [Azure portal](https://portal.azure.com), go to **Virtual Machines**, and select your virtual machine.
+
+![Azure Portal Virtual Machines page with the target VM selected. Check that you are opening the correct virtual machine before configuring its network access.#center](images/virtual_machine.png "Virtual Machines")
+
+2. In the left menu, select **Networking**, then select **Network settings**.
+
+![Azure Portal Networking page showing the network settings linked to the virtual machine. Use this entry to reach the Network Security Group settings for the inbound rule.#center](images/networking.png "Network settings")
+
+3. Navigate to **Create port rule**, and select **Inbound port rule**.
+
+![Azure Portal Create port rule menu with Inbound port rule selected. Choose this option to open port 31635 to expose the Kubernetes Node Port Externally.#center](images/port_rule.png "Create rule")
+
+4. Configure the inbound security rule with the following settings:
+
+- **Source:** My IP address  
+- **Source IP addresses:** *(auto-populated with your current public IP)*  
+- **Source port ranges:** *  
+- **Destination:** Any  
+- **Destination port ranges:** **31635**  
+- **Protocol:** TCP  
+- **Action:** Allow  
+- **Name:** allow-openebs-port
+
+{{% notice Note %}}Setting Source to My IP address restricts access to the Kubernetes application to your current machine only. Source port ranges remains * because this refers to the client's ephemeral outbound port, which is dynamically assigned. If your IP address changes or you need to access the application from another machine, update the source IP in this rule.{{% /notice %}}
+
+5. After filling in the details, select **Add** to save the rule.
+
+You can now access the Kubernetes application externally using the NodePort.
+
+## What you've learned and what's next
+
+You've now configured the Azure Network Security Group to allow external access to the Kubernetes application running with OpenEBS LocalPV persistent storage.
+
+This firewall rule enables external browser access to the application deployed on your single-node Kubernetes cluster running on Azure Cobalt 100 Arm64.
+
+Next, you'll install OpenEBS LocalPV on Kubernetes and configure persistent storage provisioning for stateful workloads.