Installation Manual - 127 spoke-dr-v7 ADR and compact hot standby design

The accepted architecture decision for spoke-dr-v7, including the compact VM-only hot standby model and the next gate.

This chapter records the architecture decision for spoke-dr-v7.

The design gate is now accepted. spoke-dr-v7 is approved as a compact three-node VM-only hot standby workload cluster for spoke-dc-v7.

Update: the parity baseline and workload inventory in #466 was completed on 2026-05-22T19:24:59Z. The allocation gate #467 completed at 2026-05-22T19:33:41Z, so the next active gate is #468.

Governance

Decision Summary

The accepted design keeps the same logical structure as spoke-dc-v7 while allowing a smaller physical footprint:

• compact three-node VM-only topology;
• same GitOps and operator model where it applies;
• CNPG/database-layer replication for the insurance workload;
• ODF or local storage for PVCs on the DR cluster;
• no default ODF block-level replication for the database PVCs;
• active/passive traffic control with split-brain prevention;
• distinct cluster identity and separate secret custody.

The active workload remains spoke-dc-v7 until a later controlled failover drill promotes spoke-dr-v7.

Non-Goals

• Do not create VMs, DNS records, HAProxy entries, install artifacts, GitOps overlays, ACM imports, or live OpenShift resources in this gate.
• Do not clone the active cluster identity or secret material.
• Do not route traffic to spoke-dr-v7 yet.

Validation

• Accepted ADR exists at adr/0030-spoke-dr-v7-hot-standby-workload-cluster.md.
• Issue #465 is the design gate for this decision.
• The design gate is closed.
• The parity baseline gate #466 is also closed.

Next Gate

#468 / OP-GF-SPOKEDRV7-4 will render install inputs and disconnected artifacts from the accepted allocation. VM creation remains gated by #469.