Heading to planet CKA in the Kubernetes cluster. About to beam down to kubectl city in the k Provence. Adjusting local context to match the native inhabitants.Establishing persistent storage to enhance communications… Mr YAML on screen Captain, ready for your orders.
After reviewing the Udemy course for CKA section 6 – Cluster Upgrade, today was busy.I finally get the upgrade sequence.1. Follow the Documentation!2. Follow your notes!3. Work the Lab!Steps:Repeat for each node– Update repository– Update kubeadm– Drain the node you are working on– Update kubelet– Update kubectl (if on that node as well)– Restart the kubelet process– Uncordon the node–
Running Mac OS 26.5.2 I’ve been using WiFi mostly on my Mac mini. Decided to connect a LAN cable to experiment with network speed and get two simultaneous input vectors going, LAN and WiFi. (No multi NIC cards in the Mac mini) EX: Trying to use AirDrop / Bluetooth / WiFi while running a heavy LAN process through the wired
Multi-Container Pods and the “Why didn’t I know this sooner?” Moment I went in for a marathon session Thursday studying for the CKA certification, and I’m still buzzing—especially after digging into multi-container Pods. Seeing how Pods handle multiple containers was really interesting, and the scheduling + logging sections were a highlight. There’s a lot of power here, and it clicked
We are talking Kubernetes of course. Got to love the quirky IT naming conventions. Once you dig into the concepts behind the naming it all starts to make sense. Today I learned about Node Affinity to control where your pods get deployed onto nodes as well DaemonSets, Taints and Tolerations. Well, you can keep the “flys” away (stray pods) from