Recap: What We Learned Previously In our previous blog, we: Introduced Ingress and Ingress Controllers Understood how Ingress routes traffic based on paths or hostnames Deployed an Ingress Controller to expose multiple services under the same doma...
Recap: Where We Left Off In our previous blog, we learned: What Services are and how they expose Pods The difference between ClusterIP, NodePort, and LoadBalancer How to connect to applications running in Kubernetes using these service types But...
Quick Recap – Where We Are In the last blog, we: Understood how Deployments manage ReplicaSets and Pods Learned to scale applications manually Performed rolling updates without downtime Saw how Kubernetes ensures self-healing by replacing failed ...
A Quick Recap In our previous blog, we explored: The Pod Lifecycle and common states like Pending, Running, CrashLoopBackOff Real-time debugging using kubectl describe, logs, and exec How to simulate pod failures and investigate them Tools and co...
What We’ve Covered So Far In the last few blogs, we’ve taken major strides: Part 1: Understood what Kubernetes is and why it exists using real-world analogies. Part 2: Explored the Kubernetes Architecture, both control plane and worker nodes. Part...
In this third installment of the "Kubernetes From Zero to Hero" series, we're diving into the practical side of Kubernetes. This article will guide you through setting up Kubernetes on your local machine using Minikube, understanding the cluster it c...
Why Architecture Matters Understanding Kubernetes architecture is like understanding how a car works before you drive it. If you know what each part does, you’ll be able to troubleshoot, optimise, and scale more effectively. Let’s break it down into ...
The Problem Before Kubernetes Before understanding what Kubernetes is, let’s rewind a bit. 1. The Old World: Monolithic Applications Back in the day, applications were developed as a single block of code, known as a monolith. Think of a traditional w...
