Operator updates for 3.6.0

docs-2.0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm.md

@@ -129,9 +129,18 @@
           --set nebula.metad.config.zone_list=<zone1,zone2,zone3> \
           --set nebula.graphd.config.prioritize_intra_zone_reading=true \
           --set nebula.graphd.config.stick_to_intra_zone_on_failure=false \
+          # Evenly distribute the Pods of the Storage service across Zones.
+          --set nebula.topologySpreadConstraints[0].topologyKey=topology.kubernetes.io/zone \
+          --set nebula.topologySpreadConstraints[0].whenUnsatisfiable=DoNotSchedule \
+          # Used to schedule restarted Graph or Storage Pods to the specified Zone.
+          --set nebula.schedulerName=nebula-scheduler \
           --namespace="${NEBULA_CLUSTER_NAMESPACE}" \
       ```      
 
+      !!! caution
+
+          Make sure storage Pods are evenly distributed across zones before ingesting data by running `SHOW ZONES` in nebula-console. For zone-related commands, see [Zones](../../4.deployment-and-installation/5.zone.md).
+
   {{ent.ent_end}}
 
   To view all configuration parameters of the NebulaGraph cluster, run the `helm show values nebula-operator/nebula-cluster` command or click [nebula-cluster/values.yaml](https://github.com/vesoft-inc/nebula-operator/blob/{{operator.branch}}/charts/nebula-cluster/values.yaml).
@@ -183,14 +192,13 @@ helm upgrade "${NEBULA_CLUSTER_NAME}" nebula-operator/nebula-cluster \
 
 Similarly, you can scale in a NebulaGraph cluster by setting the value of the `replicas` corresponding to the different services in the cluster smaller than the original value.
 
-In the process of downsizing the cluster, if the operation is not complete successfully and seems to be stuck, you may need to check the status of the job using the `nebula-console` client specified in the `spec.console` field. Analyzing the logs and manually intervening can help ensure that the Job runs successfully. For information on how to check jobs, see [Job statements](../../3.ngql-guide/4.job-statements.md).
+In the process of downsizing the cluster, if the operation is not complete successfully and seems to be stuck, you may need to check the status of the job using the `nebula-console` client specified in the `nebula.console` field. Analyzing the logs and manually intervening can help ensure that the Job runs successfully. For information on how to check jobs, see [Job statements](../../3.ngql-guide/4.job-statements.md).
 
 !!! caution
 
     - NebulaGraph Operator currently only supports scaling Graph and Storage services and does not support scale Meta services.
-    {{ent.ent_begin}}
-    - If you scale in a cluster with Zones, make sure that the number of remaining storage pods is not less than the number of Zones specified in the `spec.metad.config.zone_list` field. Otherwise, the cluster will fail to start.
-    {{ent.ent_end}}
+    - If you scale in a cluster with Zones, make sure that the number of remaining storage pods is not less than the number of Zones specified in the `nebula.metad.config.zone_list` field. Otherwise, the cluster will fail to start.
+
 You can click on [nebula-cluster/values.yaml](https://github.com/vesoft-inc/nebula-operator/blob/{{operator.tag}}/charts/nebula-cluster/values.yaml) to see more configurable parameters of the nebula-cluster chart. For more information about the descriptions of configurable parameters, see **Configuration parameters of the nebula-cluster Helm chart** below.
 
 {{ ent.ent_end }}

docs-2.0/nebula-operator/4.connect-to-nebula-graph-service.md

@@ -70,6 +70,7 @@ You can also create a `ClusterIP` type Service to provide an access point to the
 
   ```bash
   kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- nebula-console -addr 10.98.213.34  -port 9669 -u root -p vesoft
+  ```
 
   - `--image`: The image for the tool NebulaGraph Console used to connect to NebulaGraph databases.
   - `<nebula-console>`: The custom Pod name.
@@ -86,13 +87,27 @@ You can also create a `ClusterIP` type Service to provide an access point to the
   (root@nebula) [(none)]>
   ```
 
-You can also connect to NebulaGraph databases with **Fully Qualified Domain Name (FQDN)**. The domain format is `<cluster-name>-graphd.<cluster-namespace>.svc.<CLUSTER_DOMAIN>`. The default value of `CLUSTER_DOMAIN` is `cluster.local`.
+  You can also connect to NebulaGraph databases with **Fully Qualified Domain Name (FQDN)**. The domain format is `<cluster-name>-graphd.<cluster-namespace>.svc.<CLUSTER_DOMAIN>`. The default value of `CLUSTER_DOMAIN` is `cluster.local`.
 
-```bash
-kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- <nebula_console_name> -addr <cluster_name>-graphd-svc.default.svc.cluster.local -port <service_port> -u <username> -p <password>
-```
+  ```bash
+  kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- <nebula_console_name> -addr <cluster_name>-graphd-svc.default.svc.cluster.local -port <service_port> -u <username> -p <password>
+  ```
+
+  `service_port` is the port to connect to Graphd services, the default port of which is `9669`.
 
-`service_port` is the port to connect to Graphd services, the default port of which is `9669`.
+  !!! note
+
+        If the `spec.console` field is set in the cluster configuration file, you can also connect to NebulaGraph databases with the following command:
+
+        ```bash
+        # Enter the nebula-console Pod.
+        kubectl exec -it nebula-console -- /bin/sh
+
+        # Connect to NebulaGraph databases.
+        nebula-console -addr nebula-graphd-svc.default.svc.cluster.local -port 9669 -u <username> -p <password>
+        ```
+
+  For information about the nebula-console container, see [nebula-console](https://github.com/vesoft-inc/nebula-operator/blob/v{{operator.release}}/doc/user/nebula_console.md#nebula-console).
 
 ## Connect to NebulaGraph databases from outside a NebulaGraph cluster via `NodePort`
 
@@ -197,109 +212,6 @@ Steps:
 
         For information about the nebula-console container, see [nebula-console](https://github.com/vesoft-inc/nebula-operator/blob/v{{operator.release}}/doc/user/nebula_console.md#nebula-console).
 
-## Connect to NebulaGraph databases from within a NebulaGraph cluster
-
-You can also create a `ClusterIP` type Service to provide an access point to the NebulaGraph database for other Pods within the cluster. By using the Service's IP and the Graph service's port number (9669), you can connect to the NebulaGraph database. For more information, see [ClusterIP](https://kubernetes.io/docs/concepts/services-networking/service/).
-
-1. Create a file named `graphd-clusterip-service.yaml`. The file contents are as follows:
-
-  ```yaml
-  apiVersion: v1
-  kind: Service
-  metadata:
-    labels:
-      app.kubernetes.io/cluster: nebula
-      app.kubernetes.io/component: graphd
-      app.kubernetes.io/managed-by: nebula-operator
-      app.kubernetes.io/name: nebula-graph
-    name: nebula-graphd-svc
-    namespace: default
-  spec:
-    externalTrafficPolicy: Local
-    ports:
-    - name: thrift
-      port: 9669
-      protocol: TCP
-      targetPort: 9669
-    - name: http
-      port: 19669
-      protocol: TCP
-      targetPort: 19669
-    selector:
-      app.kubernetes.io/cluster: nebula
-      app.kubernetes.io/component: graphd
-      app.kubernetes.io/managed-by: nebula-operator
-      app.kubernetes.io/name: nebula-graph
-    type: ClusterIP  # Set the type to ClusterIP.
-  ```
-
-  - NebulaGraph uses port `9669` by default. `19669` is the HTTP port of the Graph service in a NebulaGraph cluster.
-  - `targetPort` is the port mapped to the database Pods, which can be customized.
-
-2. Create a ClusterIP Service.
-
-  ```bash	
-  kubectl create -f graphd-clusterip-service.yaml	  
-  ```	
-
-3. Check the IP of the Service:
-
-  ```bash
-  $ kubectl get service -l app.kubernetes.io/cluster=<nebula>  # <nebula> is the name of your NebulaGraph cluster.
-  NAME                       TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)                                          AGE
-  nebula-graphd-svc          ClusterIP   10.98.213.34   <none>        9669/TCP,19669/TCP,19670/TCP                     23h
-  ...
-  ```
-
-4. Run the following command to connect to the NebulaGraph database using the IP of the `<cluster-name>-graphd-svc` Service above:
-
-  ```bash
-  kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- <nebula_console_name> -addr <cluster_ip>  -port <service_port> -u <username> -p <password>
-  ```
-
-  For example:
-
-  ```bash
-  kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- nebula-console -addr 10.98.213.34  -port 9669 -u root -p vesoft
-  ```
-
-  - `--image`: The image for the tool NebulaGraph Console used to connect to NebulaGraph databases.
-  - `<nebula-console>`: The custom Pod name.
-  - `-addr`: The IP of the `ClusterIP` Service, used to connect to Graphd services.
-  - `-port`: The port to connect to Graphd services, the default port of which is `9669`.
-  - `-u`: The username of your NebulaGraph account. Before enabling authentication, you can use any existing username. The default username is root.
-  - `-p`: The password of your NebulaGraph account. Before enabling authentication, you can use any characters as the password.
-
-  A successful connection to the database is indicated if the following is returned:
-
-  ```bash
-  If you don't see a command prompt, try pressing enter.
-
-  (root@nebula) [(none)]>
-  ```
-
-  You can also connect to NebulaGraph databases with **Fully Qualified Domain Name (FQDN)**. The domain format is `<cluster-name>-graphd.<cluster-namespace>.svc.<CLUSTER_DOMAIN>`. The default value of `CLUSTER_DOMAIN` is `cluster.local`.
-
-  ```bash
-  kubectl run -ti --image vesoft/nebula-console:{{console.tag}} --restart=Never -- <nebula_console_name> -addr <cluster_name>-graphd-svc.default.svc.cluster.local -port <service_port> -u <username> -p <password>
-  ```
-
-  `service_port` is the port to connect to Graphd services, the default port of which is `9669`.
-
-  !!! note
-
-        If the `spec.console` field is set in the cluster configuration file, you can also connect to NebulaGraph databases with the following command:
-
-        ```bash
-        # Enter the nebula-console Pod.
-        kubectl exec -it nebula-console -- /bin/sh
-
-        # Connect to NebulaGraph databases.
-        nebula-console -addr nebula-graphd-svc.default.svc.cluster.local -port 9669 -u <username> -p <password>
-        ```
-
-  For information about the nebula-console container, see [nebula-console](https://github.com/vesoft-inc/nebula-operator/blob/v{{operator.release}}/doc/user/nebula_console.md#nebula-console).
-s
 ## Connect to NebulaGraph databases from outside a NebulaGraph cluster via Ingress
 
 When dealing with multiple pods in a cluster, managing services for each pod separately is not a good practice. Ingress is a Kubernetes resource that provides a unified entry point for accessing multiple services. Ingress can be used to expose multiple services under a single IP address.
@@ -401,7 +313,7 @@ Steps are as follows.
         kubectl exec -it nebula-console -- /bin/sh
 
         # Connect to NebulaGraph databases.
-        nebula-console -addr <host_ip> -port <external_port> -u <username> -p <password>
+        nebula-console -addr <ingress_host_ip> -port <external_port> -u <username> -p <password>
         ```
 
         For information about the nebula-console container, see [nebula-console](https://github.com/vesoft-inc/nebula-operator/blob/v{{operator.release}}/doc/user/nebula_console.md#nebula-console).  

docs-2.0/nebula-operator/8.custom-cluster-configurations/8.1.custom-conf-parameter.md

@@ -70,7 +70,5 @@ It should be noted that only when all configuration items in `config` are the pa
 
 For information about the parameters that can be dynamically modified for each service, see the parameter table column of **Whether supports runtime dynamic modifications** in [Meta service configuration parameters](../../5.configurations-and-logs/1.configurations/2.meta-config.md), [Storage service configuration parameters](../../5.configurations-and-logs/1.configurations/4.storage-config.md), and [Graph service configuration parameters](../../5.configurations-and-logs/1.configurations/3.graph-config.md), respectively.
 
-## Learn more
 
-For more information about the configuration parameters of Meta, Storage, and Graph services, see [Meta service configuration parameters](../../5.configurations-and-logs/1.configurations/2.meta-config.md), [Storage service configuration parameters](../../5.configurations-and-logs/1.configurations/4.storage-config.md), and [Graph service configuration parameters](../../5.configurations-and-logs/1.configurations/3.graph-config.md).
 

docs-2.0/nebula-operator/8.custom-cluster-configurations/8.2.pv-reclaim.md

@@ -4,13 +4,12 @@ NebulaGraph Operator uses PVs (Persistent Volumes) and PVCs (Persistent Volume C
 
 You can also define the automatic deletion of PVCs to release data by setting the parameter `spec.enablePVReclaim` to `true` in the configuration file of the cluster instance. As for whether PV will be deleted automatically after PVC is deleted, you need to customize the PV reclaim policy. See [reclaimPolicy in StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/#reclaim-policy) and [PV Reclaiming](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming) for details.
 
-## Notes
-
-The NebulaGraph Operator currently does not support the resizing of Persistent Volume Claims (PVCs), but this feature is expected to be supported in version 1.6.1. Additionally, the Operator does not support dynamically adding or mounting storage volumes to a running storaged instance.
-
 ## Prerequisites
 
 You have created a cluster. For how to create a cluster with Kubectl, see [Create a cluster with Kubectl](../3.deploy-nebula-graph-cluster/3.1create-cluster-with-kubectl.md). 
+## Notes
+
+NebulaGraph Operator does not support dynamically adding or mounting storage volumes to a running storaged instance. 
 
 ## Steps