ISTIOCTL-KUBE-INJECT(1)

💖 istioctl-kube-inject 💖

okay bestie, so this is the manual page for istioctl kube-inject — the command that manually injects the Istio sidecar into your Kubernetes pod resources. it's giving "I got you, your pods are about to be ✨enhanced✨" and honestly? iconic.

---

🌸 NAME 🌸

istioctl-kube-inject — Inject Istio sidecar into Kubernetes pod resources

---

✨ SYNOPSIS ✨

istioctl kube-inject [flags]

---

🎀 DESCRIPTION 🎀

so like, kube-inject manually injects the Istio sidecar into Kubernetes workloads. periodt. 💅

the way that unsupported resources are just left unmodified means it's totally safe to run kube-inject over a single file that contains multiple Service, ConfigMap, Deployment, etc. definitions for a complex application. no cap, it's literally designed for that. when in doubt, just re-run istioctl kube-inject on deployments to get the most up-to-date changes. iykyk.

💡 bestie tip: it's best to do kube-inject when the resource is initially created. like, get it right from the start, you know?

---

🦋 OPTIONS 🦋

okay so here's the full menu of flags, bestie. no skipping, we're covering every single one:

• --authority="" — XDS Subject Alternative Name (for example istiod.istio-system.svc)
• --cert-dir="" — XDS Endpoint certificate directory
• -f, --filename="" — Input Kubernetes resource filename
• -h, --help[=false] — help for kube-inject
• --injectConfigFile="" — Injection configuration filename. Cannot be used with --injectConfigMapName
• --insecure[=false] — Skip server certificate and domain verification. (NOT SECURE!) 🚩
• --meshConfigFile="" — Mesh configuration filename. Takes precedence over --meshConfigMapName if set
• --meshConfigMapName="istio" — ConfigMap name for Istio mesh configuration, key should be "mesh"
• --operatorFileName="" — Path to file containing IstioOperator custom resources. If configs from files like meshConfigFile, valuesFile are provided, they will be overridden by iop config values.
• -o, --output="" — Modified output Kubernetes resource filename
• --plaintext[=false] — Use plain-text HTTP/2 when connecting to server (no TLS).
• -r, --revision="" — Control plane revision
• --timeout=30s — The duration to wait before failing
• --valuesFile="" — Injection values configuration filename.
• --webhookConfig="istio-sidecar-injector" — MutatingWebhookConfiguration name for Istio
• --xds-address="" — XDS Endpoint
• --xds-label="" — Istiod pod label selector
• --xds-port=15012 — Istiod pod port

---

💅 OPTIONS INHERITED FROM PARENT COMMANDS 💅

these are the flags you get from the parent command, bestie. they're like the hand-me-downs but make it Kubernetes:

• --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace
• --as-group=[] — Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
• --as-uid="" — UID to impersonate for the operation.
• --context="" — Kubernetes configuration context
• -i, --istioNamespace="istio-system" — Istio system namespace
• --kubeclient-timeout="15s" — Kubernetes client timeout as a time.Duration string, defaults to 15 seconds.
• -c, --kubeconfig="" — Kubernetes configuration file
• -n, --namespace="" — Kubernetes namespace
• --vklog=0 — number for the log level verbosity. Like -v flag. ex: --vklog=9

---

🌈 EXAMPLE 🌈

okay these examples are literally the blueprint, bestie. copy them, love them, use them. 👑

update resources on the fly before applying:

kubectl apply -f <(istioctl kube-inject -f <resource.yaml>)

create a persistent version of the deployment with Istio sidecar injected:

istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml

update an existing deployment:

kubectl get deployment -o yaml | istioctl kube-inject -f - | kubectl apply -f -

capture cluster configuration for later use with kube-inject:

kubectl -n istio-system get cm istio-sidecar-injector  -o jsonpath="{.data.config}" > /tmp/inj-template.tmpl
kubectl -n istio-system get cm istio -o jsonpath="{.data.mesh}" > /tmp/mesh.yaml
kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.values}" > /tmp/values.json

use kube-inject based on captured configuration:

istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml \
  --injectConfigFile /tmp/inj-template.tmpl \
  --meshConfigFile /tmp/mesh.yaml \
  --valuesFile /tmp/values.json

---

💜 SEE ALSO 💜

• istioctl(1) — the parent command, the main character, the origin story 🫶

---

---

okay that's the whole page, bestie! you're now fully educated on istioctl kube-inject and honestly? you ate that. 💅✨

🎀 cute sign-off: this page was auto generated by spf13/cobra, dated Jan 1980, and it's serving ISTIOCTL-KUBE-INJECT(1) realness. no cap, that's the vibe. 🦋🌸