1Run a pipeline
The first two both build and deploy, so they can be tested against each other: run the baseline, pentest it, run the remediated build, pentest again. Same pipeline, same source, same gate settings — the only difference is whether dependencies come from upstream or from Red Hat.
Gates report rather than block on the deploying pair, so both reach build. Both promote into the same dev overlay, so whichever ran last is what dev serves — the GitOps section below names it. Remediated takes ~3 min warm, ~20 on a cold Nexus cache.
2Pipeline idle
no runs yet
3Gates this run
Which gate let this run through, and which stopped it. Counts come from task results, so they stay correct after the run ends.
4Remediation Lightwell · VEX
What this run took from Red Hat, and what it left alone.
6GitOps — what is running, and where it came from
Each environment traced back to the git revision Argo CD reconciled and the digest it is serving, with its ReplicaSets, because during a rollout that is where the truth is. Promotion sits between the two because that is literally what it does: move the digest dev proved into the prod overlay, by pull request.
