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

Add ist0167 message description (#14409) 

* add ist0167 message description

* fix lint

* Update content/en/docs/reference/config/analysis/ist0167/index.md

Co-authored-by: Michael <haifeng.yao@daocloud.io>

* Update content/en/docs/reference/config/analysis/ist0167/index.md

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

* Update content/en/docs/reference/config/analysis/ist0167/index.md

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

* Update content/en/docs/reference/config/analysis/ist0167/index.md

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

* Update content/en/docs/reference/config/analysis/ist0167/index.md

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

---------

Co-authored-by: Michael <haifeng.yao@daocloud.io>
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
This commit is contained in:
Xiaopeng Han 2024-01-08 22:15:30 +08:00 committed by GitHub
parent 3e69144a2c
commit 6a5ce80289
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
content/en/docs/reference/config/analysis/ist0167/index.md Normal file
View File

@ -0,0 +1,39 @@
---
title: IneffectivePolicy
layout: analysis-message
owner: istio/wg-user-experience-maintainers
test: n/a
---
This message occurs when a policy applied in your Istio service mesh has no impact. This might be due to the
policy's configuration incorrectly targeting any workloads or namespaces in your service mesh.
## Example
You will receive a message like this:
{{< text plain >}}
Warning [IST0167] (Sidecar ns-ambient/namespace-scoped testdata/sidecar-default-selector.yaml:84) The policy has no
impact: namespace is in ambient mode, the policy has no impact.
{{< /text >}}
or this:
{{< text plain >}}
Warning [IST0167] (Sidecar ns-ambient/pod-scoped testdata/sidecar-default-selector.yaml:90) The policy has no impact:
selected workload is in ambient mode, the policy has no impact.
{{< /text >}}
These messages indicate that the `Sidecar` resource is targeting a workload or namespace which is in
ambient mode, meaning that the policy specified in the `Sidecar` resource does not have any effect.
## How to resolve
To resolve this issue, you first need to check the reason. Currently, the policy is ineffective for the following
reasons:
1. The `Sidecar` resource is targeting a workload or namespace which is in ambient mode.
To resolve this, ensure that the policy is defined correctly or determine if it is necessary. If the namespace/pod was
recently added to the ambient mesh, you might have forgotten to remove the policy that is no longer needed, or you may
need to update the policy to target the correct workload or namespace.