User Story

As an HCM ARO HCP Service owner, I want all HO/CPO compatibility tests from CNTRLPLANE-1848 to run on Azure platform, so that I can ensure version compatibility for ARO customers and detect AKS-specific issues.

Acceptance Criteria

• All baseline jobs from Story CNTRLPLANE-1851 run on Azure
• All upgrade jobs from Stories CNTRLPLANE-1852, CNTRLPLANE-1853 run on AKS
• AKS jobs use AKS-specific configurations (managed identities, workload identities)
• Azure jobs run on same cadence as AWS jobs
• Test results tracked separately by platform
• Azure-specific failures trigger appropriate alerts
• Jobs use proper Azure credentials and resource cleanup
• All jobs use the same TestUpgradeControlPlane test, just with Azure platform configuration

Technical Details

Job Naming Convention

Mirror AWS job structure with -azure suffix:

• AWS: periodic-ci-openshift-hypershift-release-4.Y-periodics-hcm-e2e-aws-ovn
• Azure: periodic-ci-openshift-hypershift-release-4.Y-periodics-hcm-e2e-aks

Platform-Specific Configurations

Azure Test Parameters:

• Cluster profile: hypershift-azure-aro-hcp or cluster-secrets-azure
• Platform type: Set via --e2e.platform=Azure
• Environment variables:
• AZURE_AUTH_TYPE: "workload-identity" or "managed-identity"
• AZURE_LOCATION: "eastus" (or appropriate region)
• Volume mounts:
• /usr/local/e2e-azure-cluster-profile
• Target: e2e-azure instead of e2e-aws-ovn

CI Operator Config

• Path: ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.Y__periodics-hcm-azure.yaml
• Or extend existing configs with Azure variants
• Define Azure-specific test workflows

Periodic Jobs to Create

Create Azure equivalents for all AWS jobs from Epic 1:

Baseline Testing:

• periodic-ci-openshift-hypershift-release-4.Y-periodics-hcm-e2e-azure

Upgrade Testing (.0 → latest):

• periodic-ci-openshift-hypershift-release-4.Y-periodics-hcm-upgrade-dot-zero-to-latest-azure

Upgrade Testing (latest-1 → latest):

• periodic-ci-openshift-hypershift-release-4.Y-periodics-hcm-upgrade-latest-1-to-latest-azure

AKS-Specific Validation

TestUpgradeControlPlane already works across platforms. AKS-specific validation happens automatically via the test framework.

Platform Comparison

Running parallel tests on AWS and AKS enables:

• Detection of platform-specific issues
• Validation that HO/CPO compatibility is platform-agnostic
• Identification of AKS-specific regressions
• Confidence for ARO HCP customers

Resource Management

Azure Quotas:

• Ensure sufficient quota for parallel test execution
• Monitor Azure subscription limits
• Implement proper resource cleanup to avoid quota exhaustion

Cost Management:

• Azure tests may have different costs than AWS
• Monitor and optimize resource usage
• Consider running some Azure tests less frequently if needed
• Baseline and upgrades: Same cadence as AWS
• Cross-minor: Could run bi-weekly instead of weekly if cost is concern

Initial Azure Versions to Test

Same as AWS from CNTRLPLANE-1848:

• Baseline: 4.20.z, 4.21.z, 4.22.z (latest Z)
• Upgrades (.0 → latest): All minor versions
• Upgrades (latest-1 → latest): All minor versions

Coordination Required

• Align with ARO HCP team on test priorities and cadence
• Set up appropriate notification channels for Azure-specific failures

Success Metrics

• All AKS jobs run successfully on schedule
• AKS test results tracked separately from AWS
• <10% false failure rate
• AKS-specific issues detected and reported