AKS

Container Lifecycle (within a Pod) Each container follows this: Pod Lifecycle Phases

When a Pod is deleted, Kubelet (the agent running on each AKS node) handles its graceful termination using a process called graceful shutdown. Here’s how it works: 1. User runs kubectl delete pod You (or a controller like Deployment) run: kubectl delete pod my-app This sends a delete request to the Kubernetes API server. 2.

In AKS, the restart policy defines how Kubernetes restarts containers inside a Pod when they exit (fail or stop). Restart Policy is Defined at the Pod Level It’s set in the Pod spec under .spec.restartPolicy. There are 3 types: Restart Policy Description Always Always restarts the container if it fails (default for regular Pods). OnFailure

1️⃣ kubectl apply -f pod.yaml You apply the pod definition file. 2️⃣ 🧠 kubectl talks to the API Server 3️⃣ 📦 API Server stores pod data in etcd 4️⃣ 👀 Scheduler checks for new unscheduled pods 5️⃣ 📬 Kubelet on the selected node is notified 6️⃣ 📥 Kubelet pulls container image & starts pod 7️⃣

A Sidecar container is a helper container that runs alongside your main application container in the same Pod and helps it do its job. Think of your application as a car, and the sidecar is like a co-driver or a support vehicle — it’s not the driver, but helps with navigation, music, tools, or repairs.

An Init Container is a special type of container that runs before the main application container starts in a Pod. Think of it like a “setup step” before your app runs. Use Case (in simple terms): Imagine you’re baking a cake (your main app) — but before you start, you need to: These setup tasks

We call Kubernetes as K8s as a form of abbreviation. Here’s the reason: If you keep the first letter (K) and the last letter (s), and replace the 8 letters in between with the number 8, you get K8s. This style of abbreviation is known as a numeronym The word Kubernetes has 10 letters.