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

# Clusters

> Register and manage your Kubernetes clusters in Obsy.

Clusters are the foundation of Obsy's infrastructure management. Every OTel collector deployment, sampling config, and telemetry flow is scoped to a cluster.

Go to **Clusters** in the sidebar.

***

## Adding a cluster

See [Connect a cluster](/getting-started/connect-cluster) for the full guide.

Quick summary:

1. **Clusters → Add cluster**
2. Enter name, display name, and kubeconfig
3. Click **Save** — Obsy validates connectivity immediately

***

## Cluster detail

Click any cluster to open its detail page, which shows:

| Section            | Content                                           |
| ------------------ | ------------------------------------------------- |
| **Overview**       | Connection status, Kubernetes version, node count |
| **OTel Collector** | Collector health card, install/reinstall button   |
| **Sampling**       | Active sampling configuration and quick-edit link |
| **Telemetry**      | Last telemetry received per signal type           |

***

## Connection status

| Status          | Meaning                                                      |
| --------------- | ------------------------------------------------------------ |
| **Connected**   | API server reachable, credentials valid                      |
| **Unreachable** | API server not responding (network issue or cluster is down) |
| **Auth error**  | Credentials expired or insufficient permissions              |

Obsy checks connectivity every 5 minutes. If a cluster goes unreachable, a warning appears on the cluster card but existing data (reports, sampling configs) is preserved.

***

## Updating cluster credentials

If your kubeconfig rotates (e.g. service account token refresh):

1. Open the cluster detail.
2. Click **Edit cluster**.
3. Paste the new kubeconfig.
4. Click **Save**.

***

## Multiple clusters

You can register as many clusters as needed. Sampling configurations, telemetry standards, and reliability reports are managed per-cluster. Incidents, alerts, and services are organization-wide.

***

## Removing a cluster

Open the cluster detail and click **Remove cluster**. This removes the cluster from Obsy but does **not** uninstall the OTel collector Helm release. Uninstall manually:

```bash theme={null}
helm uninstall obsy-collector -n obsy-system
kubectl delete namespace obsy-system
```