Active hub

hub-dc

hub-dc is the active management cluster for the lab fleet. It owns ACM/MCE management, platform GitOps, hub backup scheduling, and current managed-cluster placement decisions.

Status

Recorded current state

Role
Active management hub.
OpenShift
Recorded baseline is 4.20.18.
GitOps
Root and hub-dc-cluster-config recorded Synced/Healthy after the latest remediation sequence.
ACM backup
acm-dpa reconciled, acm-dpa-1 available, hub-backup-daily enabled.
Managed clusters
hub-dr is no longer a managed cluster on hub-dc. Current managed pull placement selects spokes only.
User workload metrics
Disabled by cluster-monitoring-config; no user workload monitoring pods should run on this hub.

Storage

Storage-light hub posture

Hub storage was intentionally reduced. LVMS and RHACS remain. ODF/NooBaa, Pipelines/Tekton Results, logging, tracing, MinIO/Loki/Tempo, OpenTelemetry, Cluster Observability, and Network Observability were removed from hub live state.

Risk

Operational watch items

Backup freshness

Daily ACM backups complete, but the latest recorded backup can still fail a strict two-hour drill RPO. Create a fresh backup immediately before an activation drill unless a looser RPO is accepted.

GitOps status artifacts

Hub-side managed-pull status for spoke-dr-cluster-config can remain confusing or stale. Prefer local spoke Argo status for managed-pull app truth.

Network history

A previous GitLab reachability issue was caused by stale conflicting IPs on the HAProxy VM. That was remediated and GitLab route reachability was validated.

Drill ownership

Do not begin restore activation from hub-dc to hub-dr without explicit approval because managed cluster ownership can move.

Validation

Useful read-only checks

export KUBECONFIG=<hub-dc-kubeconfig>
oc get clusterversion
oc -n open-cluster-management get mch
oc get mce
oc -n open-cluster-management-backup get dpa,bsl,backupschedule
oc -n openshift-gitops get applications.argoproj.io

Next: hub-dr