Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixoperator1.5.0 #2219

Merged
merged 1 commit into from
Aug 10, 2023
Merged

fixoperator1.5.0 #2219

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-2.0/nebula-operator/3.deploy-nebula-graph-cluster/3.0.deploy-lm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

!!! enterpriseonly

The LM service is only used to manage the NebulaGraph Enterprise license. If you are using the Community Edition of NebulaGraph, you do not need to deploy LM.
The LM service is only used to manage the NebulaGraph Enterprise license. If you are using the Community Edition of NebulaGraph, you do not need to deploy LM.

Before deploying NebulaGraph Enterprise 3.5.0 or later using Operator, you first need to deploy [License Manager (LM)](../../9.about-license/2.license-management-suite/3.license-manager.md) and configure the NebulaGraph Enterprise [License](../../9.about-license/1.license-overview.md) in LM. LM is a standalone service used to manage the NebulaGraph license. LM checks the validity of the license when NebulaGraph Enterprise database starts. If the License is invalid, the database will not be able to start.

Expand Down Expand Up @@ -45,7 +45,7 @@ For information on how to deploy LM on a machine outside the K8s cluster, see [L
--docker-password=DOCKER_PASSWORD
```

- <image-pull-secret>: Specify the name of the Secret.
- `<image-pull-secret>`: Specify the name of the Secret.
- DOCKER_REGISTRY_SERVER: Specify the address of the private repository server from which the image is pulled, for example, `reg.example-inc.com`.
- DOCKER_USER: Image repository username.
- DOCKER_PASSWORD: Image repository password.
Expand Down
2 changes: 1 addition & 1 deletion ...nebula-operator/3.deploy-nebula-graph-cluster/3.1create-cluster-with-kubectl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

{{ ent.ent_begin }}

- [LM has been installed and the License Key has been successfully loaded](3.0.deploy-lm.md)
- [LM has been installed and the License Key has been successfully loaded](3.0.deploy-lm.md) (Enterprise only)

{{ ent.ent_end }}

Expand Down
5 changes: 2 additions & 3 deletions ....0/nebula-operator/3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

{{ ent.ent_begin }}

- [LM has been installed and the License Key has been successfully loaded](3.0.deploy-lm.md)
- [LM has been installed and the License Key has been successfully loaded](3.0.deploy-lm.md) (Enterprise only)

{{ ent.ent_end }}

Expand Down Expand Up @@ -46,7 +46,7 @@

{{ent.ent_begin}}

5. Create a Secret for pulling the NebulaGraph cluster image from a private repository.
5. Create a Secret for pulling the NebulaGraph cluster image from a private repository (Enterprise only).

```bash
kubectl -n "${NEBULA_CLUSTER_NAMESPACE}" create secret docker-registry <image-pull-secret> \
Expand Down Expand Up @@ -118,7 +118,6 @@
nebula-storaged-2 1/1 Running 0 5m34s
```


## Scaling clusters

- The cluster scaling feature is for NebulaGraph Enterprise Edition only.
Expand Down
2 changes: 1 addition & 1 deletion mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -726,7 +726,7 @@ nav:
#ent
- Balance storage data after scaling out: nebula-operator/8.custom-cluster-configurations/8.3.balance-data-when-scaling-storage.md
- Manage cluster logs: nebula-operator/8.custom-cluster-configurations/8.4.manage-running-logs.md
- Upgrade NebulaGraph clusters: nebula-operator/9.upgrade-nebula-cluster.md
# - Upgrade NebulaGraph clusters: nebula-operator/9.upgrade-nebula-cluster.md
- Specify a rolling update strategy: nebula-operator/11.rolling-update-strategy.md
#ent
- Backup and restore: nebula-operator/10.backup-restore-using-operator.md
Expand Down