Skip to content

Update the high availability docs to use the correct label #12

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

Closed
bkimbrough88 wants to merge 1 commit into from
Closed

Update the high availability docs to use the correct label #12

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 doc/content/en/04-administration-guide/09-high-availability/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ There are two different ways to accomplish this. The first one is with the `kube
To identify the primary node:

```
$ kubectl get pods -n default -l app=StackGresCluster -l role=master
$ kubectl get pods -n default -l app=StackGresCluster -l role=primary
NAME READY STATUS RESTARTS AGE
stackgres-0 5/5 Running 0 165m
```
Expand Down Expand Up @@ -76,4 +76,4 @@ We can retrieve some valuable information here:
- Who are the replica nodes
- The IP address and port
- The state of each node
- The lag in MB in case some nodes are not up-to-date
- The lag in MB in case some nodes are not up-to-date