update tracing (#12482)

* update tracing

* add proxy.tracer

* fix typo

* update lightstep

* fix lint

content/en/docs/ops/integrations/jaeger/index.md

@@ -7,6 +7,10 @@ owner: istio/wg-environments-maintainers
 test: n/a
 ---
 
+{{< tip >}}
+Users are encouraged to transition to the [Telemetry API](/docs/tasks/observability/telemetry/) for tracing configuration.
+{{</ tip >}}
+
 [Jaeger](https://www.jaegertracing.io/) is an open source end to end distributed tracing system, allowing users to monitor and troubleshoot transactions in complex distributed systems.
 
 ## Installation
@@ -25,7 +29,7 @@ This will deploy Jaeger into your cluster. This is intended for demonstration on
 
 Consult the [Jaeger documentation](https://www.jaegertracing.io/) to get started. No special changes are needed for Jaeger to work with Istio.
 
-Once Jaeger is installed, you will need to point Istio proxies to send traces to the deployment. This can be configured with `--set values.global.tracer.zipkin.address=<jaeger-collector-address>:9411` at installation time. See the [`ProxyConfig.Tracing`](/docs/reference/config/istio.mesh.v1alpha1/#Tracing) for advanced configuration such as TLS settings.
+Once Jaeger is installed, you will need to point Istio proxies to send traces to the deployment. This can be configured with `--set meshConfig.defaultConfig.tracing.zipkin.address=<jaeger-collector-address>:9411` at installation time. See the [`ProxyConfig.Tracing`](/docs/reference/config/istio.mesh.v1alpha1/#Tracing) for advanced configuration such as TLS settings.
 
 ## Usage
 

content/en/docs/ops/integrations/zipkin/index.md

@@ -7,6 +7,10 @@ owner: istio/wg-environments-maintainers
 test: n/a
 ---
 
+{{< tip >}}
+Users are encouraged to transition to the [Telemetry API](/docs/tasks/observability/telemetry/) for tracing configuration.
+{{</ tip >}}
+
 [Zipkin](https://zipkin.io/) is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in service architectures. Features include both the collection and lookup of this data.
 
 ## Installation
@@ -25,7 +29,7 @@ This will deploy Zipkin into your cluster. This is intended for demonstration on
 
 Consult the [Zipkin documentation](https://zipkin.io/) to get started. No special changes are needed for Zipkin to work with Istio.
 
-Once Zipkin is installed, you will need to point Istio proxies to send traces to the deployment. This can be configured with `--set values.global.tracer.zipkin.address=<zipkin-collector-address>:9411` at installation time. See the [`ProxyConfig.Tracing`](/docs/reference/config/istio.mesh.v1alpha1/#Tracing) for advanced configuration such as TLS settings.
+Once Zipkin is installed, you will need to point Istio proxies to send traces to the deployment. This can be configured with `--set meshConfig.defaultConfig.tracing.zipkin.address=<zipkin-collector-address>:9411` at installation time. See the [`ProxyConfig.Tracing`](/docs/reference/config/istio.mesh.v1alpha1/#Tracing) for advanced configuration such as TLS settings.
 
 ## Usage
 

content/en/docs/tasks/observability/distributed-tracing/lightstep/index.md

@@ -9,6 +9,10 @@ owner: istio/wg-policies-and-telemetry-maintainers
 test: no
 ---
 
+{{< tip >}}
+Users are encouraged to transition to the [Telemetry API](/docs/tasks/observability/telemetry/) for tracing configuration.
+{{</ tip >}}
+
 This task shows you how to configure Istio to collect trace spans and send them to [Lightstep](https://lightstep.com).
 Lightstep lets you analyze 100% of unsampled transaction data from large scale production software to produce meaningful
 distributed traces and metrics that help explain performance behaviors and accelerate root cause analysis.
@@ -42,20 +46,20 @@ use your own cert and your own pool's endpoint (`host:port`).
 1.  You need to deploy Istio with your Satellite address at an address in the format `<Host>:<Port>`, for example `lightstep-satellite.lightstep:9292`. You find this in your [configuration](https://docs.lightstep.com/docs/satellite-configuration-parameters#ports) file.
 
 1.  Deploy Istio with the following configuration parameters specified:
-    - `pilot.traceSampling=100`
     - `global.proxy.tracer="lightstep"`
-    - `global.tracer.lightstep.address="<satellite-address>"`
-    - `global.tracer.lightstep.accessToken="<access-token>"`
+    - `meshConfig.defaultConfig.tracing.sampling=100`
+    - `meshConfig.defaultConfig.tracing.lightstep.address="<satellite-address>"`
+    - `meshConfig.defaultConfig.tracing.lightstep.accessToken="<access-token>"`
 
     You can set these parameters using the `--set key=value` syntax
     when you run the install command. For example:
 
     {{< text bash >}}
     $ istioctl install \
-        --set values.pilot.traceSampling=100 \
-        --set values.global.proxy.tracer="lightstep" \
-        --set values.global.tracer.lightstep.address="<satellite-address>" \
-        --set values.global.tracer.lightstep.accessToken="<access-token>" \
+        --set global.proxy.tracer="lightstep" \
+        --set meshConfig.defaultConfig.tracing.sampling=100 \
+        --set meshConfig.defaultConfig.tracing.lightstep.address="<satellite-address>" \
+        --set meshConfig.defaultConfig.tracing.lightstep.accessToken="<access-token>" \
     {{< /text >}}
 
 ### Deploy Istio with Public or Developer Mode Satellites
@@ -92,13 +96,12 @@ Follow these steps if you're using the Public or Developer Mode Satellites, or i
     global:
       proxy:
         tracer: "lightstep"
-      tracer:
-        lightstep:
-          address: "ingest.lightstep.com:443"
-          accessToken: "<access-token>"
     meshConfig:
       defaultConfig:
         tracing:
+          lightstep:
+            address: "ingest.lightstep.com:443"
+            accessToken: "<access-token>"
           sampling: 100
           tlsSettings
             mode: "SIMPLE"