QoS-class resources

[marquiz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add QoS-class resources to Kubernetes
• Kubernetes Enhancement Proposal: KEP-3008: QoS-class resources #3004
• Discussion Link: https://groups.google.com/g/kubernetes-sig-node/c/UoxYzZ7gCbg
• Primary contact (assignee): @marquiz
• Responsible SIGs: SIG-Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32?
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3008: QoS-class resources #3004
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[kikisdeliveryservice]

Thanks for opening this @marquiz !! 😄

To ensure that the sig is aware of and that communication has begun regarding this KEP, please add the mandatory Discussion Link to the Description above. For ref it is a "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation"

[kad]

@kikisdeliveryservice the topic was discussed on SIG-Node on 2021-10-19.
Meeting minutes: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg

[pacoxu]

/sig node

[k8s-triage-robot]

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

[marquiz]

/remove-lifecycle stale

[Priyankasaggu11929]

/milestone v1.25

[Atharva-Shinde]

Hello @marquiz 👋, 1.25 Enhancements team here!

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.
For note, This enhancement is targeting for stage alpha for 1.25 release

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 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.

It looks like for this one, we would need to:

• The KEP needs updating most of the content of the KEP pull request as stated in the latest KEP
• Update the content of the Test Plan Section updated detailed test plan to incorporate more details.
• Fill up the Graduation section in the KEP with proper metadata
• Adding a dedicated Design Details section in the KEP and move the Test plan and Graduation sub-sections under this section.
• Create a kep.yaml file reflecting the latest milestone and stage information. Here is an example for reference.
• Create production readiness review file stating the KEP-issue number, the stage you are planning for this release cycle(in this case alpha) and the approver. Here is an example for reference.

Open PR #3004 addressing ^

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!

[Atharva-Shinde]

/stage alpha

[Atharva-Shinde]

Hello @marquiz 👋, just a quick check-in again.

The enhancements freeze for 1.25 starts on this Thursday, June 16, 2022 at 18:00 PM PT.

Please try to get the above mentioned action-items done before enhancements freeze :)

Note: the current status of the enhancement is still marked at-risk.

[marquiz]

Thanks @Atharva-Shinde for the help!

I now did the following updates:

• synced with the latest KEP template
• added graduation criteria
• updated test plan
• add kep.yaml
• add (placeholder) production readiness review file

We'll review this in SIG-Node tomorrow so more updates after that.

[Atharva-Shinde]

Hey @marquiz 👋
A good news! Enhancements Freeze is now extended to next week till Thursday June 23, 2022 🚀
So we now have one more week to submit the KEP :)

[Priyankasaggu11929]

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

Please plan to get the open PR #3004 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!

[Priyankasaggu11929]

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

[marquiz]

Hi @Atharva-Shinde @Priyankasaggu11929 I've retitled the PR (#3004) in order to reduce confusion misconceptions wrt some other KEPs and earlier work. Is it ok to retitle this issue as well?

[Priyankasaggu11929]

Hello @marquiz, retitling the issue is perfectly fine. Thank you! :)

[marquiz]

/retitle QoS-class resources

[SergeyKanzhelev]

/milestone v1.29

[npolshakova]

Hello @marquiz 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, it looks like #3004 will address most of these issues. Please update the latest-milestone to v1.29 and the alpha milestone to 1.29 in this PR.

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

[npolshakova]

Hi @marquiz, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze.

It looks like #3004 will address most of the requirements. Let me know if I missed anything. Thanks!

[npolshakova]

Hello 👋, 1.29 Enhancements Lead here.
Unfortunately, this enhancement did not meet requirements for v1.29 enhancements freeze.
Feel free to file an exception to add this back to the release tracking process. Thanks!

/milestone clear

[salehsedghpour]

/remove-label lead-opted-in

[SergeyKanzhelev]

/stage alpha
/milestone v1.30

[salehsedghpour]

Hello @marquiz , 1.30 Enhancements team here! Is this enhancement targeting 1.30? If it is, can you follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

[salehsedghpour]

/milestone clear

[k8s-triage-robot]

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

[kad]

/remove-lifecycle stale

[k8s-triage-robot]

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

[kundan2707]

/remove-lifecycle stale

[kundan2707]

/assign

[kundan2707]

/triage accepted