On this page
WP-08 Platform Services and Automation
Summary
Deliver repeatable provisioning, configuration, and day-2 operations for platform services using a GitOps-driven operating model.
Scope
- Cluster and add-on lifecycle automation.
- Baseline policy rollout and audit trail creation through fleet-management and red-hat-advanced-cluster-management.
- Day-2 change workflows with controlled exceptions.
Architecture Context
- Domain architecture: Platform Architecture
- Runtime context: Platform Architecture
- Supporting architecture note: intent-to-runtime-automation-flow
- TOGAF mapping: automation via openshift-gitops
- Hosted control plane posture: cluster-management via red-hat-advanced-cluster-management
Decision Context
Dependencies
- No hard package dependency is currently recorded.
- Delivery coordination is required with WP-09 Containers as a Service (CaaS) Platform and WP-18 Service Mesh.
Acceptance Criteria
- New tenant cluster provisioning path is fully automated and auditable, with standard profile provisioning in <= 60 minutes measured p95 from approved request timestamp to cluster-ready handover timestamp for successful standard-profile runs.
- Standard day-2 changes are executed through Git-based workflows with >= 95% change-path coverage over a rolling 30-day window; denominator is all eligible standard day-2 changes, excluding break-glass incidents and approved non-standard remediation.
- ACM onboarding and policy-baseline application are automatic for production-bound clusters.
- Break-glass path is documented, controlled, traceable, and time-bound.
- Rollout evidence for automation/governance controls is published in the release evidence bundle and approved before cutover.