From ada86059d67845dfe0ea2c4d8a4d0c1624a56b58 Mon Sep 17 00:00:00 2001 From: "abby.huang" <78209557+abby-cyber@users.noreply.github.com> Date: Thu, 7 Mar 2024 10:40:00 +0800 Subject: [PATCH] link fixes (#2511) --- .../4.3.scaling/4.3.1.resizing.md | 4 +- .../4.7.security/4.7.1.enable-mtls.md | 287 ------------------ 2 files changed, 2 insertions(+), 289 deletions(-) diff --git a/docs-2.0/k8s-operator/4.cluster-administration/4.3.scaling/4.3.1.resizing.md b/docs-2.0/k8s-operator/4.cluster-administration/4.3.scaling/4.3.1.resizing.md index a26a46c2a15..5b4cf7b8be0 100644 --- a/docs-2.0/k8s-operator/4.cluster-administration/4.3.scaling/4.3.1.resizing.md +++ b/docs-2.0/k8s-operator/4.cluster-administration/4.3.scaling/4.3.1.resizing.md @@ -113,5 +113,5 @@ If the scale-in operation remains incomplete for a long time, you can go to the !!! caution - - Scaling is supported only for the Graph and Storage services in the NebulaGraph cluster, but not for the Meta service. - - If the cluster with the zone feature enabled is scaled in, ensure that the remaining number of Storage Pods after the scaled-in is no less than the number of zones specified by `nebula.metad.config.zone_list`. For instance, if the number of zones is 3, then the number of Storage Pods after the scale-in cannot be less than 3. For more information about zones, see [Enable zones](../../4.cluster-administration/4.8.ha-and-balancing/4.8.2.enable-zone.md). \ No newline at end of file + - Scaling is supported only for the Graph and Storage services in the NebulaGraph cluster, but not for the Meta service. + - If the cluster with the zone feature enabled is scaled in, ensure that the remaining number of Storage Pods after the scaled-in is no less than the number of zones specified by `nebula.metad.config.zone_list`. For instance, if the number of zones is 3, then the number of Storage Pods after the scale-in cannot be less than 3. For more information about zones, see [Enable zones](../../4.cluster-administration/4.8.ha-and-balancing/4.8.2.enable-zone.md). \ No newline at end of file diff --git a/docs-2.0/k8s-operator/4.cluster-administration/4.7.security/4.7.1.enable-mtls.md b/docs-2.0/k8s-operator/4.cluster-administration/4.7.security/4.7.1.enable-mtls.md index 549e4c6ab54..1b7ab822d7a 100644 --- a/docs-2.0/k8s-operator/4.cluster-administration/4.7.security/4.7.1.enable-mtls.md +++ b/docs-2.0/k8s-operator/4.cluster-administration/4.7.security/4.7.1.enable-mtls.md @@ -291,257 +291,6 @@ The following provides examples of the cluster configuration file to enable mTLS # whenUnsatisfiable: "DoNotSchedule" ``` - - - - ??? info "View sample configurations of mTLS between the client and the Graph service" ```yaml @@ -807,8 +556,6 @@ The following only lists the fields that must be configured to enable mTLS with To enable mTLS between services (Graph, Meta, and Storage), add the following fields under the `spec.metad.config`, `spec.graphd.config`, and `spec.storaged.config` respectively in the cluster configuration file. - - ```yaml spec: graph: @@ -843,40 +590,6 @@ The following only lists the fields that must be configured to enable mTLS with ssl_watch_path: certs ``` - - #### `initContainers`, `sidecarContainers`, `volumes`, and `volumeMounts` `initContainers`, `sidecarContainers`, `volumes`, and `volumeMounts` fields are essential for implementing mTLS certificate online hot-reloading.