RHELS LAB
Contents · the agent book

Agent book · Start here

Service Directory

One page for every front door in the lab: where it is, how you log in, and — when a credential exists — a link that opens that exact secret in the Vault UI.

This page links to credentials, never shows values. No password, token, or key appears here or anywhere else in this book — every “Open in Vault ↗” link opens the exact secret in the Vault UI, and only works after you have logged in to Vault itself. If a link ever lands on a “not found” in the UI, the secret moved — update this page in the same change that moves it.

Front doors

ServiceURLLoginCredential
Vaultvault.rhels.comToken login — this is the credential store itselfRoot token and unseal key are not in Vault: they live in the mini’s macOS Keychain (vault-crc-lab items), and the unseal key also as the file ~/.vault-unseal-key on the mini
Argo CDargo.rhels.com“Log in via OpenLDAP” (Dex) with your directory accountBreak-glass local admin: Open in Vault ↗ (also held in the argocd-initial-admin-secret Secret, argocd namespace)
Harborharbor.rhels.comLDAP — your directory accountLocal admin (break-glass): Open in Vault ↗ · Kyverno verifier robot: Open in Vault ↗ · CRC pull robot: Open in Vault ↗ · Docs CI robot: Open in Vault ↗
Grafanagrafana.rhels.comLocal admin (anonymous viewer is on)Open in Vault ↗
StackRox Central (ACS)acs.rhels.comLDAP SSO via Dex; your directory account (admins group for Admin)Local admin (break-glass): Open in Vault ↗
Prometheusprom.rhels.comNo login — tailnet only—
AlertManageralerts.rhels.comNo login — tailnet only—
Dex (OIDC issuer)id.rhels.comThis is the login service — Argo and ACS redirect here; you sign in with your directory accountNo credential of its own in Vault: Dex’s LDAP bind password lives only in the argocd-secret Secret (argocd namespace, on the mini)
MCP servermcp.rhels.com/mcpLDAP bind login, then an opaque session tokenYour own directory account — the owner’s is recorded at Open in Vault ↗
Alert bridgebridge.rhels.comNo human login — webhook receiver that turns CRC alerts into GitHub issuesIts GitHub token: Open in Vault ↗
Docs (this site)docs.rhels.comNo login — tailnet only—
OpenLDAPldaps://ldap.rhels.com:636 (plain LDAP on port 389, same name)Bind with your directory accountDirectory admin: Open in Vault ↗ · Service binds: Open in Vault ↗, Open in Vault ↗
OpenShift console (CRC)console.crc.rhels.comOpenShift OAuth → the agentops-ldap provider, your directory account; htpasswd developer is break-glassCRC pull secret: Open in Vault ↗ · htpasswd record: Open in Vault ↗

Credentials with no front door of their own

WhatWhere it is usedCredential
ARC GitHub AppThe CI runners’ GitHub identity (pro scale sets)Open in Vault ↗
ServiceNow PDIdev377665.service-now.com — admin login; the namespace platform’s real ServiceNow backendOpen in Vault ↗ — the platform’s working copies are the pdi-creds Secrets in the clusters and the PDI_PASSWORD GitHub secret
Fixture & smoke-test LDAP accountsdev1, dev2, ops1 (test users) and svc-smoketest (health suite)Open in Vault ↗ and Open in Vault ↗; the health suite’s working copies live in the file ~/workspace/lab-health/.env on the Spark VM
Tailscale operator OAuthLets the mini’s Tailscale operator own the front-door deviceOpen in Vault ↗
Cloudflare DNS-01 tokencert-manager’s Let’s Encrypt challenges for rhels.comOpen in Vault ↗
Argo CD → pro cluster tokenHow the mini’s Argo CD drives the pro clusterOpen in Vault ↗
  • Vault — how the store itself is set up and unsealed.
  • Identity & Access — the directory behind every “your directory account” login above.
  • The cover of this site has the same front doors as a public-safe directory (names and login mechanisms only, no credential paths).