> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Read a cluster's overview and health

> Read what a cluster's Overview and Health pages report, what each health score and check means, and where to go when one is not healthy.

A cluster's **Overview** says in one screen whether it is connected, what needs you and how healthy it is. Its **Health** page breaks the health down into scores and five checks, each with a button to the page that explains it. This guide takes you through both, in about five minutes, and says where to go when a check is not healthy.

## Before you start

* **A cluster connected to Ankra.** Both pages read what the cluster agent reports. While the agent is offline they show the last readings and say so.
* **Permission to read the cluster.** Every built-in role can read clusters ([Roles and access](https://docs.ankra.ai/guides/roles-and-access.md)).

## 1. Open the cluster's Overview

Go to **Infrastructure → Clusters → \<your cluster>** (`/next/clusters/<cluster-id>`). **Clusters** is in the main menu under **Infrastructure**, in the **Platform** group. **Overview** is the first item of the cluster menu.

Under the cluster's name, the header gives its environment, Kubernetes version and when it was created, and a badge for its connection:

| Badge | Meaning |
| - | - |
| **Connected** | The agent is online. |
| **Offline** | The agent is disconnected. The page says "Live updates are paused." and "The cluster agent is disconnected. Readings may be out of date; workloads may still be running.", with **Check connection**. |
| **Connection unknown** | Ankra could not tell. |
| **Archived** or **Being deleted** | The cluster is leaving Ankra. |

The header also holds **Settings**, **Clone cluster** ([Clone a cluster](https://docs.ankra.ai/guides/clone-cluster.md)) and **Reconcile cluster**, which applies each Stack's saved definition again: changes made directly on the cluster to what a Stack deploys can be replaced by the saved definition, nothing is changed in Git, and nothing outside the Stacks is touched.

**Check:** the badge reads **Connected**. If it reads **Offline**, go to [When health is unknown](#5-when-health-is-unknown).

## 2. Read the Overview from the top

| Section | What it tells you | Where it leads |
| - | - | - |
| Notices | A setup that stopped ("Setup stopped before this cluster was ready"), a stop or start in progress, an agent or add-on that needs a security update | **See what went wrong**, **Stop, start and schedules** |
| **Needs you** | The latest operation, when it failed, with what to do about it; and the resources whose latest change failed | **Review operation**, **See the error** or **Review failed runs**, **Open in stack**, **Browse operations** |
| **Reported health** | The health badge, **Overall score**, **Nodes ready**, **Pods running** (with pending, failed, crash-looping and image pull failures) and **Add-ons healthy** (with degraded and progressing) | **View health**, **Browse nodes**, the counts open the matching pods and add-ons |
| **Resource usage** | CPU and memory used against capacity over the last hour, in 1-minute samples | |
| **Agent and GitOps** | Whether the agent is online, its **Agent version** and any upgrade, its **Last check-in**, and whether a GitOps repository is connected and on which branch | |
| **Workloads and resources** | How many Stacks, add-ons and manifests the cluster runs, its Deployments, StatefulSets, DaemonSets and CronJobs, and its services, ingresses and namespaces | **Browse pods**, **Browse stacks** |
| **Add-ons** | The main add-ons with their chart, version, a newer version when one is available, their Stack and health | **Browse add-ons**, **Manage add-ons and stacks** |
| **Recent operation** | The latest operation, when it did not fail | **Browse operations** |

When pods crash-loop, fail or cannot pull their image, add-ons are degraded or nodes are not ready, **Reported health** also shows **Ask Ankra why**. It sends Ankra AI the question "What is causing ... on this cluster?" with what is wrong filled in.

The line under **Reported health** says how fresh the readings are: "Read live from the cluster.", "Served from the platform cache, N seconds old." or, past five minutes, "Served from the platform cache, N minutes old: stale."

**Check:** no **Needs you** section means the latest operation did not fail and no resource's latest change failed.

## 3. Open the Health page

Click **View health**, or go to **Infrastructure → Clusters → \<your cluster> → Health** (`/next/clusters/<cluster-id>/health`). The page is headed **Cluster health**. **Refresh health** reads everything again.

### The scores

**Reported health** carries a badge and four scores:

| Badge | Meaning |
| - | - |
| **Healthy** | Overall score 90% or more |
| **Warning** | Overall score from 70% to 89% |
| **Critical** | Overall score from 1% to 69%, or no node is ready |
| **Not reported** | The cluster reported no score |
| **Unknown** | The readings are not recent enough to judge; see [step 5](#5-when-health-is-unknown) |

| Score | How Ankra works it out |
| - | - |
| **Node health** | Ready nodes as a share of all nodes |
| **Pod health** | Running and succeeded pods as a share of all pods, less half the share of failed pods |
| **Add-on health** | Healthy add-ons as a share of all add-ons, less 30% of the share of degraded ones |
| **Overall score** | 30% node health, 25% pod health, 25% Deployment readiness (ready Deployments as a share of all) and 20% add-on health |

A cluster with no nodes, pods or add-ons scores 100% on that part. While the agent is offline, Ankra reports no score.

### The health checks

Each check reports what the cluster last observed and has a button to the page that explains it. A check has no pass or fail of its own: read the counts.

| Check | What it reports | Button |
| - | - | - |
| **Nodes** | Nodes ready, unavailable and in total | **Inspect nodes** |
| **Pods** | Pods running, pending and failed; crash-looping, with image pull failures, and unknown | **Inspect pods** |
| **Add-ons** | Add-ons healthy, degraded, progressing and unknown | **Inspect add-ons** |
| **Cluster agent** | "Reported online" or "Reported offline", the agent's version and its last check-in | **Agent settings** |
| **GitOps** | "Repository connected on \<branch>" or "Repository not connected" | **Inspect operations** |

The page says it plainly: these are cluster observations, and running pods and a connected repository do not prove application availability.

Under the checks, **Runtime** charts what each node group used over the last hour: **CPU used**, **Memory used**, **Network traffic** and **Disk used**.

## 4. Go from a check that is not healthy

| What you see | Where to go |
| - | - |
| **Nodes**: some unavailable | **Inspect nodes**, open the node, and read its **Conditions** and **Workload impact** ([Kubernetes nodes](https://docs.ankra.ai/platform/kubernetes-nodes.md)). For the machine behind it, see [Nodes](https://docs.ankra.ai/platform/cluster-nodes.md). |
| **Pods**: pending, failed, crash-looping or image pull failures | **Inspect pods** and open the pod ([Kubernetes resources](https://docs.ankra.ai/platform/kubernetes-insights.md)). Read its [logs](https://docs.ankra.ai/platform/logs.md), including the previous container's after a crash. To look inside, start a [debug pod](https://docs.ankra.ai/platform/debug-pods.md). |
| **Add-ons**: degraded or progressing for long | **Inspect add-ons** and open the add-on. If its last deploy failed, the operation has the error and a retry ([Operations](https://docs.ankra.ai/platform/operations.md)). |
| **Cluster agent**: Reported offline | **Agent settings**, then [Agent not connecting](https://docs.ankra.ai/concepts/cluster-agent.md#agent-not-connecting). |
| **GitOps**: Repository not connected | To connect a repository, see [GitOps](https://docs.ankra.ai/concepts/gitops.md). A sync that failed shows as a failed operation: **Inspect operations**. |
| A failed operation under **Needs you** on the Overview | **Review operation**, then [find out why it failed and retry it](https://docs.ankra.ai/platform/operations.md). |
| Usage high or rising | [Cluster metrics](https://docs.ankra.ai/platform/cluster-metrics.md), with the time range widened and the namespace filter set. |

When the cause is not obvious, click **Ask Ankra why** on the Overview, or ask [Ankra AI](https://docs.ankra.ai/platform/ai-assistant.md) about the cluster.

## 5. When health is unknown

When the readings are not recent, the Health page shows **Current health is unknown**, withholds the scores, and renames **Health checks** to **Last reported checks**. The alert says why:

| The page says | What to do |
| - | - |
| "The cluster agent is offline. These are the last reported readings." | Check the agent on **Settings → Agent** and follow [Agent not connecting](https://docs.ankra.ai/concepts/cluster-agent.md#agent-not-connecting). |
| "Readings are N minutes old. Current health is unknown." | Readings older than five minutes are not current. Click **Refresh health**; if they stay old, check the agent. |
| "The platform could not confirm a successful sync. Current health is unknown." | Click **Refresh health**. If it repeats, check the agent and **Operations**. |
| "Data freshness was not reported. Current health is unknown." or "The age of the cached readings is unknown. Current health is unknown." | Click **Refresh health**. |

If the page cannot read the cluster at all, it says "Cluster health could not be read." and "Previous readings cannot confirm current health." The Overview says "The cluster overview could not be read." Click **Try again**.

## From the CLI and MCP

The CLI reads the same signals without the portal:

```bash theme={null}
# The cluster's state, Kubernetes version and node count
ankra cluster info

# Nodes and pods, and the warnings Kubernetes recorded
ankra cluster get nodes
ankra cluster get pods --all-namespaces
ankra cluster events --all-namespaces --type Warning

# Failed operations that still need someone
ankra cluster operations list --attention open
```

Over MCP, `get_cluster_status` returns the cluster's health overview and `get_cluster_insights` the platform's own AI health diagnoses ([MCP tools](https://docs.ankra.ai/platform/mcp-tools.md)).

## Verify

The cluster is in good shape when:

* the Overview's badge reads **Connected** and it shows no **Needs you** section,
* the Health page's badge reads **Healthy**, with no **Current health is unknown** alert,
* **Nodes** shows 0 unavailable, **Pods** 0 failed and 0 crash-looping, **Add-ons** 0 degraded, and **Cluster agent** "Reported online".

## Where to go next

* [Cluster metrics](https://docs.ankra.ai/platform/cluster-metrics.md) - usage over time, per node and namespace
* [Operations](https://docs.ankra.ai/platform/operations.md) - read a failed step and retry it
* [Alerts](https://docs.ankra.ai/guides/alerts.md) - be told when a cluster turns unhealthy instead of checking
* [Home](https://docs.ankra.ai/platform/home.md) - what needs you across the organisation


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.