Kubernetes applications often need persistent storage to keep data even when containers restart or are recreated. Kubernetes provides Persistent Volumes (PV) and Persistent Volume Claims (PVC) to manage this storage. In this practical lab, we will create a PersistentVolume, create a PersistentVolumeClaim, attach the PVC to an Nginx Pod, and use a node’s /mnt/data directory as persistent storage through hostPath. What You Will Learn In this practical, we will understand:
Tag: YAML
Kubernetes provides several powerful mechanisms for managing application configuration, sensitive information, containers, and access to the Kubernetes API. In this hands-on practice, I worked through: This article documents the complete workflow step by step. 1. Checking Existing ConfigMaps I started by checking the ConfigMaps already available in the namespace. Flow A ConfigMap is used to store non-sensitive configuration data separately from application code. 2. Creating a ConfigMap with Literal Values
Category: Kubernetes, CKA, ReplicaSet, Labels, Selectors Introduction One of the biggest improvements of ReplicaSet over the old ReplicationController is its more expressive label selectors. ReplicationController supports only simple equality-based selectors such as: ReplicaSet introduces set-based selectors, allowing you to create much more flexible selection rules using matchExpressions. In this hands-on lab, we’ll explore all four ReplicaSet selector operators: We’ll also verify each operator by changing Pod labels and observing ReplicaSet’s