Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

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.

Close
?
How can I verify that data persists after I recreate the pod?
Write data to /usr/share/nginx/html/index.html in the running NGINX container. Delete and recreate the pod, then use kubectl exec to read the file. If the original content appears, the data persisted on the Longhorn-backed volume.
What network configuration do I need to access the Longhorn web UI?
Add an inbound network security group rule for TCP ports 80, 8080, and 6443. Apply the rule to the VM’s network interface or subnet, then use the VM’s IP address and port 8080 while the Longhorn port-forward command is running.
How do I know K3s and Longhorn are ready to use?
Check that the Kubernetes node reports Ready, the Longhorn pods report Running, and the longhorn StorageClass is available. Confirm that the Longhorn interface also loads in your browser.
Which StorageClass name should I use in my PersistentVolumeClaim?
Set storageClassName: longhorn in your manifest. Your PersistentVolumeClaim should bind when the longhorn StorageClass is available.
What result should I expect when running fio on the Longhorn-backed volume?
Confirm that fio completes without errors and prints throughput, input/output operations per second (IOPS), and latency metrics. Use this output as a baseline for later runs in your environment.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing