Customer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group
SRE should be able to log into a cluster via a breakglass session
SRE should be able to retrieve serial console logs for a VM
Customer should be able to test admin credentials before cluster ready, then full admin credential lifecycle
Customer should be able to create node pools with ARM64-based VMs
Authorized CIDRs Connectivity should allow API access only from authorized VM IP
Customer should be able to create an HCP cluster with custom autoscaling and update the autoscaling configuration
Customer should be able to create a HCP cluster and use cilium CNI plugin
Customer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully
Customer should be able to create an HCP cluster and custom node pool osDisk size
Customer should create a cluster with private ingress using v20260630preview and verify the ingress is internal
Customer should create a cluster with private KAS and verify API server is only reachable from VNet while ingress remains public
Create HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API
Customer should create a cluster using v20260901preview API and verify cluster health
ARO HCP Service should successfully provision cluster when MI role assignments are added after cluster creation
FIPS Mode Support with v2026-06-30 API should create an HCP cluster with FIPS mode enabled via cryptoRestrictions property
Customer should be able to create an HCP cluster and manage pull secrets
Update HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request
Customer should be able to create an HCP cluster with back-level version 4.19
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.20
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.21
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.22
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.23
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.0
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.1
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.2
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.3
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.4
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.5
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.6
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.7
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.8
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.9
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.10
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.11
ARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.12
Service Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.19
Service Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.20
Service Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.21
Service Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.22
Service Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.23
Customer should be able to successfully upgrade control plane minor version from 4.20 minor to 4.21 minor
Customer should be able to successfully upgrade control plane minor version from 4.21 minor to 4.22 minor
Customer should be able to successfully upgrade control plane minor version from 4.22 minor to 4.23 minor
Customer should be able to successfully upgrade control plane minor version from 4.22 minor to 5.0 minor
Customer should be able to successfully upgrade control plane minor version from 5.0 minor to 5.1 minor
Customer should be able to successfully upgrade control plane minor version from 5.1 minor to 5.2 minor
Customer should be able to successfully upgrade control plane minor version from 5.2 minor to 5.3 minor
Customer should be able to successfully upgrade control plane minor version from 5.3 minor to 5.4 minor
Customer should be able to successfully upgrade control plane minor version from 5.4 minor to 5.5 minor
Customer should be able to successfully upgrade control plane minor version from 5.5 minor to 5.6 minor
Customer should be able to successfully upgrade control plane minor version from 5.6 minor to 5.7 minor
Customer should be able to successfully upgrade control plane minor version from 5.7 minor to 5.8 minor
Customer should be able to successfully upgrade control plane minor version from 5.8 minor to 5.9 minor
Customer should be able to successfully upgrade control plane minor version from 5.9 minor to 5.10 minor
Customer should be able to successfully upgrade control plane minor version from 5.10 minor to 5.11 minor
Customer should be able to successfully upgrade control plane minor version from 5.11 minor to 5.12 minor
Customer should be able to create a cluster with an external auth config and get the external auth config
Customer should be able to lifecycle and confirm external auth on a cluster
Customer should be able to create an HCP cluster and manage ImageDigestMirrors
Customer should be able to create an HCP cluster with Image Registry not present
Customer should be able to rotate KMS key for a cluster with version >= 4.22
Engineering should be able to retrieve kusto logs for a cluster and services
Customer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits
Nodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled
Customer should be able to update node pool labels and taints
Customer should be able to update nodepool replicas and autoscaling
Customer should upgrade and update a nodepool from 4.20.z to 4.21.zLatest
Customer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest
Customer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest
Customer should upgrade a nodepool to a version without Cincinnati upgrade edge z-stream upgrade without Cincinnati edge in 4.20
Customer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest
Customer should downgrade a nodepool version z-stream downgrade from 4.21.zLatest to 4.21.zPrevious
Customer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest
Customer should be able to use workload identity via the cluster OIDC issuer URL
Customer should be able to list available HCP OpenShift versions and validate response content
Engineering should be able to retrieve expected metrics from the /metrics endpoint
Fleet should have registered stamps with ready management clusters
