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.

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

Support recovery from volume expansion failure #1790

Open
12 tasks
gnufied opened this issue May 18, 2020 · 82 comments
Open
12 tasks

Support recovery from volume expansion failure #1790

gnufied opened this issue May 18, 2020 · 82 comments
Assignees
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status

Comments

@gnufied
Copy link
Member

gnufied commented May 18, 2020

Enhancement Description

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 18, 2020
@gnufied
Copy link
Member Author

gnufied commented May 18, 2020

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 18, 2020
@palnabarun
Copy link
Member

/milestone v1.19

@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone May 18, 2020
@palnabarun
Copy link
Member

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 18, 2020
@palnabarun palnabarun added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 18, 2020
@liggitt liggitt added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label May 21, 2020
@palnabarun
Copy link
Member

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


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

@mikejoh
Copy link

mikejoh commented May 26, 2020

Hello, @gnufied ! 👋 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.

@palnabarun
Copy link
Member

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

@gnufied
Copy link
Member Author

gnufied commented Jun 1, 2020

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

@gnufied
Copy link
Member Author

gnufied commented Jun 10, 2020

PR that implements necessary API changes and updates quota calculation code - kubernetes/kubernetes#91976

@mikejoh
Copy link

mikejoh commented Jun 15, 2020

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!

@palnabarun
Copy link
Member

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


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

@gnufied
Copy link
Member Author

gnufied commented Jun 19, 2020

Docs PR - kubernetes/website#21920

@palnabarun
Copy link
Member

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

Thank you. 🙂


Code Freeze begins on Thursday, July 9th EOD PST

@annajung
Copy link
Contributor

annajung commented Jul 6, 2020

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!

@gnufied
Copy link
Member Author

gnufied commented Jul 6, 2020

@annajung done. thank you.

@palnabarun
Copy link
Member

@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

@kikisdeliveryservice
Copy link
Member

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

@k8s-ci-robot
Copy link
Contributor

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

@kikisdeliveryservice
Copy link
Member

/milestone v1.20

@k8s-ci-robot k8s-ci-robot removed this from the v1.19 milestone Jul 10, 2020
@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 May 8, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels May 14, 2023
@xing-yang
Copy link
Contributor

/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 May 22, 2023
@xing-yang xing-yang added lead-opted-in Denotes that an issue has been opted in to a release stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels May 22, 2023
@Atharva-Shinde
Copy link
Contributor

Atharva-Shinde commented May 23, 2023

Hello @gnufied 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.

Looks like this enhancement is targeting for stage alpha for v1.28

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:v1.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would need to update the following:

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 :)

@carlory
Copy link
Member

carlory commented Jun 14, 2023

Hi @Atharva-Shinde, this kep is updated by #4083 .

@Atharva-Shinde
Copy link
Contributor

Hey @carlory

This is a nit that needs to be addressed:
Add the acknowledgement under the Test Plan section.
I won't decline this KEP for the Enhancements freeze because of this change but would be great to get a PR ready addressing it.

From the comments above it seems that this enhancement already had a PRR done for stage alpha, if not please let me know ASAP.

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@carlory
Copy link
Member

carlory commented Jun 16, 2023

Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@gnufied I can't update it. Can you help to do it?

@AdminTurnedDevOps
Copy link

Hey @gnufied

1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@Rishit-dagli
Copy link
Member

Hey @gnufied , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

@Atharva-Shinde
Copy link
Contributor

Hey again @carlory @gnufied 👋
Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

  • All the PR/s that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
  • All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

For this enhancement, it looks like the following code related PR/s are open and they need to be merged or should be in merge-ready state before the code freeze commences :

Also please let me know if there are other PR/s in k/k we should be tracking for this KEP.

As always, we are here to help if any questions come up. Thanks!

@Atharva-Shinde
Copy link
Contributor

Hey @carlory @gnufied 👋 Enhancements Lead here,
With kubernetes/kubernetes#116335 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!

@Rishit-dagli
Copy link
Member

Hey @carlory @gnufied , we are already past the deadline for having a draft docs PR make on kubernetes/website , could you please do this as soon as possible, it could be a PR with no content yet too.

@gnufied
Copy link
Member Author

gnufied commented Jul 26, 2023

Sorry I was on PTO. I am working on updating existing docs with new API changes. Sorry about the delay.

@gnufied
Copy link
Member Author

gnufied commented Jul 28, 2023

I made kubernetes/website#42277 that updates existing doc with newer field.

@npolshakova
Copy link

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Aug 27, 2023
@salehsedghpour
Copy link
Contributor

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.28 now,
If you wish to progress this enhancement in v1.30, please 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 and finally add /milestone v1.30. Thanks!

/milestone clear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Status: Graduating
Status: Deferred
Status: Tracked
Development

No branches or pull requests