RHELS LAB

The RHELS lab · a guided tour

Two planes. One GitOps spine.

A place to build, run, and protect your work, the way we do it here — everything is delivered from git.

lab — zsh

$ lab read --from-chapter-1

● tooling plane · Docker Desktop Kubernetes · workloads — live state in Argo CD

● workload cluster · OpenShift 4.22 (CRC) · apps — live state in Argo CD

● supply chain · partial · chapters 3–5 cover the journey

Start reading → Browse the contents ↓ Lab at a glance →

Table of contents

Five chapters

Each chapter hands off to the next — planes first, then what runs on them, then how code flows, then how we watch it, and finally how you add your own app.

  1. Tooling plane The workshop: everything that builds, signs, and delivers software.
  2. Workload cluster The factory floor: OpenShift, GitOps, and the apps that live there.
  3. CI/CD & supply chain From git push to running pod: how code ships today, and the signed future.
  4. Observability Metrics, logs, and traces — the watchtower is lit.
  5. Add an app The capstone: six steps from an idea to a Healthy workload.
Key terms The vocabulary the chapters assume — BSN, IaC repo, GitOps, and the supply-chain terms. Appendix — The lab at a glance The reference tables, in the back where they belong: status cards, the applications table, the full service directory, and how the front door works.

About this site

This showcase is built from a private source repository and published as a sanitized static bundle: inventory is snapshotted at build time, addresses and credentials are stripped by construction, and the agent-facing docs live in a private repo (see the footer link).

How this lab is run: every change starts as one GitHub issue holding the plan, the peer review, the human authorization, and the evidence. Agents draft and review; the human authorizes; nothing mutates without that loop. That is also how this book stays honest — each claim traces back to an issue or a repo, and snapshots are labeled with the date they were taken.