Platform
Platform services and cleanup state
This page summarizes the platform services that matter for OCP operations and separates active platform capabilities from retired or source-only app material.
Summary
Service matrix
| Area | Current state | Notes |
|---|---|---|
| Storage | Hubs are storage-light with LVMS. Spokes retain ODF. | Hub ODF/NooBaa and related stacks were removed; RHACS PVCs remain bound on LVMS. |
| Identity | WSO2 IS removed. Google and htpasswd remain by cluster role. | spoke-dc is Google-only; other clusters retain htpasswd plus Google where recorded. |
| AI | No user AI workloads found. | spoke-dr has RHOAI operator only; hub-dc has stale-looking RHOAI artifacts. |
| User workload metrics | Enabled only on spokes. | hub-dc and hub-dr are explicitly disabled; spoke-dc and spoke-dr run the user workload monitoring stack. |
| Demo apps | No removable demo apps on spokes. | demo-orders was wiped from desired state. |
| Kafka on OCP | Retired from spoke desired state. | Future app Kafka usage should target RKE2 Kafka after DNS and app credentials are ready. |
| OADP | General daily backups complete in latest recorded run. | Monitor hub-dr archive persistence and cluster-to-MinIO path latency. |
Retired or absent
What should not reappear accidentally
- WSO2 IS OAuth integration and its client secret on
spoke-dc. demo-ordersnamespace, workload resources, KafkaUser, and orders topics.- AMQ Streams, Streams Console, Apicurio Registry, Strimzi CRDs, and
kafkanamespace on the OCP spokes. - Hub ODF/NooBaa, hub logging/tracing/observability test stacks, and hub MinIO/Loki/Tempo stacks removed by storage-light cleanup.
- User workload Prometheus and Thanos ruler pods on the management hubs.
Operational note
Source-only app bases
Some app bases may remain in source repositories as templates or retained examples. They are not live workloads unless a cluster overlay includes them. Current rendered spoke overlays do not deploy candidate demo apps.