-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
Quality / Stability / Reliability
-
5
-
False
-
-
False
-
Not Selected
-
-
-
Denalli #2026/3
-
0
Objective
Validate STS credentials flow on ARO clusters using Managed Identities, and ensure no regressions in existing credential flows (CCO and Manual) on ARO/Azure standard clusters.
1. Feature Testing: ARO Cluster with Managed Identities – STS Credentials Flow
Prerequisites:
Follow the Workload Identity Documentation and validate these test cases are working as expected:
- PodVM image Creation
- peer pod can reach running state
- peerpod-ctrl able to clean dangling VM
- podVM image deletion
2. Regression Testing: ARO / Azure Standard Cluster – CCO Credentials Flow
Prerequisites:
- ARO / Azure Standard Cluster
Follow the normal peer-pods documentation without setting a peer-pods-secret and validate these test cases are working as expected:
- PodVM image Creation
- peer pod can reach running state
- peerpod-ctrl able to clean dangling VM
- podVM image deletion
3. Regression Testing: ARO / Azure Standard Cluster – Manual Credentials Flow
Prerequisites:
- ARO / Azure Standard Cluster
- Azure Credentials with Contributer role
Follow the normal peer-pods documentation and set manually the peer-pods-secret and validate these test cases are working as expected:
- PodVM image Creation
- peer pod can reach running state
- peerpod-ctrl able to clean dangling VM
- podVM image deletion