Quota by Priority

[justaugustus]

Feature Description

• One-line feature description (can be used as a release note):
• Primary contact (assignee): @bsalamat
• Responsible SIGs: @kubernetes/sig-scheduling-feature-requests, @kubernetes/sig-node-feature-requests
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @davidopp, @derekwaynecarr, @erictune, @k82cn, @timothysc, @wojtek-t @dchen1107
• Approver (likely from SIG/area to which feature belongs): @davidopp
• Feature target (which target equals to which milestone):
  • Alpha release target: ???
  • Beta release target: 1.12
  • Stable release target: ???

rel: #268
/sig scheduling node
/kind feature
/stage beta
/milestone v1.12
/assign @bsalamat

[justaugustus]

@bsalamat @kubernetes/sig-scheduling-feature-requests @kubernetes/sig-node-feature-requests --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[bsalamat]

This feature is implemented and docs are also written.

cc/ @vikaschoudhary16

[bsalamat]

And the doc is updated for 1.12.

[bsalamat]

The doc change that I sent above is actually for 1.11. I am going to send a PR to update the version tag in the doc.

[justaugustus]

@bsalamat please also link it here, so we can track.

[bsalamat]

@justaugustus Done

[ameukam]

Hi folks,
Kubernetes 1.13 is going to be a 'stable' release since the cycle is only 10 weeks. We encourage no big alpha features and only consider adding this feature if you have a high level of confidence it will make code slush by 11/09. Are there plans for this enhancement to graduate to alpha/beta/stable within the 1.13 release cycle? If not, can you please remove it from the 1.12 milestone or add it to 1.13?

We are also now encouraging that every new enhancement aligns with a KEP. If a KEP has been created, please link to it in the original post. Please take the opportunity to develop a KEP.

[yastij]

@ameukam - this is already in beta, @bsalamat do we plan to move this to GA in 1.13 ?

[bsalamat]

No, we don't. We should probably target 1.14 for GA of pod priority and quota by priority if things go well.

[kacole2]

thanks for the update!
/milestone clear

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[bsalamat]

/remove-lifecycle stale

[claurence]

@bsalamat - Hello, enhancements lead here - checking to see if there is any work being planned for the 1.14 release? Enhancements freeze is 1/29 and we want all enhancements to have a KEP. Thanks

[bsalamat]

@claurence This is not a new enhancement. It is already implemented and is in Beta.

[claurence]

ok so then no plans to move to stable in 1.14? Thanks.

[kacole2]

I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[rbitia]

Hi @bsalamat , I'm the 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If it's not graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.