Multicloud Navigator

  Kubernetes Pods: Public & Private Container Registries, Local Images, Authentication and Image Pulling Complete Beginner-to-Practical Guide When Kubernetes creates a Pod, it needs a container image . That image can come from: A local image already available to the Kubernetes node A public container registry such as Docker Hub A private container registry requiring authentication Understanding this process helps us troubleshoot common Kubernetes errors such as: ErrImagePull ImagePullBackOff 1. First Understand Image → Container → Pod The easiest way to remember the relationship is: Container Image ↓ Container ↓ Pod In Kubernetes terminology, the Pod is the Kubernetes unit that contains the container: Pod └── Container └── Image For example: Pod └── nginx container └── nginx:latest image Remember Image = package/template Container = running instance of the image Pod = Kubernetes unit containing one or more containers 2. What Happens When We Create a Pod?...

🐳 Docker inspect — Easy Memory Trick Instead of memorizing dozens of docker inspect commands, remember: CSNMH → ICEEP → FSRPET → PING → SD → CMR 1️⃣ Main Mnemonic — CSNMH C → Config S → State N → NetworkSettings M → Mounts H → HostConfig Think: Config → State → Network → Mount → Host 2️⃣ Config → ICEEP 🧊 ICEEP = Ice P I → Image C → Cmd E → Entrypoint E → Env P → ExposedPorts Fields .Config.Image .Config.Cmd .Config.Entrypoint .Config.Env .Config.ExposedPorts 3️⃣ State → FSRPET ⚙️ F → FinishedAt S → Status R → Running P → PID E → ExitCode T → StartedAt Fields .State.FinishedAt .State.Status .State.Running .State.Pid .State.ExitCode .State.StartedAt 4️⃣ NetworkSettings → PING 📡 Network = PING P → Ports I → IPAddress N → Networks G → Gateway Fields .NetworkSettings.Ports .NetworkSettings.IPAddress .NetworkSettings.Networks .NetworkSettings.Gateway ⚠️ IP and Gateway are commonly nested inside Networks , so in practice use range : docker inspect con...

 Let's make it very simple and practical . Kubernetes: Pod → ReplicaSet → Deployment The whole story is: Pod ↓ Problem: only one Pod / no proper management ↓ ReplicaSet ↓ Problem: no proper application rollout/version management ↓ Deployment 1. POD Why Pod? You simply want to run one application/container. Pod └── nginx container Pod YAML apiVersion: v1 kind: Pod metadata: name: nginx-pod spec: containers: - name: nginx image: nginx:latest ports: - containerPort: 80 Create Pod kubectl apply -f pod.yaml Pod commands — important types 1. Create / Apply kubectl apply -f pod.yaml 2. Get kubectl get pods kubectl get pod nginx-pod kubectl get pods -o wide 3. Describe kubectl describe pod nginx-pod 4. Logs kubectl logs nginx-pod 5. Execute inside Pod kubectl exec -it nginx-pod -- /bin/bash 6. Delete kubectl delete pod nginx-pod 7. Get YAML kubectl get pod nginx-pod -o yaml Why move from Pod → ReplicaSet? Suppose: Po...