From c2b7c035f34b5ed72bc8396786b4b2dd075ad391 Mon Sep 17 00:00:00 2001 From: Raghu Katti Date: Mon, 9 Mar 2020 12:29:38 -0400 Subject: [PATCH] Added cluster-health check instructions (#18958) * Added cluster-health check instructions * Added cluster info command Added cluster info command * Fixed Cluster health check instruction * Fixed typo in documentation --- .../en/docs/tasks/debug-application-cluster/debug-cluster.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/tasks/debug-application-cluster/debug-cluster.md b/content/en/docs/tasks/debug-application-cluster/debug-cluster.md index ae56c42411..495545ee1a 100644 --- a/content/en/docs/tasks/debug-application-cluster/debug-cluster.md +++ b/content/en/docs/tasks/debug-application-cluster/debug-cluster.md @@ -29,6 +29,11 @@ kubectl get nodes And verify that all of the nodes you expect to see are present and that they are all in the `Ready` state. +To get detailed information about the overall health of your cluster, you can run: + +```shell +kubectl cluster-info dump +``` ## Looking at logs For now, digging deeper into the cluster requires logging into the relevant machines. Here are the locations