diff --git a/3.6.0/index.html b/3.6.0/index.html index 51cb8302e89..e9ed283059e 100644 --- a/3.6.0/index.html +++ b/3.6.0/index.html @@ -5737,7 +5737,7 @@
Note
-This manual is revised on 2023-10-30, with GitHub commit 095118b400.
+This manual is revised on 2023-10-30, with GitHub commit f488eba609.
NebulaGraph is a distributed, scalable, and lightning-fast graph database. It is the optimal solution in the world capable of hosting graphs with dozens of billions of vertices (nodes) and trillions of edges (relationships) with millisecond latency.
The NebulaGraph Operator scaling feature is only available for the Enterprise Edition of NebulaGraph clusters and does not support scaling the Community Edition version of NebulaGraph clusters.
Note
??? Info "Expand to show parameter descriptions of community clusters"
-| Parameter | Default value | Description |
-| :---- | :--- | :--- |
-| `metadata.name` | - | The name of the created NebulaGraph cluster. |
-|`spec.console`|-| Configuration of the Console service. For details, see [nebula-console](https://github.com/vesoft-inc/nebula-operator/blob/v1.7.1/doc/user/nebula_console.md#nebula-console).|
-| `spec.graphd.replicas` | `1` | The numeric value of replicas of the Graphd service. |
-| `spec.graphd.image` | `vesoft/nebula-graphd` | The container image of the Graphd service. |
-| `spec.graphd.version` | `v3.6.0` | The version of the Graphd service. |
-| `spec.graphd.service` | - | The Service configurations for the Graphd service. |
-| `spec.graphd.logVolumeClaim.storageClassName` | - | The log disk storage configurations for the Graphd service. |
-| `spec.metad.replicas` | `1` | The numeric value of replicas of the Metad service. |
-| `spec.metad.image` | `vesoft/nebula-metad` | The container image of the Metad service. |
-| `spec.metad.version` | `v3.6.0` | The version of the Metad service. |
-| `spec.metad.dataVolumeClaim.storageClassName` | - | The data disk storage configurations for the Metad service. |
-| `spec.metad.logVolumeClaim.storageClassName`|- | The log disk storage configurations for the Metad service.|
-| `spec.storaged.replicas` | `3` | The numeric value of replicas of the Storaged service. |
-| `spec.storaged.image` | `vesoft/nebula-storaged` | The container image of the Storaged service. |
-| `spec.storaged.version` | `v3.6.0` | The version of the Storaged service. |
-| `spec.storaged.dataVolumeClaims.resources.requests.storage` | - | Data disk storage size for the Storaged service. You can specify multiple data disks to store data. When multiple disks are specified, the storage path is `/usr/local/nebula/data1`, `/usr/local/nebula/data2`, etc.|
-| `spec.storaged.dataVolumeClaims.resources.storageClassName` | - | The data disk storage configurations for Storaged. If not specified, the global storage parameter is applied. |
-| `spec.storaged.logVolumeClaim.storageClassName`|- | The log disk storage configurations for the Storaged service.|
-| `spec.storaged.enableAutoBalance` | `true` |Whether to balance data automatically. |
-|`spec.<metad|storaged|graphd>.securityContext`|`{}`|Defines privilege and access control settings for NebulaGraph service containers. For details, see [SecurityContext](https://github.com/vesoft-inc/nebula-operator/blob/release-1.7/doc/user/security_context.md). |
-|`spec.agent`|`{}`| Configuration of the Agent service. This is used for backup and recovery as well as log cleanup functions. If you do not customize this configuration, the default configuration will be used.|
-| `spec.reference.name` | - | The name of the dependent controller. |
-| `spec.schedulerName` | - | The scheduler name. |
-| `spec.imagePullPolicy` | The image policy to pull the NebulaGraph image. For details, see [Image pull policy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy). | The image pull policy in Kubernetes. |
-|`spec.logRotate`| - |Log rotation configuration. For more information, see [Manage cluster logs](../8.custom-cluster-configurations/8.4.manage-running-logs.md).|
-|`spec.enablePVReclaim`|`false`|Define whether to automatically delete PVCs and release data after deleting the cluster. For more information, see [Reclaim PVs](../8.custom-cluster-configurations/8.2.pv-reclaim.md).|
-
See community cluster configurations.
+The following table describes the parameters in the sample configuration file.
+Parameter | +Default value | +Description | +
---|---|---|
metadata.name |
+- | +The name of the created NebulaGraph cluster. | +
spec.console |
+- | +Configuration of the Console service. For details, see nebula-console. | +
spec.graphd.replicas |
+1 |
+The numeric value of replicas of the Graphd service. | +
spec.graphd.image |
+vesoft/nebula-graphd |
+The container image of the Graphd service. | +
spec.graphd.version |
+v3.6.0 |
+The version of the Graphd service. | +
spec.graphd.service |
+- | +The Service configurations for the Graphd service. | +
spec.graphd.logVolumeClaim.storageClassName |
+- | +The log disk storage configurations for the Graphd service. | +
spec.metad.replicas |
+1 |
+The numeric value of replicas of the Metad service. | +
spec.metad.image |
+vesoft/nebula-metad |
+The container image of the Metad service. | +
spec.metad.version |
+v3.6.0 |
+The version of the Metad service. | +
spec.metad.dataVolumeClaim.storageClassName |
+- | +The data disk storage configurations for the Metad service. | +
spec.metad.logVolumeClaim.storageClassName |
+- | +The log disk storage configurations for the Metad service. | +
spec.storaged.replicas |
+3 |
+The numeric value of replicas of the Storaged service. | +
spec.storaged.image |
+vesoft/nebula-storaged |
+The container image of the Storaged service. | +
spec.storaged.version |
+v3.6.0 |
+The version of the Storaged service. | +
spec.storaged.dataVolumeClaims.resources.requests.storage |
+- | +Data disk storage size for the Storaged service. You can specify multiple data disks to store data. When multiple disks are specified, the storage path is /usr/local/nebula/data1 , /usr/local/nebula/data2 , etc. |
+
spec.storaged.dataVolumeClaims.resources.storageClassName |
+- | +The data disk storage configurations for Storaged. If not specified, the global storage parameter is applied. | +
spec.storaged.logVolumeClaim.storageClassName |
+- | +The log disk storage configurations for the Storaged service. | +
spec.storaged.enableAutoBalance |
+true |
+Whether to balance data automatically. | +
spec.<metad|storaged|graphd>.securityContext |
+{} |
+Defines privilege and access control settings for NebulaGraph service containers. For details, see SecurityContext. | +
spec.agent |
+{} |
+Configuration of the Agent service. This is used for backup and recovery as well as log cleanup functions. If you do not customize this configuration, the default configuration will be used. | +
spec.reference.name |
+- | +The name of the dependent controller. | +
spec.schedulerName |
+- | +The scheduler name. | +
spec.imagePullPolicy |
+The image policy to pull the NebulaGraph image. For details, see Image pull policy. | +The image pull policy in Kubernetes. | +
spec.logRotate |
+- | +Log rotation configuration. For more information, see Manage cluster logs. | +
spec.enablePVReclaim |
+false |
+Define whether to automatically delete PVCs and release data after deleting the cluster. For more information, see Reclaim PVs. | +
+ | + | + |
Create a NebulaGraph cluster.
@@ -5817,9 +5928,7 @@The cluster scaling feature is for NebulaGraph Enterprise Edition only.
Run the following command to delete a NebulaGraph cluster with Kubectl:
kubectl delete -f apps_v1alpha1_nebulacluster.yaml
@@ -5832,7 +5941,7 @@ What's nextOctober 25, 2023
+ October 30, 2023
diff --git a/3.6.0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm/index.html b/3.6.0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm/index.html
index 8a7d2cc82de..ad19b559a58 100644
--- a/3.6.0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm/index.html
+++ b/3.6.0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm/index.html
@@ -5794,23 +5794,10 @@ Create clusterskubectl -n "${NEBULA_CLUSTER_NAMESPACE}" get pod -l "app.kubernetes.io/cluster=${NEBULA_CLUSTER_NAME}"
Output:
-NAME READY STATUS RESTARTS AGE
-nebula-graphd-0 1/1 Running 0 5m34s
-nebula-graphd-1 1/1 Running 0 5m34s
-nebula-metad-0 1/1 Running 0 5m34s
-nebula-metad-1 1/1 Running 0 5m34s
-nebula-metad-2 1/1 Running 0 5m34s
-nebula-storaged-0 1/1 Running 0 5m34s
-nebula-storaged-1 1/1 Running 0 5m34s
-nebula-storaged-2 1/1 Running 0 5m34s
-
The cluster scaling feature is for NebulaGraph Enterprise Edition only.
Run the following command to delete a NebulaGraph cluster with Helm:
helm uninstall "${NEBULA_CLUSTER_NAME}" --namespace="${NEBULA_CLUSTER_NAMESPACE}"
@@ -5826,7 +5813,7 @@ What's nextOctober 25, 2023
+ October 30, 2023
diff --git a/3.6.0/pdf/NebulaGraph-EN.pdf b/3.6.0/pdf/NebulaGraph-EN.pdf
index 1671731dd76..58bdad363a4 100644
Binary files a/3.6.0/pdf/NebulaGraph-EN.pdf and b/3.6.0/pdf/NebulaGraph-EN.pdf differ
diff --git a/3.6.0/sitemap.xml.gz b/3.6.0/sitemap.xml.gz
index 9bc094e9da8..5ff830dcef2 100644
Binary files a/3.6.0/sitemap.xml.gz and b/3.6.0/sitemap.xml.gz differ