Step 1: Deploy the Bookinfo Application
Run the following command from the directory containing your Istio samples. Adjust the directory path if your Istio samples are located elsewhere on your computer:Step 2: Verify Istio Sidecar Injection
At this point, with Istio installed, you might expect every pod to include an additional Envoy proxy container. However, the output under the “READY” column indicates that each pod has only a single container. This suggests that the Envoy sidecar is not present. The issue lies in the namespace configuration. Execute the following command for a detailed analysis:The analysis reveals that sidecar injection is not active for the default namespace. In Kubernetes environments with multiple namespaces (e.g., kube-system for core services and default for user applications), you must explicitly enable Istio sidecar injection where required.
Step 3: Enable Istio Sidecar Injection
To activate sidecar injection in the default namespace, execute:Step 4: Re-deploy the Application
Before re-deploying the application, delete the existing deployment:Step 5: Confirm All Pods
For further confirmation, list all the pods to see that each contains both the main application container and its corresponding Envoy sidecar:In upcoming lessons, you’ll explore how these Envoy sidecar proxies manage traffic, enforce policies, and enhance the overall security within the Istio service mesh.