spoke-dr

GitOps

spoke-dr-cluster-config recorded Synced/Healthy.

Storage

ODF desired/live spec uses compact LVMS topology and StorageCluster is ready.

OADP

lab-dpa reconciled, BSL available, latest scheduled daily completed in the recorded run. A historical partially failed backup remains in history.

AMQ/Kafka

Retired from spoke desired state. No local AMQ/Kafka/Strimzi objects remain.

AI platform

RHOAI operator installed, but no DataScienceCluster or user AI workloads exist.

User workload metrics

Enabled; user workload Prometheus, Thanos ruler, and the Prometheus operator should run here.

• servicemeshoperator3.v3.3.2 and kiali-operator.v2.22.2 CSVs recorded Succeeded.
• Istio/default, IstioCNI/default, Kiali, OSSM Console, CNI pods, and ingress gateway are recorded running.
• Only istio-ingress is labeled for injection.
• RHOAI ServiceMesh capability is recorded False/MissingOperator because it expects the old OSSM v2 operator; this does not block OSSM 3 itself.

The main open design question is whether spoke-dr should remain platform standby or become app-ready hot standby. If app-ready standby is required, app placement, data dependencies, Kafka credentials, routes, mesh labels, and validation should be added to lab-workloads deliberately.