Skip to content

Commit

Permalink
update commands
Browse files Browse the repository at this point in the history
change version to 2.5.1
fixed command
  • Loading branch information
abby-cyber committed Sep 24, 2021
1 parent e81dc23 commit 4d2c4c9
Showing 1 changed file with 17 additions and 10 deletions.
27 changes: 17 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,17 @@ Nebula Operator manages [NebulaGraph](https://github.com/vesoft-inc/nebula-graph
It evolved from [NebulaGraph Cloud Service](https://www.nebula-cloud.io/), makes NebulaGraph a truly cloud-native database.

## Quick Start
- [Install Nebula Operator](#install-nebula-operator)
- [Create and Destroy](#create-and-destroy-a-nebula-cluster)
- [Resize](#resize-a-nebula-cluster)
- [Failover](#failover)
- [Nebula Operator](#nebula-operator)
- [Quick Start](#quick-start)
- [install nebula operator](#install-nebula-operator)
- [Create and destroy a nebula cluster](#create-and-destroy-a-nebula-cluster)
- [Resize a nebula cluster](#resize-a-nebula-cluster)
- [Failover](#failover)
- [FAQ](#faq)
- [Community](#community)
- [Contributing](#contributing)
- [Acknowledgements](#acknowledgements)
- [License](#license)

### install nebula operator
See [install/uninstall nebula operator](doc/user/install_guide.md) .
Expand All @@ -18,7 +25,7 @@ $ kubectl create -f config/samples/apps_v1alpha1_nebulacluster.yaml
```
A none ha-mode nebula cluster will be created.
```bash
$ kubectl get pods -l app.kubernetes.io/instance=nebula
$ kubectl get pods -l app.kubernetes.io/cluster=nebula
NAME READY STATUS RESTARTS AGE
nebula-graphd-0 1/1 Running 0 1m
nebula-metad-0 1/1 Running 0 1m
Expand Down Expand Up @@ -63,7 +70,7 @@ Modify the file and change `replicas` from 3 to 5.
memory: "1Gi"
replicas: 5
image: vesoft/nebula-storaged
version: v2.5.0
version: v2.5.1
storageClaim:
resources:
requests:
Expand All @@ -78,7 +85,7 @@ $ kubectl apply -f config/samples/apps_v1alpha1_nebulacluster.yaml

The storaged cluster will scale to 5 members (5 pods):
```bash
$ kubectl get pods -l app.kubernetes.io/instance=nebula
$ kubectl get pods -l app.kubernetes.io/cluster=nebula
NAME READY STATUS RESTARTS AGE
nebula-graphd-0 1/1 Running 0 2m
nebula-metad-0 1/1 Running 0 2m
Expand All @@ -101,7 +108,7 @@ Similarly we can decrease the size of the cluster from 5 back to 3 by changing t
memory: "1Gi"
replicas: 3
image: vesoft/nebula-storaged
version: v2.5.0
version: v2.5.1
storageClaim:
resources:
requests:
Expand All @@ -111,7 +118,7 @@ Similarly we can decrease the size of the cluster from 5 back to 3 by changing t
We should see that storaged cluster will eventually reduce to 3 pods:
```bash
$ kubectl get pods -l app.kubernetes.io/instance=nebula
$ kubectl get pods -l app.kubernetes.io/cluster=nebula
NAME READY STATUS RESTARTS AGE
nebula-graphd-0 1/1 Running 0 10m
nebula-metad-0 1/1 Running 0 10m
Expand Down Expand Up @@ -139,7 +146,7 @@ $ kubectl delete pod nebula-storaged-2 --now
The nebula operator will recover the failure by creating a new pod `nebula-storaged-2`:

```bash
$ kubectl get pods -l app.kubernetes.io/instance=nebula
$ kubectl get pods -l app.kubernetes.io/cluster=nebula
NAME READY STATUS RESTARTS AGE
nebula-graphd-0 1/1 Running 0 15m
nebula-metad-0 1/1 Running 0 15m
Expand Down

0 comments on commit 4d2c4c9

Please sign in to comment.