What is the problem you're trying to solve
The current E2E test cases set the replicas of Volcano components (e.g., volcano-scheduler, volcano-controller, volcano-admission) to 1. Such a configuration cannot cover concurrent running scenarios of multiple component instances, so it fails to expose potential race condition problems (e.g., #5074) that may occur in production environments with high availability (HA) deployments.
Describe the solution you'd like
- Modify E2E test configurations to set replicas: 2 (or higher) for core Volcano components
- Add E2E tests to specifically verify the status of the components and the related resources, ensuring the correctness and stability under multi-instance concurrent running settings
Additional context
No response
Documentation Updates
What is the problem you're trying to solve
The current E2E test cases set the replicas of Volcano components (e.g., volcano-scheduler, volcano-controller, volcano-admission) to 1. Such a configuration cannot cover concurrent running scenarios of multiple component instances, so it fails to expose potential race condition problems (e.g., #5074) that may occur in production environments with high availability (HA) deployments.
Describe the solution you'd like
Additional context
No response
Documentation Updates