From 8725b9458ade0ca39e267bd81729b4ee29e036fd Mon Sep 17 00:00:00 2001 From: Xiaopeng Han Date: Thu, 23 Feb 2023 15:32:54 +0800 Subject: [PATCH] Add IST0158 message description (#12744) * Add IST0158 message description * fix lint * revise description --- .../config/analysis/ist0158/index.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 content/en/docs/reference/config/analysis/ist0158/index.md diff --git a/content/en/docs/reference/config/analysis/ist0158/index.md b/content/en/docs/reference/config/analysis/ist0158/index.md new file mode 100644 index 0000000000..62b3f10b4e --- /dev/null +++ b/content/en/docs/reference/config/analysis/ist0158/index.md @@ -0,0 +1,27 @@ +--- +title: PodsIstioProxyImageMismatchInNamespace +layout: analysis-message +owner: istio/wg-user-experience-maintainers +test: n/a +--- + +This message is similar to [IST0105](/docs/reference/config/analysis/ist0105/), which is a warning message for a single pod. + +This message occurs when the namespace is enabled for automatic sidecar injection, but some pods in the namespace are not having the correct sidecar injected. + +If any of the pods in the namespace are not running the correct sidecar version, this message will be reported. +The names of the pods are listed in the message detail. + +This often happens as a result of upgrading the Istio control plane; after upgrading +Istio (which includes the sidecar injector), all running workloads with an Istio +sidecar must be recreated to allow the new version of the sidecar to be +injected. + +To resolve this problem, update the sidecar version by redeploying your applications +using your normal rollout strategy. For a Kubernetes deployment: + +* If you're using Kubernetes 1.15 or higher, you can run + `kubectl rollout restart ` to trigger a new rollout. +* Alternatively, you can modify the deployment's `template` field to force a new + rollout. This is often done by adding a label like + `force-redeploy=` to the pod definition in the template.