From 87a0c5171170e4c473e1c13d04ef15e54977de4e Mon Sep 17 00:00:00 2001
From: Brandon Kimbrough <53441835+bkimbrough88@users.noreply.github.com>
Date: Fri, 11 Jul 2025 11:36:46 -0400
Subject: [PATCH] Update the high availability docs to use the correct label

---
 .../en/04-administration-guide/09-high-availability/_index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/content/en/04-administration-guide/09-high-availability/_index.md b/doc/content/en/04-administration-guide/09-high-availability/_index.md
index d458dbf918..67d563c8ce 100755
--- a/doc/content/en/04-administration-guide/09-high-availability/_index.md
+++ b/doc/content/en/04-administration-guide/09-high-availability/_index.md
@@ -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
 ```
@@ -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
\ No newline at end of file
+- The lag in MB in case some nodes are not up-to-date