Skip to main content
Connect a Red Hat OpenShift cluster so CloudThinker agents can report its version and available updates, find degraded cluster operators, check node readiness, catch crash-looping and failing pods, and review how routes are exposed. The connection uses a service account token bound to OpenShift’s cluster-reader role, and is read-only by design: agents can describe the cluster and cannot change it.

Prerequisites

  • An HTTPS path from CloudThinker to the cluster’s API server, usually on port 6443. On CloudThinker Cloud, allow CloudThinker’s egress IPs: these docs don’t publish the list, so ask your CloudThinker contact, or contact us. See Reaching private services. On a self-hosted deployment, allow your CloudThinker deployment.
  • The oc command-line tool, signed in to the cluster as a user who can create service accounts and bind cluster roles, such as a cluster administrator.
  • The Admin role in your CloudThinker workspace, which can add and edit connections. See Roles.

Setup

1

Create a service account

Create a project for CloudThinker and a service account in it, instead of reusing a person’s account:
2

Grant read access

Bind the service account to the cluster-reader cluster role, which can view most objects in the cluster but can’t modify them:
To limit agents to a few projects instead, see Required permissions.
3

Create a token

The command prints the token. 2160h asks for 90 days, but the cluster can return a token with a shorter or longer lifetime. When the token expires, the connection stops working: create a new one and enter it in the connection.
4

Get the API server address and CA certificate

Print the API server address of the cluster oc is signed in to:
By default, an internal OpenShift CA issues the API server’s certificate, so CloudThinker can’t verify it without that CA. Print the CA certificate from your oc configuration:
If the command prints nothing, ask your cluster administrator for the certificate of the CA that issued the API server’s certificate. If the API server uses a certificate from a publicly trusted CA, you can skip this.
5

Add the connection in CloudThinker

In the sidebar, click More → Workspace settings → Connections. On the Builtin Connections tab, search for Red Hat OpenShift and click Connect. Fill in the fields from Connection details and click Connect.CloudThinker tests the token by reading the cluster version.Success state: the message reads Red Hat OpenShift connected; the cluster runs <version>. and the connection shows Connected.

Connection details

TLS verification always stays on, because the token travels with every request. Leave Cluster CA certificate empty only when the API server’s certificate comes from a publicly trusted CA. CloudThinker doesn’t follow redirects, so enter the address the API server answers on directly.

Required permissions

The token sees exactly what its service account can read. Pick one: For project access, run this once per project, replacing <project>:
The connection test reads the cluster version, which belongs to the cluster rather than to a project. If Connect shows The service account cannot read the cluster version., grant that one read:
With project access, agents name every part of the cluster they couldn’t read, such as nodes and cluster operators, instead of reporting it as empty.
Never bind the service account to an edit or admin role. The connection has no way to send a change, so write access only adds risk if the token leaks.

Agent capabilities

When a token can’t list pods across the cluster, agents scan up to 10 of the projects it can see, and you can ask about one project by name. A count ending in + means more exist than the agent read. Agents read the cluster live for every answer and don’t store its state. Agents can’t upgrade the cluster, cordon nodes, scale or restart workloads, or edit routes. Ask for a change and the agent tells you to make it with oc or the OpenShift web console.

Verify the connection

Expected result: the full cluster version, any available updates, and the operators, nodes, and pods that need attention, each by name.

Example prompts

Replace payments with one of your projects.

Troubleshooting

Except for the last one, the accordion titles below are the exact messages CloudThinker shows when the connection test fails.
The API server uses a certificate from a CA that CloudThinker doesn’t trust, which is the default on OpenShift. Paste the CA certificate from Get the API server address and CA certificate into Cluster CA certificate, then connect again.
Paste the certificate as PEM text, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines. If you copied certificate-authority-data, decode it with base64 --decode first.
The token expired, was revoked, or was copied incompletely. Create a new token as in the token step, and paste it as one line into Service account token.
The token works, but its service account can’t read the cluster version. Bind cluster-reader, or for project access grant the cluster version read in Required permissions, then connect again.
Check the API server URL, including the port (usually 6443), and that the network path in Prerequisites is open.
Enter only the https:// address and port, with no path. The web console address is not the API server: print the right one with the oc config view command in Setup.
The address reached something other than the OpenShift API, such as the web console or a load balancer page. The same fix applies to That API server has no OpenShift cluster version. Is it OpenShift?, which also appears for a plain Kubernetes cluster: use the Kubernetes connection for those. If the message starts OpenShift answered and mentions a redirect code, enter the address the API server answers on directly.
The service account has project access only. Bind cluster-reader to read nodes and cluster operators, or ask about a project the service account can read.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Use a dedicated read-only service account with an expiring token. You can revoke it without affecting other tools, and a leaked token stops working on its own.
  • Token stays on your API server. CloudThinker sends the token only to the API server URL you enter, always verifies the server’s certificate, and never follows a redirect.

Kubernetes

Inspect workloads, rollouts, logs, and node pressure in other clusters

Rancher

List managed clusters, projects, and nodes, and review who has access