kubernetes
KEP-3370: add native PodGroup api
Signed-off-by: Alex Wang [email protected]
- One-line PR description: Add Native PodGroup api
- Issue link: https://github.com/kubernetes/enhancements/issues/3370
- Other comments:
Can you add sig-autoscaling as a participating sig and have an approver from it? In the high level, we should have an implementation path that is compatible with the cluster autoscaler.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: denkensk
To complete the pull request process, please assign ahg-g, wojtek-t after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahg-g @wojtek-t in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Any plans of an updated proposal? I was thinking that the new PreEnqueue endpoint might help have a more reliable implementation than the current QueueSort approach. But we also need more clarity around compatibility with cluster-autoscaler.
Key points from today's SIG meeting:
This KEP needs more work, specifically:
- Clarify how PodGroup could be supported by cluster-autoscaler.
- Evaluate using the PreEnqueue endpoint for better sorting and overall performance.
Key points from today's SIG meeting:
This KEP needs more work, specifically:
Clarify how PodGroup could be supported by cluster-autoscaler.
Thanks. @alculquicondor Ok. I will continue to work on this part. It's worth to rethink how to integrate with cluster-autoscaler again.
Evaluate using the PreEnqueue endpoint for better sorting and overall performance.
Yes. One of the original goals of PreEnqueue was also to optimize the performance of coscheduling.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: denkensk Once this PR has been reviewed and has the lgtm label, please ask for approval from wojtek-t and additionally assign ahg-g for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
hey @denkensk is there any reason you stopped working on this? We would find this highly useful for one of our needs.
hey @denkensk is there any reason you stopped working on this? We would find this highly useful for one of our needs.
+1 for having this. Would like to know the status of this KEP.
hey @denkensk is there any reason you stopped working on this? We would find this highly useful for one of our needs.
+1 for having this. Would like to know the status of this KEP.
I guess that we need to move the cluster-autoscaler ProvisioningRequest forward more and more before we work on this.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale