mirror of https://github.com/istio/istio.io.git
Explain pod annotation overrides for tracing (#7923)
* Explain pod annotation overrides for tracing * Review comments
This commit is contained in:
parent
6f66132c02
commit
c94a3f2e80
|
@ -46,6 +46,13 @@ In order for the new tracing configuration to take effect for either of these
|
||||||
options you need to restart pods injected with Istio proxies.
|
options you need to restart pods injected with Istio proxies.
|
||||||
{{< /warning >}}
|
{{< /warning >}}
|
||||||
|
|
||||||
|
Note that any pod annotations added for tracing configuration overrides global settings.
|
||||||
|
In order to preserve any global settings you should copy them from
|
||||||
|
global mesh config to pod annotations along with workload specific
|
||||||
|
customization. In particular, make sure that the tracing backend address is
|
||||||
|
always provided in the annotations to ensure that the traces are reported
|
||||||
|
correctly for the workload.
|
||||||
|
|
||||||
### Using `MeshConfig` for trace settings
|
### Using `MeshConfig` for trace settings
|
||||||
|
|
||||||
All tracing options can be configured globally via `MeshConfig`.
|
All tracing options can be configured globally via `MeshConfig`.
|
||||||
|
|
Loading…
Reference in New Issue