Goal

 
Enable E2E test runs for Fleet Virtualization on ACM (Advanced Cluster Management) topologies: a manager (hub) cluster with Fleet Virtualization and one or more managed clusters. Tests focus on Fleet Virtualization UI and workflows from the manager cluster; fleet management (importing or binding the managed cluster) is performed only in setup when needed, not as part of test scenarios. CI/build pipelines support dual-cluster authentication and kubeconfig so that setup can bind a to-be-managed cluster to the manager when required. Expected outcomes: a dedicated Fleet Virtualization / ACM test tier, multi-cluster orchestration in the framework, dual-cluster Allure reporting, and a clear ACM mode for setup and tests.

User Stories

• As a cluster administrator or test maintainer, I want the test framework to authenticate to both manager and managed clusters and use the manager cluster for all UI interactions, with a dedicated Fleet Virtualization / ACM tag/tier and an ACM mode flag or fixture, so that Fleet Virtualization workflows can be validated end-to-end, tests can be selected and run in CI (e.g. `--grep @acm`) with manager UI + optional managed cluster context, fleet management is handled in setup only, and the Allure report includes both manager and managed cluster (and console) URLs when running in ACM mode so report consumers can see which clusters were used.
• As a CI/CD maintainer, I want the Jenkins pipeline to support dual-cluster auth and to find/read kubeconfig for both manager and managed (or to-be-managed) clusters, so that Fleet Virtualization test jobs can run with the right credentials and, when the managed cluster is not yet bound, setup can use the to-be-managed kubeconfig to add it to the manager (tests do not perform fleet management).
• As a CI/CD maintainer, I want the test image Dockerfile to support dual-cluster auth and to find/read kubeconfig for both clusters (with the same fallback as Jenkins), so that containerized Fleet Virtualization test runs work in dual-cluster environments and setup can bind the cluster when needed.