Day 60: Persistent Volumes and IP Configuration
Day 60 of DevOps, Day 10 of Azure. Both tasks today had an object in the middle that the task never names. A pod does not mount a PersistentVolume; it mounts a claim, and the claim finds the volume. A VM does not hold a public IP; an IP configuration on its network interface does. One Kubernetes task, one Azure task. Give a web server pod storage that outlives it, then attach an existing public…
Day 60 brought two tasks in DevOps and Azure. The first task focused on providing persistent storage for a Kubernetes pod. A 3Gi PersistentVolume, named pv-xfusion, was created on a host path. A claim, pvc-xfusion, was then created, which found the volume based on shared storageClassName, compatible access mode, and sufficient capacity.
The claim was mounted within a pod called pod-xfusion, which ran the httpd:latest image. The pod was then exposed through a NodePort Service, web-xfusion, on port 30008. The data persisted even after the pod's deletion, proving that the volume and claim outlived the pod.
The second task involved attaching an existing public IP, devops-pip, to a virtual machine. This task demonstrated the configuration of a VM's network interface, which holds the public IP, as opposed to the VM itself.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
