From e46910910212da07b600317c4204339e6c0cc11e Mon Sep 17 00:00:00 2001 From: kmetin Date: Tue, 5 Nov 2024 11:55:28 +0300 Subject: [PATCH] fix PR comment --- docs/modules/ROOT/pages/tls.adoc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/modules/ROOT/pages/tls.adoc b/docs/modules/ROOT/pages/tls.adoc index 010f6f9a..f2ea0c48 100644 --- a/docs/modules/ROOT/pages/tls.adoc +++ b/docs/modules/ROOT/pages/tls.adoc @@ -47,14 +47,7 @@ Below are the configuration options for the TLS. |`secretName` | Specifies the name of Kubernetes TLS secret. -|`mutualAuthentication` (deprecated) -| Mutual authentication configuration, available values are: -- `None` (default): The client side of the connection is not authenticated. -- `Required`: Server forces usage of a trusted client certificate. -- `Optional`: Server asks for a client certificate, but it doesn't require it. - -WARNING: It is deprecated and should no longer be used. It is retained solely for the purpose of maintaining backward compatibility. In the previous versions, the Operator was forcing mutual authentication between members and the `mutualAuthentication` field was being used as the `clientAuthentication` field. Now, it is possible to configure them separately. |`clientAuthentication` | Mutual authentication configuration for client to member communication, available values are: