Istio Sidecar Injection¶
Istio Sidecar Injection is the mechanism used to integrate application pods into the Istio service mesh. This process involves modifying a Pod's specification to include an Istio Proxy, typically Envoy, which manages traffic routing, security, and observability features for the service^[httpbin-README.md].
Deployment Methods¶
There are two primary ways to enable sidecar injection when deploying services:
Automatic Injection¶
When automatic sidecar injection is enabled for a namespace, the Istio admission controller automatically injects the proxy configuration into pods upon creation^[httpbin-README.md]. This allows users to deploy applications using standard commands without manually modifying the resource definitions^[httpbin-README.md, websockets-README.md].
Manual Injection¶
If automatic injection is not enabled, the sidecar must be injected manually before deployment^[httpbin-README.md]. This is achieved using istioctl kube-inject, which transforms the standard Kubernetes configuration by adding the necessary proxy container configurations^[httpbin-README.md, websockets-README.md].