Explain pod annotation overrides for tracing (#7923)

* Explain pod annotation overrides for tracing

* Review comments
This commit is contained in:
Neeraj Poddar 2020-08-11 20:36:29 -06:00 committed by GitHub
parent 6f66132c02
commit c94a3f2e80
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions

View File

@ -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.
{{< /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
All tracing options can be configured globally via `MeshConfig`.