From c2b75db41c5eee689eb8b5c5c76c8b56d4b62523 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kristoffer=20Gr=C3=B6nlund?= Date: Tue, 10 Sep 2019 11:53:12 +0200 Subject: [PATCH] Doc (Yugabyte DB): Fix hostname in API connection (#3816) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use the correct hostname when accessing the API. Resolves: #3816 Signed-off-by: Kristoffer Grönlund --- Documentation/yugabytedb.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/yugabytedb.md b/Documentation/yugabytedb.md index 53d76bf33..dc162fbe5 100644 --- a/Documentation/yugabytedb.md +++ b/Documentation/yugabytedb.md @@ -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.