Update document.

Signed-off-by: Liping Xue <lipingx@vmware.com>
lipingxue · Feb 2, 2024 · c2ae26d · c2ae26d
1 parent bc8df9f
commit c2ae26d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/self-signed-certificate.md b/docs/self-signed-certificate.md
@@ -8,7 +8,7 @@ To keep consistency with velero, Velero plugin for vsphere also supports using v
 * Guest cluster: supported since v1.1.1
 * Supervisor cluster: not supported
 
-To install with a storage provider secured by a self-signed certificate, the --cacert option needs to be added to provide a path to a certificate bundle to trust.
+To install with a storage provider secured by a self-signed certificate, the --cacert option needs to be added to provide a path to a certificate bundle to trust. This certificate is used to verify TLS connection to the object store when backing up and restoring. The object store is specified with ` --backup-location-config` in the install command.
 
 Here is an example install command:
 ```text

diff --git a/docs/supervisor.md b/docs/supervisor.md
@@ -48,7 +48,7 @@ for the detail.
 
 ### Install with self-signed certificate
 
-**Note**: Currently self-signed certificate is not supported on supervisor cluster, please refer to [velero-plugin-for-vsphere with a storage provider secured by a self-signed certificate](self-signed-certificate.md).
+**Note**: Currently using self-signed certificate to connect to the object store is not supported on supervisor cluster. please refer to [velero-plugin-for-vsphere with a storage provider secured by a self-signed certificate](self-signed-certificate.md).
 
 ## Uninstall