Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Native PodGroup API #3370

Open
4 tasks
denkensk opened this issue Jun 9, 2022 · 43 comments
Open
4 tasks

Add Native PodGroup API #3370

denkensk opened this issue Jun 9, 2022 · 43 comments
Assignees
@denkensk
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. wg/batch Categorizes an issue or PR as relevant to WG Batch.

Comments

@denkensk
Copy link
Member

denkensk commented Jun 9, 2022 •
edited by pacoxu
Loading

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 9, 2022
@denkensk
Copy link
Member Author

denkensk commented Jun 9, 2022

/sig scheduling
/wg batch

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. wg/batch Categorizes an issue or PR as relevant to WG Batch. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 9, 2022
@denkensk denkensk mentioned this issue Jun 9, 2022
Open
@denkensk
Copy link
Member Author

denkensk commented Jun 9, 2022

/assign

@MaciekPytel
Copy link

/sig autoscaling

@k8s-ci-robot k8s-ci-robot added the sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. label Jun 9, 2022
@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 16, 2022
@Priyankasaggu11929
Copy link
Member

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jun 16, 2022
@parul5sahoo
Copy link

parul5sahoo commented Jun 16, 2022 •
edited by Priyankasaggu11929
Loading

Hello @denkensk and @MaciekPytel 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would need to update the above items before enhancements freeze.

Open PR #3371

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@Priyankasaggu11929
Copy link
Member

Hello @denkensk 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

The open KEP PR #3371 still misses updating the status from provisional to implementable in the kep.yaml file.

Please plan to update the PR with above & get it merged before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT, which is just over 3 days away from now.

For note, the current status of the enhancement is atat-risk. Thank you!

@parul5sahoo
Copy link

parul5sahoo commented Jun 23, 2022 •
edited
Loading

Hello @denkensk the 1.25 enhancements freeze is on Thursday, June 23, 2022 at 18:00 PM PT, which is tomorrow.
The PR above needs to be merged the changes mentioned in the previous comment, for the enhancement to be marked as tracked the current status of the enhancement is at-risk.

@Priyankasaggu11929
Copy link
Member

Hello, 1.25 Enhancements Lead here 👋. With Enhancements Freeze now in effect, this enhancement has not met the criteria for the freeze and has been removed from the milestone.

As a reminder, the criteria for enhancements freeze is:

  • KEP file using the latest template has been merged into the k/enhancements repo, with up to date latest milestone and stage
  • KEP status is marked as implementable
  • KEP has an updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks!
/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Jun 24, 2022
@Priyankasaggu11929 Priyankasaggu11929 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jun 24, 2022
@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 22, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 22, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2022
@alculquicondor
Copy link
Member

/reopen

@k8s-ci-robot
Copy link
Contributor

@alculquicondor: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 30, 2023
@kerthcet
Copy link
Member

/reopen

Back from the sig scheduling meeting, I'd like to complete the KEP about the unresolved part of autoscaler and PreEnqueue, I'll talk with @denkensk offline.

@tenzen-y
Copy link
Member

If @denkensk doesn't have enough bandwidth, I'll try to tackle this KEP.

@denkensk
Copy link
Member Author

I am still working on this. I have finished the PreEnqueue part. But It is difficult to think of a more ideal way to integrate with auto-scale. I will update the KEP recently.

@alculquicondor
Copy link
Member

If it helps, we can discuss some points about autoscaling in the WG Batch. @mwielgus (SIG Autoscaling chair) is a regular attendee

@Atharva-Shinde Atharva-Shinde removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 14, 2023
@AxeZhan
Copy link
Member

AxeZhan commented Sep 12, 2023

/cc
I'm very interested in this KEP. If anyone is going to work on this again, please let me know if I can be part of this :)

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 28, 2024
@kerthcet
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 31, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2024
@tenzen-y
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2024
@AxeZhan
Copy link
Member

AxeZhan commented Apr 30, 2024

Do we have a plan to push this forward?

@tenzen-y
Copy link
Member

Do we have a plan to push this forward?

I think that we still need to evolve ProbvisioningRequest.

@AxeZhan
Copy link
Member

AxeZhan commented May 3, 2024

I think that we still need to evolve ProbvisioningRequest.

Sorry to bother again. @tenzen-y
I came back after reading https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/proposals/provisioning-request.md. But I'm not familiar with cluster-autoscaler. I checked the code of CA and found related codes in the repo. So I'm not very clear what more work of ProbvisioningRequest need to be done. I tried to find a tracking issue in CA but still can't find a result. Can you explain this more clearly or post a related issue/pr ? Thanks in advance :)

@alculquicondor
Copy link
Member

@yaroslava-serdiuk could you post links to the issues where the progress is tracked?

@alculquicondor
Copy link
Member

alculquicondor commented May 3, 2024 •
edited
Loading

@AxeZhan there was also a completely different approach proposed yesterday at SIG Scheduling meeting https://www.youtube.com/watch?v=KoLnC24fQVc (https://docs.google.com/document/d/1IQreuruUEaG6wJEAxqiIpDfcEDAVkYTq5wTZS4sL8nc/edit?usp=sharing), although it tries to cover more than just scheduling.

@AxeZhan
Copy link
Member

AxeZhan commented May 3, 2024

@AxeZhan there was also a completely different approach proposed yesterday at SIG Scheduling meeting https://www.youtube.com/watch?v=KoLnC24fQVc, although it tries to cover more than just scheduling.

Yes, I watched the recording today :) But I think that proposal lacks lots of implementation details. This one seems more promising? As co-shceduling plugin is already used in many places, and seems the only thing blocking us is integrating with CA.

@alculquicondor
Copy link
Member

the only thing blocking us is integrating with CA.

TBH, that "only thing" is not simple either.

But I think that proposal lacks lots of implementation details.

I agree, but there are some pain points that are worth paying attention to.

In any case, I'm interested in seeing a renewed proposal of the co-scheduling plugin to come upstream.

@yaroslava-serdiuk
Copy link

Yaroslava Serdiuk could you post links to the issues where the progress is tracked?

My bad, it doesn't have an issue with tracked progress. I'll create one when I'm back from holidays.

@yaroslava-serdiuk
Copy link

@kerthcet kerthcet mentioned this issue May 30, 2024
Open
4 tasks
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2024
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@denkensk denkensk

Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. wg/batch Categorizes an issue or PR as relevant to WG Batch.
Projects
SIG Scheduling
Status: Needs Triage
Milestone
No milestone
Development

No branches or pull requests