Search

Showing top 116 results for "Integration constraints"

People also ask

When does the integration kick in?

To keep the first feature iteration predictable, the Job controller only creates a Workload and PodGroup when the Job has a well-defined, fixed shape: .spec.parallelism is greater than 1.spec.completionMode is set to Indexed.spec.completions is equal to .spec.parallelismThe schedulingGroup is not already set on the Pod template. These conditions describe the class of Jobs that gang scheduling can reason about: each Pod has a stable identity (Indexed), the gang size is known and fixed at admission time (parallelism == completions), and no other controller has already claimed scheduling responsi

Kubernetes v1.36: Advancing Workload-Aware Scheduling
2 sources covering this — show 1 more

Discussions and forums