# Red Hat OpenShift (ROSA) inventory and tuning | ZopNight

> Connect ROSA clusters through OpenShift Cluster Manager, grant access one cluster at a time, see the workloads, and resize worker pools and the autoscaler.

Source: https://zop.dev/zopnight/openshift

---

_ROSA, through OpenShift Cluster Manager_

## Connect OpenShift clusters.

ZopNight connects to Red Hat OpenShift Service on AWS (ROSA) the way OpenShift expects: through OpenShift Cluster Manager, with cluster access you grant explicitly, one cluster at a time. Then it shows the workloads and lets you resize worker pools.

- 3 — ways to connect a cluster
- 5 — OpenShift-native kinds shown
- 2 — things to tune: pools, autoscaler
- 0 — writes without your say-so

Free to start. No card. The playground just needs your work email.

## Connected on purpose.

Nothing touches a cluster until you say so.

- 01. Connect the organisation — ZopNight links to your OpenShift Cluster Manager organisation and lists your ROSA clusters and their worker pools.
- 02. Grant access per cluster — Automatically, by logging in to the cluster, or with a service account token. Nothing is written to a cluster until you choose to connect it.
- 03. See the workloads — The full Kubernetes set plus Routes, DeploymentConfigs, BuildConfigs, ImageStreams and Projects, shown beside their Kubernetes counterparts.
- 04. Tune it — Resize a worker pool or set an autoscaling range, and edit the cluster autoscaler, all through OpenShift Cluster Manager.

## Built for how Red Hat runs it.

Different from EKS, GKE and AKS, and treated that way.

- Why it differs: An OpenShift Cluster Manager credential is not a Kubernetes credential. A cluster is listed but not readable until you grant access to it, on purpose.
- Consent: Connecting is an explicit action with a matching disconnect. Opening a page never writes an identity to your cluster.
- Limits: Adding or deleting worker pools is refused, since that provisions or terminates nodes. Scheduling is not offered, because Red Hat manages the workers.
- External auth: The service account method never touches OAuth, so it works on clusters that run external authentication.

## Bring your OpenShift estate into view.

Connect your cluster manager organisation, then connect each cluster when you are ready.

[object Object]