Quotas for Ephemeral Storage

[RobertKrawitz]

Enhancement Description

• Use filesystem quotas to monitor local ephemeral storage utilization
• Kubernetes Enhancement Proposal: 1029-ephemeral-storage-quotas
• Primary contact (assignee): @RobertKrawitz @pacoxu
• Responsible SIGs: SIG-Node
• Reviewer(s) - @dashpole @derekwaynecarr
• Approver: #derekwaynecarr @dchen1107
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.15
  • Beta release target (x.y): 1.31 (User Namespace https://github.com/kubernetes/enhancements/issues/127 is beta in v1.30)
    • promoted in v1.25.0 and then reverted in v1.25.1
  • Stable release target (x.y): TBD
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/646/
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/66928
  • [x] Docs (k/website) update(s): https://github.com/kubernetes/website/pull/14268
• [x] Reverted Beta (first-try: promoted in v1.25.0 and then reverted in v1.25.1)
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/2697
  • [x] Code (k/k) update PR(s):
    • [x] https://github.com/kubernetes/kubernetes/pull/107329
    • [x] https://github.com/kubernetes/kubernetes/pull/107201
    • [x] https://github.com/kubernetes/kubernetes/pull/107302
    • [x] https://github.com/kubernetes/kubernetes/pull/107490
  • [x] Docs(k/website) updates: https://github.com/kubernetes/website/pull/36401
  • [x] Revert PR: https://github.com/kubernetes/kubernetes/pull/112076, https://github.com/kubernetes/kubernetes/pull/112106, https://github.com/kubernetes/enhancements/pull/3485
• [ ] Beta (second-try) 1.31
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3821
    • [x] https://github.com/kubernetes/enhancements/pull/4699
  • [ ] Code (k/k) update PR(s):
    • https://github.com/kubernetes/test-infra/issues/28614
    • [x] 1.27 https://github.com/kubernetes/kubernetes/pull/112624
    • [x] 1.27 https://github.com/kubernetes/kubernetes/pull/115314
    • [ ] ~~https://github.com/kubernetes/kubernetes/pull/112626~~
    • [ ] ~~https://github.com/kubernetes/kubernetes/pull/112626#issuecomment-1864986501 kernel @haircommander pointed out that it's in a user namespace it can't change the projid and if not, project ID could be changed. So we want to wait for User Namespace beta before promoting this to beta.~~
    • [ ] update to use this when User Namespace is enabled
  • [ ] Docs (k/website) update(s):
    • [ ] https://github.com/kubernetes/website/pull/43455
    • [ ] https://github.com/kubernetes/website/pull/46967

[RobertKrawitz]

/sig node

[derekwaynecarr]

per sig-node discussion, this is good.

the kep will merge here: https://github.com/kubernetes/enhancements/pull/646

/milestone v1.15

[kacole2]

@RobertKrawitz This is OK to track for 1.15. However, please update the KEP with established graduation criteria for Beta and Alpha when possible.

/stage alpha

[makoscafee]

Hey, @RobertKrawitz @derekwaynecarr 👋 I'm the v1.15 docs Lead. Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

[RobertKrawitz]

Yes, this will require new documentation.

I will open the website PR today.

[kacole2]

Hi @RobertKrawitz @derekwaynecarr . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

[makoscafee]

Hey, @RobertKrawitz @derekwaynecarr .Just a friendly reminder we're looking for at least a draft/placeholder PR against k/website (branch dev-1.15) due by Thursday, May 30th 2019 @ EOD PST.

[RobertKrawitz]

@makoscafee The k/website PR is https://github.com/kubernetes/website/pull/14268

[kacole2]

Hi @RobertKrawitz @derekwaynecarr , today is code freeze. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[RobertKrawitz]

The PR for this is https://github.com/kubernetes/kubernetes/pull/66928

[RobertKrawitz]

/hold cancel

[kacole2]

Hi @RobertKrawitz , I'm the 1.16 Enhancement Lead. 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.6 Tracking Spreadsheet. If not's 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.

[kcmartin]

Hello @RobertKrawitz -- 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?

 Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

The current release schedule is

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

[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

[palnabarun]

/remove-lifecycle stale

[palnabarun]

Hey there @RobertKrawitz -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18 or having a major change in its current level?

The current release schedule is:

• Monday, January 6th - Release Cycle Begins
• Tuesday, January 28th EOD PST - Enhancements Freeze
• Thursday, March 5th, EOD PST - Code Freeze
• Monday, March 16th - Docs must be completed and reviewed
• Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release,

1. The KEP PR must be merged
2. The KEP must be in an implementable state
3. The KEP must have test plans and graduation criteria.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

[palnabarun]

@RobertKrawitz Just a friendly reminder, we are just 7 days away from the Enhancement Freeze (Tuesday, January 28th).

[palnabarun]

@RobertKrawitz Just a friendly reminder, we are just 2 days away from the Enhancement Freeze (3 PM Pacific Time, Tuesday, January 28th).

[palnabarun]

Unfortunately, the deadline for the 1.18 Enhancement freeze has passed. For now, this is being removed from the milestone. If there is a need to get this in, please file an enhancement exception.

[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

[palnabarun]

/remove-lifecycle stale

[harshanarayana]

Hey there @RobertKrawitz , 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[RobertKrawitz]

On 4/29/20 10:57 AM, Harsha Narayana wrote:

Hey there @RobertKrawitz , 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Hi Harsha,

I don't expect that this is going to graduate.

[harshanarayana]

Hi @RobertKrawitz, thanks for following up with an update on this. I have updated the tracking sheets accordingly. 👍

[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

[frittentheke]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @RobertKrawitz

Enhancements Lead here. Any plans for this in 1.20?

Thanks! Kirsten

[kikisdeliveryservice]

Hi @RobertKrawitz

Enhancements Lead here again. Enhancements Freeze is next week Tuesday October 6th.

Any plans for this in 1.20?

Also, this KEP is using the older format that is missing the Production Readiness Review Questionnaire, etc... so if you could please update that would be awesome (see for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template)

Thanks! Kirsten

[sjenning]

No plans for 1.20

[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