CKA(Certified Kubernetes Administrator) Q&A | Practical

Learn to create a Kubernetes pod named cookie eight with two containers, nginx and redis, using the provided images in a practical CKA Q&A overview.

Label the target node, use a node selector in the pod YAML to schedule the pod there, and verify with kubectl commands and pod describe to view events.

Explore essential node-based concepts in Kubernetes, including node selector, node affinity and anti-affinity, node labels, and pod topology, to prepare for diverse exam questions.

Explore configuring a Kubernetes deployment named nginx-app with three replicas using nginx:1.25.0-alpine, perform a rolling update to 1.26.0-alpine, and rollback to 1.25, using an imperative kubectl approach.

Learn to create a Kubernetes deployment with kubectl, set image upgrades for nginx from 1.25.0-alpine to 1.26.0-alpine with three replicas, verify pods, and rollback using rollout history and undo.

Configure the Kubernetes context and create a cluster IP service named frontend service that routes to the existing frontend pod.

Create a cluster IP service bound to a pod by label app is equal to front end using declarative YAML with a selector and ports, verify with kubectl and curl.

Understand the question, edit the service with kubectl edit svc to switch from cluster IP to node port, and verify changes to reinforce exam-ready practice.

Configure the Kubernetes context and ensure the website-frontend namespace exists. Launch a pod named nginx using the nginx image in that namespace.

Configure kubernetes context and create a deployment with three replicas of the image, labeled app_runtime_stage=prod, named KUA100201, saved as spec_deployment.yaml under /opt/KUAL00201, then apply, verify, and delete.

Create a Kubernetes deployment YAML at opt/kual00201/spec_deployment.yaml to deploy Redis with three replicas and label app_runtime_stage=prod on both deployment and pod, then apply with kubectl.

Perform a hands-on Kubernetes task to find a service's endpoints, list pods with their IPs, and save the filtered pod names to a file for validation.

Configure the cluster context and create a secret named 'super secret' with credential. Deploy two pods: one mounts the secret as a file, the other via environment variable named credentials.

Create a generic secret with kubectl imperatively, then mount it as a file or pass it as an environment variable to a pod, illustrating base64 encoding in the default namespace.