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

PersistentVolume last phase transition time #3762

Open
8 tasks done
RomanBednar opened this issue Jan 20, 2023 · 37 comments
Open
8 tasks done

PersistentVolume last phase transition time #3762

RomanBednar opened this issue Jan 20, 2023 · 37 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status

Comments

@RomanBednar
Copy link
Contributor

RomanBednar commented Jan 20, 2023

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 20, 2023
@RomanBednar RomanBednar changed the title PV release timestamp PersistentVolume release timestamp Jan 20, 2023
@RomanBednar
Copy link
Contributor Author

/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 Jan 20, 2023
@RomanBednar
Copy link
Contributor Author

/milestone v1.27
/kind feature
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 20, 2023
@k8s-ci-robot
Copy link
Contributor

@RomanBednar: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.27
/kind feature
/stage alpha

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.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 20, 2023
@RomanBednar RomanBednar changed the title PersistentVolume release timestamp PersistentVolume last phase transition time Jan 27, 2023
@jsafrane
Copy link
Member

/milestone v1.27

@k8s-ci-robot k8s-ci-robot added this to the v1.27 milestone Jan 30, 2023
@jsafrane jsafrane added the lead-opted-in Denotes that an issue has been opted in to a release label Jan 30, 2023
@fsmunoz
Copy link

fsmunoz commented Feb 1, 2023

Hello @RomanBednar 👋, v1.27 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (please 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.27
  • 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.

If you could point me to the KEP (or KEP PR), a more detailed analysis can be made.

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!

@fsmunoz
Copy link

fsmunoz commented Feb 8, 2023

@RomanBednar if there's a PR for the KEP please tell me, I can have a look.

@jsafrane
Copy link
Member

jsafrane commented Feb 9, 2023

@fsmunoz #3796, merged with PRR approval for alpha

@fsmunoz
Copy link

fsmunoz commented Feb 9, 2023

@jsafrane thank you - could you please update the description field with the link to the KEP and the appropriate stage information?

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo. NOTE: there is a missing question in the Scalability section of the PRR, added recently. Since this is not mandatory for alpha I'm not taking that into consideration.
  • KEP status is marked as implementable for latest-milestone: 1.27
  • 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.

This enhancement is ready to be traced for graduation to alpha in v1.27

/label tracked/yes
/remove-label tracked/no

@k8s-ci-robot k8s-ci-robot added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Feb 9, 2023
@k8s-ci-robot
Copy link
Contributor

@fsmunoz: Those labels are not set on the issue: tracked/no

In response to this:

@jsafrane thank you - could you please update the description field with the link to the KEP and the appropriate stage information?

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo. NOTE: there is a missing question in the Scalability section of the PRR, added recently. Since this is not mandatory for alpha I'm not taking that into consideration.
  • KEP status is marked as implementable for latest-milestone: 1.27
  • 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.

This enhancement is ready to be traced for graduation to alpha in v1.27

/label tracked/yes
/remove-label tracked/no

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.

@mickeyboxell
Copy link

Hi @RomanBednar 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

@fsmunoz
Copy link

fsmunoz commented Mar 13, 2023

Hi @RomanBednar 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

For this enhancement, it looks like the code PR is not linked in the issue description.

Please let me know what other PRs in k/k I should be tracking for this KEP.

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

@RomanBednar
Copy link
Contributor Author

@fsmunoz thank you, although this will slip to next release as I did not have enough time to finish. Is there anything I need to do to flag this for next release? Apart from updating KEP and this issue?

@fsmunoz
Copy link

fsmunoz commented Mar 14, 2023

@RomanBednar when the new release starts this can be opted-in again. In the meantime I can mark it as Deferred for this release. Thanks!

@Atharva-Shinde Atharva-Shinde removed this from the v1.27 milestone May 14, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/yes Denotes an enhancement issue is 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
@jsafrane
Copy link
Member

/milestone v1.28
/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone May 16, 2023
@RomanBednar
Copy link
Contributor Author

@taniaduggal @Rishit-dagli Doc placeholder PR opened: kubernetes/website#42008

@salehsedghpour
Copy link
Contributor

Hey again @RomanBednar 👋
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 PRs 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 :

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and 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

Hello @RomanBednar 👋, 1.28 Enhancements Lead here.

Unfortunately, the implementation (code related) PR associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.28 milestone.

If you still wish to progress this enhancement in v1.28, please file an exception request. Thanks!

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.28 milestone Jul 19, 2023
@Atharva-Shinde
Copy link
Contributor

Hey again 👋
As the only related PR(according to the issue description) for the code freeze was merged by the additional time approved in the exception request, I am adding this back to v1.28 milestone and changing the status of this enhancement to Tracked :)

/milestone v1.28

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

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.28 milestone Aug 31, 2023
@xing-yang
Copy link
Contributor

/milestone v1.29

@rayandas
Copy link
Member

Hello @RomanBednar 👋, v1.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 beta for v1.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
  • 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.

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

@Princesso
Copy link

Hey there @RomanBednar ! 👋, v1.29 Docs team shadow here.
Does this enhancement work planned for v1.29 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.
Thank you!

@RomanBednar
Copy link
Contributor Author

@Princesso Thank you for the notice, I've opened k/website PR: kubernetes/website#43532

@kcmartin
Copy link

Hi @RomanBednar! 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here's the 1.29 Calendar

@rayandas
Copy link
Member

rayandas commented Oct 28, 2023

Hey again @RomanBednar 👋, 1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: .

Here's where this enhancement currently stands:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).

  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

With all this, the status of this KEP is now tracked for code freeze.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

@Priyankasaggu11929
Copy link
Member

Hello @RomanBednar 👋, 1.29 Enhancements team here.

With below implementation(code related) PRs merged as per the issue description, this enhancement is now marked as tracked for code freeze for the 1.29 Code Freeze! 🚀

The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then.

Please let me know if there are any test PRs we should track. Thanks!

cc: @rayandas

@salehsedghpour
Copy link
Contributor

/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 Jan 6, 2024
@salehsedghpour
Copy link
Contributor

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 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

@k8s-ci-robot k8s-ci-robot removed this from the v1.29 milestone Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
Status: Deferred
Status: Tracked
Status: Tracked for Code Freeze
Development

No branches or pull requests