After Submariner is deployed and verified, complete the CCLM setup:

1. RWX Storage:
Create an Azure Files NFS StorageClass on both managed clusters. Azure's default disk storage (managed-csi) is RWO only – live migration requires RWX.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: azurefile-csi-nfs
provisioner: file.csi.azure.com
parameters:
  protocol: nfs
reclaimPolicy: Delete
volumeBindingMode: Immediate
mountOptions:
  - nconnect=4

2. CCLM Feature Enablement:
Run the existing setup_virt-cclm_env.sh script (ACM-27325) which handles:

• CNV decentralizedLiveMigration feature gate on HyperConverged CR
• MTV feature_ocp_live_migration flag on ForkliftController
• CCLM UI toggle (kubevirtCrossClusterMigration) on console-mce-config
• virt-synchronization-controller Kubernetes Service

Any remaining manual steps not covered by the script should be documented.

3. E2E Verification:

• Create a test VM on managed1 with RWX storage and Broadwell CPU model
• Initiate cross-cluster live migration to managed2 via Fleet Virt UI
• Confirm VM migrates with sub-second downtime
• Verify VM is accessible on managed2 post-migration

4. Jenkins Pipeline:
Create a Jenkinsfile automating the full flow end-to-end:

1. Deploy clusters (openshift-install with custom CIDRs + D8s_v3 workers)
2. Azure networking (subctl cloud prepare azure)
3. Submariner deployment (subctl deploy-broker + subctl join)
4. RWX storage setup
5. CCLM feature enablement
6. Verification

References:

• CCLM Network Guide
• Submariner Azure Quickstart