[Feature] [Alpha] Scheduling Suspend and Resume

[RainbowMango]

Summary:

This feature allows third-party systems to temporarily pause the scheduling of applications across the cluster. When the scheduling of an application is suspended, it will not be scheduled until it is explicitly resumed. This provides fine-grained control over the lifecycle of applications, enabling users to manage resource allocation, prioritize critical workloads, or integrate with external systems that need to control when applications are deployed.

The feature can be configured through API calls, command-line tools, or a graphical user interface, offering flexibility for different use cases. (But we currently just focus on API calls in the alpha stage).

Why is this needed:

This feature is essential for scenarios where dynamic control over application scheduling is required. For example, during periods of resource contention, administrators may want to pause non-critical applications to ensure that critical workloads have priority access to cluster resources. Additionally, third-party systems can leverage this feature to build queues, allowing them to manage the order in which applications are scheduled based on external conditions or policies. This ensures that applications are only deployed when the necessary prerequisites are met, such as waiting for data to become available or for infrastructure to be ready. By providing a mechanism to suspend and resume scheduling, Karmada enhances operational flexibility, improves resource utilization, and supports more complex deployment workflows, making it easier to manage large-scale, multi-cluster environments.

Proposal

• [Proposal] Support for resource scheduling suspend and resume capabilities #5690

Author(s):

• @Vacant2333
• @Monokaix

Iteration Tasks

• Prerequisites: decouple suspension definition between PropgationPolicy and ResourceBinding. (@Monokaix, decouple suspension of propagation and resourcebinding #5974)
• API Change: introduce scheduling suspension to RB (@Monokaix, feat: cluster-level resource scheduling suspend and resume capabilities #5937)
• karmada-scheduler: Implement scheduling suspension (@Monokaix, feat: cluster-level resource scheduling suspend and resume capabilities #5937)
• karmada-webhook(Not sure if we need to introduce validating to discourage suspend scheduling after RB scheduled. [Proposal] Support for resource scheduling suspend and resume capabilities #5690 (comment))
• E2E Tests
• TBD