Skip to content

Commit

Permalink
Update 4.connect-to-nebula-graph-service.md
Browse files Browse the repository at this point in the history
  • Loading branch information
abby-cyber committed Nov 15, 2021
1 parent 587afeb commit 6d0fe54
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs-2.0/nebula-operator/4.connect-to-nebula-graph-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,15 +170,15 @@ data:

Steps are as follows.

1. Create a file named `nginx-ingress-daemonset-hostnetwork.yaml`. The YAML file reads as follows:
1. Create a file named `nginx-ingress-daemonset-hostnetwork.yaml`.

Click on [nginx-ingress-daemonset-hostnetwork.yaml](https://github.com/vesoft-inc/nebula-operator/blob/{{operator.branch}}/config/samples/nginx-ingress-daemonset-hostnetwork.yaml) to view the complete content of the example YAML file.

!!! note

The resource objects in the YAML file above use the namespace `nginx-ingress`. You can run `kubectl create namespace nginx-ingress` to create this namespace, or you can custom a different namespace.
The resource objects in the YAML file above use the namespace `nginx-ingress`. You can run `kubectl create namespace nginx-ingress` to create this namespace, or you can customize the namespace.

2. Label a node where runs the DaemonSet named `nginx-ingress-controller` in the above YAML file (The node used in this example is named `worker2` with an IP of `192.168.8.160`).
2. Label a node where the DaemonSet named `nginx-ingress-controller` in the above YAML file (The node used in this example is named `worker2` with an IP of `192.168.8.160`) runs.

```bash
kubectl label node worker2 nginx-ingress=true
Expand Down Expand Up @@ -207,9 +207,9 @@ Steps are as follows.
daemonset.apps/nginx-ingress-controller created
```

Since the network type is configured in Nginx Ingress is `hostNetwork`, after successfully deploying Nginx Ingress, you can access Nebula Graph through the IP (`192.168.8.160`) of the node where Nginx Ingress deployed and the external port (`9769`) you define.
Since the network type that is configured in Nginx Ingress is `hostNetwork`, after successfully deploying Nginx Ingress, with the IP (`192.168.8.160`) of the node where Nginx Ingress is deployed and with the external port (`9769`) you define, you can access Nebula Graph.

4. Run the following command to create a console used to connect to Nebula Graph and to access Nebula Graph databases with the IP (`192.168.8.160`) of the node where Nginx Ingress deployed and the external port you define.
4. Use the IP address and the port configured in the preceding steps. You can connect to Nebula Graph with Nebula Console.

```bash
kubectl run -ti --image vesoft/nebula-console:{{console.branch}} --restart=Never -- <nebula_console_name> -addr <host_ip> -port <external_port> -u <username> -p <password>
Expand Down

0 comments on commit 6d0fe54

Please sign in to comment.