Given a Kubernetes cluster with Istio service mesh enabled, what will be the output of the command kubectl get pods -n default after deploying an app with sidecar injection enabled?
medium📝 Command Output Q4 of 15
Kubernetes - Service Mesh
Given a Kubernetes cluster with Istio service mesh enabled, what will be the output of the command kubectl get pods -n default after deploying an app with sidecar injection enabled?
APods will show multiple replicas of the app container only
BPods will show only the app container without any sidecar
CPods will fail to start due to sidecar injection errors
DPods will show two containers each: the app container and the Istio sidecar proxy
Step-by-Step Solution
Solution:
Step 1: Understand sidecar injection effect
When sidecar injection is enabled, each pod includes the app container plus an Istio proxy container.
Step 2: Interpret kubectl get pods output
The pod description will list two containers per pod, showing the sidecar alongside the app.
Final Answer:
Pods will show two containers each: the app container and the Istio sidecar proxy -> Option D
Quick Check:
Sidecar injection adds proxy container to pods [OK]
Quick Trick:Sidecar injection adds proxy container visible in pod details [OK]
Common Mistakes:
Expecting pods to have only app containers
Assuming pods fail due to injection
Confusing replicas with sidecar containers
Master "Service Mesh" in Kubernetes
9 interactive learning modes - each teaches the same concept differently
