Rendered folder index
Direct articles in this section
Folders and articles are both available in the left browser. This panel promotes actual notes first.
The platform will launch across two physical locations but will not operate in an active-active posture initially. We need a rollout strategy that keeps production stable, accelera
adr / acceptedADR-005 Datacenter Services baseline and external load balancing approachClusters as a Service needs a minimal, dependable baseline with limited dependencies. ADR-006 constrains the external load-balancing vendor; this ADR defines the full Datacenter Se
adr / acceptedADR-006 External load-balancing vendor constraintExternal load balancing is required for north-south traffic. Procurement constraints mandate the NetScaler vendor family, recorded in internal sourcing documentation.
adr / acceptedADR-010 ACM (Advanced Cluster Management) for 1H2026 Cluster DeploymentThe long-term design assumes Advanced Cluster Management (ACM) for cluster lifecycle management, but initial hardware constraints may limit how many hubs and service clusters we ca
adr / acceptedADR-011 Restricted network vs disconnected OpenShift installationFor high-security environments, disconnected OpenShift deployments are an option but require extra preparation (registry mirroring, operator catalogs, and update processes). The 1H
adr / draftADR-012 SSO (Single Sign-On) for OpenShift and Hosted ServicesA federated authentication solution is required across clusters and hosted services to simplify smart access operations. The platform baseline already assumes keycloak; this ADR de
adr / acceptedADR-013 Phasing and Ordering of OpenShift ImplementationThe implementation needs a clear dependency order for MVP delivery. Storage, Advanced Cluster Management (ACM)/Red Hat Advanced Cluster Management, Automation, and hosted control p
adr / draftADR-015 Keycloak IAM (Identity and Access Management) Architecturekeycloak must provide resilient smart access across clusters. We need to choose a deployment model that meets availability, scale, and operational requirements while remaining mana
adr / draftADR-017 Service Mesh: ambient-first target default (production exception request)The platform aims to offer a multi-cluster service mesh capability on top of OpenShift Service Mesh 3. The preferred architecture pattern is to host control planes on dedicated ser
adr / draftADR-022 Transitional production exception for OpenShift AI in DC-AThe program needs production-visible progress early, while the broader DC 3.0 target architecture is still being engineered and validated. A dedicated OpenShift AI cluster in DC-A
Platform ADRs capture runtime, identity, rollout strategy, and operational control decisions for the platform domain.
Start Here
Key Platform ADRs
- ADR-004 Single-active phased datacenter rollout (accepted)
- ADR-005 Datacenter Services baseline (accepted)
- ADR-006 External load-balancing vendor constraint (accepted)
- ADR-010 ACM for cluster deployment (accepted)
- ADR-011 Restricted network vs disconnected OCP (accepted)
- ADR-013 Implementation phasing (accepted)
- ADR-015 Keycloak IAM architecture (draft)
- ADR-017 Service mesh production exception (draft)
- ADR-022 OpenShift AI transitional production exception (draft)
Related Lenses
- TOGAF mapping: DC 3.0 Building Block Lens.
- Delivery planning: Delivery Work Packages.