Enhancement Description

• One-line enhancement description (can be used as a release note): Allow users to recover from volume expansion failure
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR): https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1790-recover-resize-failure/README.md
• Primary contact (assignee): @gnufied
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.32
  • Stable release target (x.y): 1.34
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s):
    • https://github.com/kubernetes/enhancements/pull/1516
    • https://github.com/kubernetes/enhancements/pull/4102
  • [x] Code (k/k) update PR(s):
    • 1.23 https://github.com/kubernetes/kubernetes/pull/106154
    • 1.28 https://github.com/kubernetes/kubernetes/pull/116335
  • [x] Docs (k/website) update PR(s):
• [x] Beta
  • [x] KEP (k/enhancements) update PR(s):
    • 1.24 https://github.com/kubernetes/enhancements/pull/3188
    • 1.32 https://github.com/kubernetes/enhancements/pull/4849
  • [x] Code (k/k) update PR(s):
    • 1.32 https://github.com/kubernetes/kubernetes/pull/128342
  • [x] Docs (k/website) update PR(s):
    • 1.32 https://github.com/kubernetes/website/pull/48532
• [ ] Stable
  • [x] KEP (k/enhancements) update PR(s):
    • https://github.com/kubernetes/enhancements/pull/5353
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

/sig storage

/milestone v1.19

/stage alpha

@gnufied -- Can you please link to all the implementation PR's here - k/k or otherwise? :slightly_smiling_face:

---

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

Hello, @gnufied ! :wave: I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

This is a friendly reminder that we're looking for a PR against kubernetes/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

Regards, Mikael.

Can you please link to all the implementation PR's here - k/k or otherwise?

@gnufied -- Pinging back as a friendly reminder for the above. :slightly_smiling_face:

@palnabarun thanks for the reminder. there isn't one yet.

PR that implements necessary API changes and updates quota calculation code - https://github.com/kubernetes/kubernetes/pull/91976

Hi @gnufied! Friendly reminder regarding that docs placeholder PR against kubernetes/website (branch dev-1.19). The deadline for this have been pushed to Friday the 19th of June. Let me know if you have any questions!

Hi @gnufied -- just wanted to check in about the progress of the enhancement.

The release timeline has been revised recently, more details of which can be found here.

Please let me know if you have any questions. :slightly_smiling_face:

---

The revised release schedule is:

• Thursday, July 9th: Week 13 - Code Freeze
• Thursday, July 16th: Week 14 - Docs must be completed and reviewed
• Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released

Docs PR - https://github.com/kubernetes/website/pull/21920

Hi @gnufied :wave:, I see that https://github.com/kubernetes/kubernetes/pull/91976 and https://github.com/kubernetes/kubernetes/pull/92770 yet to be merged. Do you think that they will be merged before the Code Freeze on Thursday, July 9th?

Thank you. :slightly_smiling_face:

---

Code Freeze begins on Thursday, July 9th EOD PST

Hi @gnufied 👋 docs shadow here. Just a quick reminder to get your doc PR ready for review (Remove WIP/rebased/all ready to go) by EOD. Thank you!

@annajung done. thank you.

@gnufied -- Please note that tomorrow is Code Freeze.

If the enhancement misses the code freeze, you will need to file an Exception Request in order to get this back into 1.19.

---

Code Freeze begins on Thursday, July 9th EOD PST

I spoke to @gnufied this evening as since all of the related PRs have not merged he would like to defer this to 1.20

/milestone 1.20

@kikisdeliveryservice: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21]

Use /milestone clear to clear the milestone.

In response to this:

I spoke to @gnufied this evening as since all of the related PRs have not merged he would like to defer this to 1.20

/milestone 1.20

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.

/milestone v1.20

Hi @gnufied !

Enhancements Lead here, do you still intend to target this for alpha in 1.20?

Thanks! Kirsten

Hi @gnufied

Checking in again - will this go alpha in 1.20?

By Enhancements Freeze, Oct 6th, all KEPs intended for the 1.20 Release must be:

• Merged in an implementable state
• Have test plans
• Have graduation criteria
• Have an open issue in the release milestone

Thanks, Kirsten

We are just planning to design this feature in 1.20. I do not think we will be able to implement this in 1.20.

Sounds good, if anything changes just LMK.

Thank you!

/milestone clear

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

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

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-contributor-experience at kubernetes/community. /close

@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-contributor-experience at kubernetes/community. /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.

/reopen

/remove-lifecycle rotten

@gnufied: 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.

@JamesLaverack Can you track this for v1.22? Thanks. The KEP is https://github.com/kubernetes/enhancements/pull/2685.