> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.9/add-on-health.md).

# Add On Health

Add-ons operate as independent applications within a cluster. Each add-ons health status is reported back to the SaaS Management Plane and can be viewed on the Clusters Details Page.

You can view Add-on Health by navigating to Infrastructure -> Clusters -> Cluster Details -> Add-ons

Add-ons can be in one of the following states:

* Healthy - Add-on is up and running and healthy
* Error - Add-on has run into an error during or after installation.
* Installing - Add-on is being installed
* Installation Failed - Add-on installation failed.

At this point, the PMK dashboard does not provide visibility into errors when an add-on runs into an error state. You need to contact Platform support for help with triaging the add-on health issue.

<figure><img src="https://3967081272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7OvBu55YygcqVDnKSi7Y%2Fuploads%2Fgit-blob-1b764a3c122d907fe9ef1c324ef70fe1c12e8cb7%2Frrk197u22auwwvl7omo9tcxf568cyybakrw1x6kn3gema8p1darsx9twlt2pudt2.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-kubernetes/5.9/add-on-health.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.