istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add IST0158 message description (#12744) 

* Add IST0158 message description

* fix lint

* revise description
This commit is contained in:
Xiaopeng Han 2023-02-23 15:32:54 +08:00 committed by GitHub
parent 05e2035c40
commit 8725b9458a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
content/en/docs/reference/config/analysis/ist0158/index.md Normal file
View File

@ -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 <my-deployment>` 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=<current-timestamp>` to the pod definition in the template.