What CKA adds to CKAD

~/shop $ kubectl get nodesNAME                STATUS     ROLES           AGE     VERSIONdev-control-plane   Ready      control-plane   6m34s   v1.37.0dev-worker          NotReady   <none>          6m34s   v1.37.0dev-worker2         Ready      <none>          6m34s   v1.37.0

A stall went dark: dev-worker is NotReady. No YAML file can fix this. Someone must go behind the counter, into the machine itself.

CKAD tests the cooks: your apps. The CKACKA: Certified Kubernetes Administrator: hands-on tasks to run the cluster itself. tests the building manager: the cluster itself. Sort each task.

The CKA is 2 hours of hands-on tasks on Kubernetes 1.37. It has five parts. Which part weighs the most?

K9 is your road map to the back office. Tap each stop.

Each stall is a real machine. Step into its back room: a node shellnode shell: A terminal inside one stall's back room: you type commands on the node itself (ssh, or docker exec on kind).. Type ssh dev-worker, then hostname.

~/shop $ docker exec -it dev-worker bashroot@dev-worker:/# hostnamedev-workerroot@dev-worker:/# exitexit

On kindkind: Kubernetes IN Docker: a practice food court built from containers on your laptop., each stall is a Docker container with no SSH server. So you step in with docker exec -it dev-worker bash. Same back room, other door.

K9 breaks stalls on purpose. Where is it safe to practise? Swipe right for safe.

You can now name what the CKA adds, and step inside a node.