Skip to content

Commit 37b8729

Browse files
committed
upgrading changes
1 parent 62027e8 commit 37b8729

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

service_mesh/v2x/upgrading-ossm.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ include::modules/ossm-document-attributes.adoc[]
55

66
toc::[]
77

8-
To access the most current features of {ProductName}, upgrade to the current version, 2.0. Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and apps to a new instance of {ProductName} running the new version.
8+
Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and application to a new instance of {ProductName} running the new version.
99

1010
.Prerequisites
1111

@@ -368,7 +368,7 @@ Istiod manages client certificates and private keys used by service proxies. By
368368
[id="ossm-upgrading-config-tracing_{context}"]
369369
=== Tracing
370370

371-
_Tracing_ is configured under `spec.tracing`. Currently, the only type of tracer that is supported is `Jaeger`. Sampling is a scaled integer representing 0.01% increments, for example, 1 is 0.01% and 10000 is 100%. The tracing implementation and sampling rate can be specified:
371+
Tracing is configured in `spec.tracing`. Currently, the only type of tracer that is supported is `Jaeger`. Sampling is a scaled integer representing 0.01% increments, for example, 1 is 0.01% and 10000 is 100%. The tracing implementation and sampling rate can be specified:
372372

373373
[source,yaml]
374374
----
@@ -378,7 +378,7 @@ spec:
378378
type: Jaeger
379379
----
380380

381-
_Jaeger_ is configured under the addons section of the SMCP spec.
381+
Jaeger is configured in the addons section of the `ServiceMeshControlPlane` resource.
382382

383383
[source,yaml]
384384
----
@@ -430,7 +430,7 @@ spec:
430430
install: {} # customize install
431431
----
432432

433-
The Grafana and Kiali installations can be somewhat customized through their respective `install` fields. Container customization, such as resource limits, is configured in `spec.runtime.components.kiali` and `spec.runtime.components.grafana`. If an existing Kiali resource matching the value of name exists, the control plane configures the Kiali resource for use with the control plane. Some fields in the Kiali resource are overridden, such as the `accessible_namespaces` list, as well as the endpoints for Grafana, Prometheus, and tracing. Use an existing resource to fully customize your Kiali installation.
433+
The Grafana and Kiali installations can be customized through their respective `install` fields. Container customization, such as resource limits, is configured in `spec.runtime.components.kiali` and `spec.runtime.components.grafana`. If an existing Kiali resource matching the value of name exists, the control plane configures the Kiali resource for use with the control plane. Some fields in the Kiali resource are overridden, such as the `accessible_namespaces` list, as well as the endpoints for Grafana, Prometheus, and tracing. Use an existing resource to fully customize your Kiali installation.
434434

435435
=== Resource utilization and scheduling
436436

0 commit comments

Comments
 (0)