Backup health
ACM and OADP backup health alerts now exist. Validate alert behavior before using them as a DR drill gate.
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 is
Synced/Healthy.hub-dc-cluster-configisSynced/Progressingwhile image pre-pull completes. - ACM backup
acm-dpareconciled,acm-dpa-1available,hub-backup-dailyenabled, with backup health alerts added.- Managed clusters
hub-dris no longer a managed cluster onhub-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. - ACM Observability
- Enabled and recorded
Ready=True. Grafana is part of the ACM Observability stack. PVC requests were increased, but still use lab-local LVMS. - Vault / ESO
SecretStore/rke2-vaultisReady=TrueandExternalSecret/eso-vault-smokeis synced through thekubernetes-hub-dcVault auth mount.
Storage
Storage-light hub posture
Hub storage was intentionally reduced. LVMS and RHACS remain. ODF/NooBaa, Pipelines/Tekton Results, app logging/tracing stacks, MinIO/Loki/Tempo, OpenTelemetry, and Network Observability were removed from hub live state. ACM Observability remains as a hub management service.
lvms-vg1is the remaining hub storage class.- RHACS Central PVCs remain bound on
lvms-vg1. - LVMS device discovery is pinned to
/dev/vdb,/dev/vdc, and/dev/vdd.
Risk
Operational watch items
Image pre-pull
The hub image pre-pull DaemonSet is warming selected recovery images. It is a bridge until durable mirroring is built.
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 GitOps source reachability issue was caused by stale conflicting edge IPs. That was remediated and 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 open-cluster-management-backup get servicemonitor,prometheusrule
oc -n openshift-image-prepull get ds,pods
oc -n openshift-gitops get applications.argoproj.io