Update output from kubectl gs get clusters (#2274)

* Update output from kubectl gs get clusters Signed-off-by: Matias Charriere <[email protected]> * update review date Signed-off-by: Matias Charriere <[email protected]> --------- Signed-off-by: Matias Charriere <[email protected]>
giantswarm · Aug 12, 2024 · fdd7c2c · fdd7c2c
1 parent fbf4b2c
commit fdd7c2c
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/src/content/vintage/use-the-api/kubectl-gs/get-clusters.md b/src/content/vintage/use-the-api/kubectl-gs/get-clusters.md
@@ -9,7 +9,7 @@ menu:
 user_questions:
   - How can I list clusters using kubectl?
   - How can I inspect clusters using kubectl?
-last_review_date: 2024-01-18
+last_review_date: 2024-08-12
 aliases:
   - /use-the-api/kubectl-gs
   - /reference/kubectl-gs/get-clusters/
@@ -35,9 +35,9 @@ to list some information on all clusters available to you in the current install
 For a Cluster API management cluster, the result looks like this:
 
 ```nohighlight
-NAME         AGE   CONDITION   CLUSTER VERSION   PREINSTALLED APPS VERSION   SERVICE PRIORITY   ORGANIZATION            DESCRIPTION
-operations   64d   READY                                                     highest            giantswarm-production   Operations cluster
-gazelle      89d   READY                                                     highest            giantswarm              Management cluster
+NAMESPACE                   NAME         AGE    CONDITION   RELEASE   SERVICE PRIORITY   ORGANIZATION            DESCRIPTION
+org-giantswarm-production   operations   270d   READY       28.1.0    highest            giantswarm-production   Operations Cluster
+org-giantswarm              gazelle      296d   READY       25.0.0    highest            giantswarm              Management Cluster
 ```
 
 Here is some example output from a vintage management cluster: