Skip to content

Commit b319d07

Browse files
authored
Merge pull request #28904 from jritter/fix-mtls-min-max-version-documentation
[OSSMDOC-224] instructions on how to set the minimum and maximum protocol versions is incorrect
2 parents c8eb244 + 20d4303 commit b319d07

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

modules/ossm-security-mtls.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -87,16 +87,16 @@ spec:
8787
[id="ossm-security-min-max-tls_{context}"]
8888
== Setting the minimum and maximum protocol versions
8989

90-
If your environment has specific requirements for encrypted traffic in your service mesh, you can control the cryptographic functions that are allowed by setting the `spec.istio.global.tls.minProtocolVersion` or `spec.istio.global.tls.maxProtocolVersion` in your `ServiceMeshControlPlane` resource. Those values, configured in your control plane resource, define the minimum and maximum TLS version used by mesh components when communicating securely over TLS.
90+
If your environment has specific requirements for encrypted traffic in your service mesh, you can control the cryptographic functions that are allowed by setting the `spec.security.controlPlane.tls.minProtocolVersion` or `spec.security.controlPlane.tls.maxProtocolVersion` in your `ServiceMeshControlPlane` resource. Those values, configured in your control plane resource, define the minimum and maximum TLS version used by mesh components when communicating securely over TLS.
9191

9292
[source,yaml]
9393
----
9494
kind: ServiceMeshControlPlane
9595
spec:
96-
istio:
97-
global:
96+
security:
97+
controlPlane:
9898
tls:
99-
minProtocolVersion: TLSv1_0
99+
minProtocolVersion: TLSv1_2
100100
----
101101

102102
The default is `TLS_AUTO` and does not specify a version of TLS.

0 commit comments

Comments
 (0)