-
Sub-task
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Quality / Stability / Reliability
-
5
-
False
-
-
False
-
-
-
-
ACM Console Train 37 - 1
Goal
Automate the full Azure CCLM environment deployment via a Jenkins pipeline. This codifies the manual process validated in ACM-30198, ACM-30199, and ACM-30200.
Pipeline Stages
| Stage | What it does |
|---|---|
| 1. Deploy OCP clusters | openshift-install IPI on Azure with non-overlapping CIDRs and D8s_v3 workers (hub + managed clusters) |
| 2. Install ACM | Apply acm-dev-catalog CatalogSource, install ACM operator, create MultiClusterHub |
| 3. Import spokes | Import managed clusters into ACM hub |
| 4. Submariner networking | subctl cloud prepare azure – NSGs, gateway MachineSets, public IPs per cluster |
| 5. Submariner deployment | subctl deploy-broker + subctl join per cluster, verify IPsec tunnels |
| 6. CCLM features | Run setup_virt-cclm_env.sh --all – MCH components, CNV, MTV, feature gates, console plugins |
| 7. E2E verification | Create test VM, trigger cross-cluster migration, verify success |
| 8. Cleanup | Tear down clusters on failure or on-demand |
Parameters
- OCP version
- ACM catalog image tag
- Azure region
- Worker instance type (default: Standard_D8s_v3)
- Number of managed clusters (1 or 2)
- CIDR plan
Prerequisites
Manual process fully validated (all closed):
ACM-30201– Azure permissionsACM-30198– Cluster deployment with custom CIDRsACM-30199– Submariner networkingACM-30200– CCLM features + e2e verification
Notes
- setup_virt-cclm_env.sh has 2 local bug fixes that need to be upstreamed or baked into pipeline (see
ACM-30200comment) - MSA token validity should be set to long duration to avoid expiry during runs
- OCP 4.21 requires --skip-version-check with subctl v0.22.0