feedc0de/my-rook-config
1
0 Fork 0
forked from rook/rook
Code Pull Requests Activity

Merge pull request #3820 from krig/yugabyte-doc

Browse Source 
Doc (Yugabyte DB): Fix hostname in API connection (#3816)
This commit is contained in:
Alexander Trost authored and GitHub committed 2019-09-23 10:01:56 +02:00
2 parents f96960cfcc c2b75db41c
commit ba12167ff5
1 file changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/yugabytedb.md
+3 -3
View File
@@ -74,8 +74,8 @@ kubectl -n rook-yugabytedb-system logs -l app=rook-yugabytedb-operator
If everything is OK in the operator logs, check the YugabyteDB Master & TServer logs next.
```console
kubectl -n rook-yugabytedb logs -l app=yb-master-rook-yugabytedb
kubectl -n rook-yugabytedb logs -l app=yb-tserver-rook-yugabytedb
kubectl -n rook-yugabytedb logs -l app=yb-master-hello-ybdb-cluster
kubectl -n rook-yugabytedb logs -l app=yb-tserver-hello-ybdb-cluster
```
## Access the Database
@@ -83,7 +83,7 @@ kubectl -n rook-yugabytedb logs -l app=yb-tserver-rook-yugabytedb
After all the pods in YugabyteDB cluster are running, you can access the YugabyteDB's postgres compliant `ysql` api. Run following command to access it.
```console
kubectl exec -it yb-tserver-rook-yugabytedb-0 /home/yugabyte/bin/ysqlsh -- -h yb-tserver-rook-yugabytedb-0 --echo-queries
kubectl -n rook-yugabytedb exec -it yb-tserver-hello-ybdb-cluster-0 /home/yugabyte/bin/ysqlsh -- -h yb-tserver-hello-ybdb-cluster-0 --echo-queries
```
Refer the [YugabyteDB documentation](https://docs.yugabyte.com/latest/quick-start/explore-ysql/#kubernetes) for more details on the `ysql` api.