OpenShift-only tracker

BRAC POC OpenShift operating wiki

This wiki tracks the OCP side of the BRAC POC: cluster roles, current platform state, GitOps ownership, DR gates, service mesh readiness, and the planned Java/JBoss application path. The RKE2/shared-infra catalogue is tracked separately.

Fleet snapshot

Current operating view

Clusters4Two hubs, two spokes
OCP version4.20.18Recorded fleet baseline
Platform repolab-gitops-fullDesired state source
Workload repolab-workloadsApp source boundary

The management DC side is active through hub-dc. The restore hub hub-dr is passive. spoke-dc is the active workload cluster, while spoke-dr is platform-ready standby. The immediate operational queue is DR drill readiness, Kafka DNS readiness for future app consumption, and OSSM 3 workload onboarding.

Pages

Detailed sections

TopologyCluster roles, management model, and current DR semantics. GitOps modelRepository boundaries, Argo CD flow, and validation rules. hub-dcActive hub state, ACM backup, storage-light posture, and risks. hub-drPassive restore hub readiness, blockers, and activation constraints. spoke-dcActive workload cluster details and app onboarding status. spoke-drStandby workload cluster details and RHOAI platform state. Platform servicesStorage, identity, AI, demo app cleanup, OADP, and observability. Backup and DROADP status, ACM backup gates, restore hub gates, and validation commands. Service meshOSSM 3 live state and workload onboarding checklist. Apps and KafkaJava/JBoss app architecture and RKE2 Kafka dependency readiness. RoadmapImmediate gates, later work, and done criteria. Operating rulesSecret handling, live-change discipline, and session memory rules.

Current risk posture

Items to watch