Doc-482 self-managed update of REDPANDA variable (#972)

redpanda-data · Jan 31, 2025 · d460ad6 · d460ad6
1 parent 92d4f9b
commit d460ad6
Showing 1 changed file with 8 additions and 7 deletions.
diff --git a/modules/reference/pages/rpk/rpk-container/rpk-container-status.adoc b/modules/reference/pages/rpk/rpk-container/rpk-container-status.adoc
@@ -19,15 +19,16 @@ endif::[]
 
 [,bash]
 ----
-$ rpk container status
-    NODE-ID  STATUS   KAFKA-ADDRESS    ADMIN-ADDRESS    PROXY-ADDRESS    
-    0        running  127.0.0.1:34189  127.0.0.1:36539  127.0.0.1:41235  
-    1        running  127.0.0.1:45523  127.0.0.1:35135  127.0.0.1:40155  
-    2        running  127.0.0.1:37223  127.0.0.1:42571  127.0.0.1:41907  
+rpk container status
+NODE-ID  STATUS   KAFKA-ADDRESS   ADMIN-ADDRESS   PROXY-ADDRESS   SCHEMA-REGISTRY-ADDRESS
+0        running  127.0.0.1:9092  127.0.0.1:9644  127.0.0.1:8082  127.0.0.1:8081
 
-You can use rpk to interact with this cluster. For example:
+Redpanda Console started in: http://localhost:8080
 
-    rpk cluster info --brokers 127.0.0.1:34189,127.0.0.1:45523,127.0.0.1:37223
+You can use rpk to interact with this cluster. E.g:
+
+    rpk cluster info
+    rpk cluster health
 
 You may also set an environment variable with the comma-separated list of
 broker addresses: