Hello all! I did not realize how much it takes to create a course. I’m currently finishing up the labs. I was hoping to get everything done sooner but I didn’t want to sacrifice quality for speed. I’ll keep you guys in the loop. Hope everyone has a great week!

Hope everyone is having a great week so far! I wanted to let you know that my Kubernetes 101 course is scheduled to be released by the end of this weekend. 💪

The kubectl CLI tool is your window into a Kubernetes cluster. You can't get a Kubernetes certification without it. Below are some of the commands I use on a daily bases: Command: kubectl get pods Purpose: List running containers/pods Command: kubectl logs <pod> Purpose: View logs for the chosen pod. Command: kubectl describe pod <pod-name> Purpose: Get detailed info of the chosen pod. Command: kubectl exec -it <pod-name> --bash Purpose: Execute an interactive shell inside the pod. Command: kubectl delete pod <pod-name> Purpose: Remove container/pod Command: kubectl config current-context Purpose: Shows which cluster you are working with. You can find many commands like this in my free Kubernetes cheat-sheet. We will be using these often in future lab exercises. Hope you all have a great weekend!

You just pushed your app to your Kubernetes cluster. You can't wait to jump to your web browser and see your work come to life on the screen. You type in the URL for the app, but you quickly see something is wrong. You log into your cluster to investigate and find this error: ⏳ Pending Your pod is stuck in "Pending" state because the scheduler can’t find a suitable node. 🔍 This usually happens due to insufficient resources or missing tolerations/node selectors. Not sure what I mean by scheduler or node selectors? Keep an eye out for my upcoming free Kubernetes 101 course coming soon!

You just pushed your app to your Kubernetes cluster. You can't wait to jump to your web browser and see your work come to life on the screen. You type in the URL for the app, but you quickly see something is wrong. You log into your cluster to investigate and find this error: ⚠️ ImagePullBackOff / ErrImagePull Kubernetes can’t pull your container image: often due to a wrong image name, missing tag, or lack of access to a private registry. 🔍 Double-check the image URL and credentials (if private). I recently experienced this myself. I made a change to my Azure DevOps pipeline that incorrectly configured the Azure Container Registry URL. Never heard of "Azure DevOps" or "Azure Container Registry"? Keep an eye out for new posts related to Azure. 😎