From 3bcd4b250d6655ab0cb8197fe0f9b847fda130c9 Mon Sep 17 00:00:00 2001 From: Yanjun Zhou Date: Tue, 25 Jul 2023 17:54:30 -0700 Subject: [PATCH] Update doc Signed-off-by: Yanjun Zhou --- docs/network-flow-visibility.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/network-flow-visibility.md b/docs/network-flow-visibility.md index f8e480e5a..2b7fdbae9 100644 --- a/docs/network-flow-visibility.md +++ b/docs/network-flow-visibility.md @@ -292,20 +292,20 @@ PV creation, you can configure a customized `StorageClass` in ##### Secure Connection -From Theia 0.7, we support TLS connection option in ClickHouse server. To +From Theia 0.8, we support TLS connection option in ClickHouse server. To enable TLS connection, please set `clickhouse.service.secureConnection.enable` to true. Currently ClickHouse Operator does not support cert-manager, which means users need to manually do the certs rotation when using this ClickHouse server TLS option. You can set `clickhouse.service.secureConnection.selfSignedCert` to -true to use the default certs. Please ensure you set the Subject's common name -and optional IP addresses and DNS names. You will need to renew the certs after -`clickhouse.service.secureConnection.daysValid` passes. +true to use the default certs. Please ensure that you have set the subject's +common name. You will need to renew the certs after `clickhouse.service.secureConnection.daysValid` +passes. You can set `clickhouse.service.secureConnection.selfSignedCert` to -false to use you own certicates by providing them in a Secret called -`clickhouse-tls` with the following keys: `tls.crt` and `tls.key`. +false to provide your own certificates by creating a Secret with name +`clickhouse-tls` containing the following keys: `tls.crt` and `tls.key`. #### With Standalone Manifest