Diagram

Fleet topology and core dependencies

Current OCP management and workload placement, including only external dependencies that directly support OpenShift operations: secrets, backup/object storage, GitOps source, identity, and edge ingress.

DC and DR OpenShift topology with core external operational dependencies
DC runs the active management and workload side. DR remains restore-ready and platform standby. External systems are shown only where they support OpenShift core operations.

Source

Mermaid source

Use this source when copying the topology into tools that render Mermaid diagrams.

flowchart LR
  subgraph DC["DC site"]
    HDC["hub-dc<br/>active management hub"]
    SDC["spoke-dc<br/>active workload cluster"]
  end

  subgraph DR["DR site"]
    HDR["hub-dr<br/>passive restore hub"]
    SDR["spoke-dr<br/>workload standby"]
  end

  EXT["Core external dependencies<br/>Vault, MinIO, GitOps source, identity, edge ingress"]

  HDC -- "ACM manages active spoke" --> SDC
  HDC -. "ACM backup and activation path" .-> HDR
  SDC -. "standby placement decision" .-> SDR
  HDR -. "restore hub later manages DR" .-> SDR
  EXT -- "Vault ESO path" --> HDC
  EXT -- "Vault ESO path" --> HDR
  EXT -- "GitOps / backup / ingress path" --> SDC
  EXT -- "Vault ESO path" --> SDR

Back to diagrams