Challenge, Medium,  on  Kubernetes

Bind a PersistentVolume to a Specific Node Using Node Affinity

Scenario

Create a PersistentVolume named secure-pv with a capacity of 1Gi, using the hostPath volume type at /mnt/secure-data. Set the storageClassName to local-path, add the label app=secure-data, and configure the nodeAffinity using the key kubernetes.io/hostname so that it is available only on node-02.

Create a PersistentVolumeClaim named secure-pvc requesting 1Gi with ReadWriteOnce access mode and local-path StorageClass. Use a label selector app=secure-data and set volumeName to bind it directly to the correct PersistentVolume.

Finally, confirm that the PersistentVolumeClaim is successfully bound to the PersistentVolume.

After the PVC is bound, deploy the pod using the manifest located at:

/home/laborant/pod-bind-vol.yaml

This pod will mount the PersistentVolume and create data to verify the storage is working correctly.

# Check the data on node-02.
cat /mnt/secure-data/info.txt
Hint
  • PV: Use nodeAffinity with kubernetes.io/hostname: node-02, label app: secure-data, storageClass local-path
  • PVC: Set volumeName: secure-pv, selector.matchLabels.app: secure-data, storageClass local-path
  • Deploy: kubectl apply -f /home/laborant/pod-bind-vol.yaml
  • PersistentVolumes
  • PersistentVolumeClaims

🧪 Test Cases

How to Author Challenges on iximiuz Labs

Instead of providing a subpar online editing experience, iximiuz Labs offers a helper CLI tool called labctl, allowing you to use your favorite text editor (or a full-featured IDE) to write content from the comfort of your local machine.

Install labctl CLI

curl -sf https://labs.iximiuz.com/cli/install.sh | sh

This will download and install the latest version of the labctl CLI. You only need to do this once per workstation.

Authorize labctl

labctl auth login

This will open a browser window asking you to authorize labctl to access your account. You need to do it after a fresh install of labctl and repeat it whenever the auth session expires.

Pull challenge content

labctl content pull challenge bind-a-persistent-volume-to-a-specific-node-using-node-affinity-09e4d506

This will create a local copy of the challenge content in a directory named bind-a-persistent-volume-to-a-specific-node-using-node-affinity-09e4d506. You only need to do this once per challenge.

Stream your changes

labctl content push -fw challenge bind-a-persistent-volume-to-a-specific-node-using-node-affinity-09e4d506

Run this command in a separate terminal to continuously upload your changes to the server while editing the challenge in your favorite text editor or IDE.

You can also use labctl to create, list, and delete your content. Learn more about the available commands: labctl content --help

Start challenge