Red Hat Openshift
Red Hat OpenShift is an enterprise Kubernetes container platform that enables organizations to build, deploy, and manage containerized applications at scale. As a comprehensive container orchestration and application platform, OpenShift provides developer and operational tools for managing the entire application lifecycle from development through production.
| Category | Containers |
| Direction | Query source |
| Sign-in | Kubeconfig File |
| Query languages | SQLite |
| Tables | 8 |
| Query templates | 47 |
| Website | redhat.com |
Before you start
Huntbase signs in to Red Hat Openshift with Kubeconfig File. Create the credential in Red Hat Openshift first, then keep it to hand for the Connect step.
- Log in with the OpenShift CLI as the user whose access Huntbase should use, for example
oc login <cluster_url> --web. You can also select Copy login command from the username drop-down menu at the top right of the web console and run that command. - Use the kubeconfig that
ocwrites after login, by default~/.kube/config.
- Running
oc logoutdeletes the saved token from the server and from the kubeconfig, which breaks the connection.
For the vendor's own instructions, see OpenShift CLI login documentation.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect Red Hat Openshift
- Go to Connections and click New connection, or click New connection on the Red Hat Openshift product page.
- On Product, pick Red Hat Openshift and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Settings
Where your Red Hat Openshift lives:
| Field | Required | Notes |
|---|---|---|
| Kubeconfig Path | No | |
| Kubeconfig Context | No | The kubeconfig context to use. Leave it empty to use the current context. |
Credentials
The only Method is Kubeconfig File. Enter a Credential label (for example Production), then fill in:
| Field | Required | Notes |
|---|---|---|
| Kubeconfig File | Yes | Secret — not shown again after you save it. |
Query it
Once connected, Red Hat Openshift can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| SQLite | SQL over the 8 tables listed below, alongside every other connected source. |
Example: SQLite
List OpenShift Route Ingresses — Retrieve ingress details for all OpenShift routes, showing UID, name, namespace, and ingress configuration.
select
uid,
name,
namespace,
ingress
from
openshift_route;
Red Hat Openshift ships with 47 query templates. Find them in Library › Queries — see Query templates.
Tables
Red Hat Openshift adds 8 tables. Browse their columns from Schema in the query bar's ⋯ menu.
All 8 tables
| Table | Contains |
|---|---|
openshift_build | Retrieve information about OpenShift builds. |
openshift_build_config | Retrieve information about OpenShift build configs. |
openshift_deployment_config | Retrieve information about OpenShift deployment configs. |
openshift_image_stream | Retrieve information about OpenShift image streams. |
openshift_oauth_access_token | Retrieve information about OpenShift OAuth access tokens. |
openshift_project | Retrieve information about OpenShift projects. |
openshift_route | Retrieve information about OpenShift routes. |
openshift_user | Retrieve information about OpenShift users. |
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog