CKA 2025 MOCK Q-01 Storage Class

🔶 Question 1: 

Task:
Create a StorageClass named csi-retain-sc with the following specifications:

  • Use provisioner: csi-driver.example-vendor.example

  • Set this class as the default

  • Set reclaimPolicy to Retain

  • Allow volume expansion

  • Add mount option discard

  • Use WaitForFirstConsumer as the volumeBindingMode

✅ Save this configuration to a file named sc-default-retain.yaml and apply it.

🔶 Question 2: 

Task:
You already have a default StorageClass named old-default.
You created a new class fast-csi (already applied) but forgot to mark it as default.

  • Patch fast-csi to be the default StorageClass.

  • Remove the default annotation from old-default.

🔶 Question 3: 

Task:
Create a StorageClass named perf-csi-sc using the same csi-driver.example-vendor.example provisioner but do not make it default.

It must:

  • Allow volume expansion

  • Include the parameter guaranteedReadWriteLatency: "true"

  • Use Immediate volumeBindingMode

  • Use Delete as reclaimPolicy

✅ Save as sc-perf.yaml and apply.

🔶 Question 4: 

Task:
Run a command to identify which StorageClass is currently set as default.

✅ Provide the kubectl command output showing the correct storageclass.kubernetes.io/is-default-class annotation.

🔶 Question 5: 

1. Create a new StorageClass named `cluster-one` with:

   - `rancher.io/local-path'

   - `volumeBindingMode: WaitForFirstConsumer`

2. Mark `cluster-one` as the default StorageClass.

**do not** modify the PVC manifest or any existing Deployments.

🔶 Question 1: Scenario not required

🔶 Question 2: Change Default StorageClass

✅ Scenario Setup

We'll simulate two StorageClasses:

  • old-default (currently default)

  • fast-csi (created but not default)

Apply these two YAMLs:

🔧 old-default.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: old-default
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"  # [default] this is current default
provisioner: csi-driver.example-vendor.example
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: Immediate

🔧 fast-csi.yaml


apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast-csi
  # No default annotation yet
provisioner: csi-driver.example-vendor.example
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: Immediate

Apply both:


kubectl apply -f old-default.yaml
kubectl apply -f fast-csi.yaml

Solution

✅ Step 1: Patch fast-csi to become default


kubectl patch storageclass fast-csi \
  -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

✅ Step 2: Remove is-default-class from old-default


kubectl patch storageclass old-default \
  -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"false"}}}'

✅ Step 3: Confirm the result


kubectl get sc


🔶 Question 3: Scenario not required

🔶 Question  4: Scenario not required

🔶 Question 5: Scenario not required


Comments

Post a Comment

Popular posts from this blog

CKA 2025 MOCK Q-05 HPA

5 Mock Questions on Horizontal Pod Autoscaler (HPA) 🔶 Question 1: Scale Based on Custom CPU Target and Scale-Up Cooldown You have a Deployment named api-backend in the default namespace. Task: Create an HPA targeting 70% CPU usage Min: 1, Max: 10 replicas Set scale-up cooldown (delay before scaling up again) to 30 seconds File name: hpa-backend.yaml Bonus: Set the HPA to avoid scaling up rapidly even if CPU spikes.   cat <<EOF | kubectl apply -f - apiVersion: apps/v1 kind: Deployment metadata:   name: api-backend   namespace: default spec:   replicas: 2   selector:     matchLabels:       app: api-backend   template:     metadata:       labels:         app: api-backend     spec:       containers:   ...
Read more

CKA-2025 MOCK Q-06 PRIORITY

 Generate a PriorityClass named urgent-priority for urgent workloads,  setting the value to 10 less than the highest current user-defined priority class value.  Patch the Deployment mysql-writer in the database namespace to use the urgent-priority class and verify a successful rollout.   Note – Pods from other Deployments in the database namespace should be evicted if resources Cruch kubectl create namespace database # redis-cache Deployment cat <<EOF | kubectl apply -f - apiVersion: apps/v1 kind: Deployment metadata:   name: redis-cache   namespace: database spec:   replicas: 2   selector:     matchLabels:       app: redis-cache   template:     metadata:       labels:         app: redis-cache     spec:       containers:       - name: redis         image: redis:7         resources: ...
Read more

Cert-manager - Custom Resource Definitions

 Cert-manager is a Kubernetes add-on used to manage and automate the issuance, renewal, and management of TLS/SSL certificates inside a Kubernetes cluster. It helps in securing applications and services by integrating with external and internal certificate authorities (CAs) like Let’s Encrypt, HashiCorp Vault, or even self-signed issuers. Here’s how it works: CRDs (Custom Resource Definitions) : cert-manager introduces new Kubernetes resource types like Issuer , ClusterIssuer , and Certificate . These CRDs are used to define how and from where the certificates will be issued. Issuer and ClusterIssuer : Issuer is a namespaced resource that defines a certificate authority configuration usable within a single namespace. ClusterIssuer is similar but works cluster-wide and can issue certificates across all namespaces. Certificate Resource : You define a Certificate resource specifying the domain, secret name (where the certificate will be stored), and which Issuer ...
Read more