Skip to content

Commit 6ad75b6

Browse files
authored
Merge pull request #45784 from JStickler/version
Clarify how version parameter is applied.
2 parents 3b690d0 + 7f8fc49 commit 6ad75b6

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

modules/ossm-cr-version.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
//
33
// * service_mesh/v2x/ossm-reference-smcp.adoc
44

5+
:_content-type: REFERENCE
56
[id="ossm-cr-version_{context}"]
67
= version parameter
78

8-
You use the `version` parameter to specify what version of the control plane to install. When you create a `ServiceMeshControlPlane` object with an empty `version` parameter, the admission webhook sets the version to the current version. New `ServiceMeshControlPlanes` objects with an empty `version` parameter are set to `v2.0`. Existing `ServiceMeshControlPlanes` objects with an empty `version` parameter keep their setting.
9+
The {SMProductName} Operator supports installation of different versions of the `ServiceMeshControlPlane`. You use the version parameter to specify what version of the control plane to install. If you do not specify a version parameter when creating your SMCP, the Operator sets the value to the latest version: ({MaistraVersion}). Existing `ServiceMeshControlPlane` objects keep their version setting during upgrades of the Operator.

0 commit comments

Comments
 (0)