Closed asm582 closed 1 day ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I think a better approach is if the cloud provider gives some form of atomicity when doing scale ups.
What you are proposing sounds very problematic. How do you express that a job is ok to run in nodes provisioned for some other job? When/how to do preemption?
Do you have a more specific proposal?
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What would you like to be added: A mechanism to submit queued jobs/workloads on the newly added available nodes in the cluster while the scale up completes for the previous job via provisioningrequest.
Why is this needed: We block quota and later acquire resources in some what sequential fashion from cloud provider, not using newly added resources for queued jobs will lead to resource wastage and decrease in cluster throughput.
Completion requirements: New preemption policy may be needed to force terminate already existing running backfilled jobs on the newly acquired nodes.
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.