RHELS LAB

Plane 02 · run

The workload cluster

OpenShift 4.22 (CRC) — every namespace is managed by OpenShift GitOps via AppProjects and ApplicationSets. Apps follow strict conventions so the platform can stay boring and predictable.

Inside this chapter

  1. 1 · The jobs The doors onto the factory floor — console, live state, a namespace of your own.
  2. 2 · What runs here OpenShift and its operators, how apps are watched, and the naming rules.
  3. 3 · The data The applications table, at the back where reference belongs.

Start here

The jobs this cluster does for you

You are on the factory floor — this is the OpenShift cluster where finished apps run. Its front door is the console, and your badge is the same LDAP account as everywhere else.

Open the console The cluster's front door — sign in with your LDAP account and you are on the floor. See what's running Live state lives in Argo CD — if it isn't green there, it isn't healthy, whatever any snapshot says. Get a namespace Every app starts as a requested namespace — never hand-made, always from the service. Add your app Chapter 5 walks an app from idea to Healthy in six steps — this is where yours lands. Sign in once One LDAP account opens the console, Argo CD, and everything else on this floor. When an app is sick Runbooks first, heroics second — the floor's fixes are written down before you need them.

Concepts

What runs here, and why

Operators

OpenShift GitOps v1.21

Argo CD 3.4.7, manages all namespaces via AppProjects/ApplicationSets

Monitoring

  • ▸ Prometheus (kube-prometheus-stack)
  • ▸ Grafana
Observability →

Naming conventions

  • ▸ BSN format: app + 4 digits (7 chars, e.g. app1004)
  • ▸ one namespace per app-env, e.g. app1001-dev
  • ▸ one private IAC repo per app: rhels/IAC.app1001
Add an app →

Reference

The applications, as data

A snapshot from the inventory, taken when this site was built — for the live picture, Argo CD is the truth (the "See what's running" door above).

Applications

BSN Language Namespace IaC repo Health
app1001 Java app1001-dev rhels/IAC.app1001 Healthy
app1002 Python app1002-dev rhels/IAC.app1002 Healthy
app1003 Redis-backed app1003-dev rhels/IAC.app1003 Healthy

Next chapter

3. CI/CD & supply chain

You know where apps run. Next, the thread that connects the two planes: how a git push becomes a running pod.