PersistentVolume last phase transition time

[RomanBednar]

Enhancement Description

• One-line enhancement description (can be used as a release note): PersistentVolume release timestamp
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/3762-persistent-volume-last-phase-transition-time/README.md
• Discussion Link: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#bookmark=id.k72l93cygtip
• Primary contact (assignee): @RomanBednar
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.28
  • Beta release target (x.y): 1.29
  • Stable release target (x.y): 1.31
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3762: PersistentVolume last phase transition time #3796
  • Code (k/k) update PR(s):
    • PersistentVolume last phase transition time kubernetes#116469
  • Docs (k/website) update PR(s):
    • Add docs for PersistentVolume last phase transition time website#42008
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3762: graduate PersistentVolumeLastPhaseTransitionTime to beta in v1.29 #4125
  • Code (k/k) update PR(s):
    • graduate PersistentVolumeLastPhaseTransitionTime to beta in v1.29 kubernetes#120627
  • Docs (k/website) update PR(s):
    • graduate PersistentVolumeLastPhaseTransitionTime to beta in v1.29 website#43532
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-3762: graduate PersistentVolumeLastPhaseTransitionTime to GA in 1.31 #4644
  • Code (k/k) update PR(s):
    • graduate PersistentVolumeLastPhaseTransitionTime to GA in 1.31 kubernetes#124969
  • Docs (k/website) update(s)
    • graduate PersistentVolumeLastPhaseTransitionTime to GA in v1.31 website#46463

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

[RomanBednar]

/sig storage

[RomanBednar]

/milestone v1.27
/kind feature
/stage alpha

[k8s-ci-robot]

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

[jsafrane]

/milestone v1.27

[fsmunoz]

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]

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

[jsafrane]

@fsmunoz #3796, merged with PRR approval for alpha

[fsmunoz]

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

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

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]

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]

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

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

[jsafrane]

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

[sreeram-venkitesh]

@xing-yang I removed the label by mistake, I've added it back.

/label lead-opted-in

[ArkaSaha30]

Hello @RomanBednar 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting stage stable for v1.31 (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: v1.31. 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

All the KEP requirements are 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!

[MaryamTavakkoli]

Hello @RomanBednar 👋, 1.31 Docs Shadow here.
Does this enhancement work planned for 1.31 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, June 27, 2024, 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!

[edithturn]

Hello @RomanBednar!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[edithturn]

Hello @RomanBednar!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Hi @RomanBednar 👋!

Just a friendly reminder: if you need to open a Feature Blog placeholder PR against the website repository, please go ahead and do so. If you have any questions or need any help, feel free to reach out! For more information about writing a blog, check out the blog contribution guidelines.

Remember, the deadline for this is coming up soon: Wednesday, July 03, 2024, at 18:00 PDT.

Thank you!!
Edith

[ArkaSaha30]

Hey again @RomanBednar 👋, Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

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.

Regarding this enhancement, it appears that there is 1 open PR in the k/k repository with an LGTM label and pending review.

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

• Ensure the PR has approved by the code freeze deadline.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is currently marked as at risk for code freeze.

[ArkaSaha30]

Hey again @RomanBednar 👋, 1.31 Enhancements team here,

Everything is in place for this KEP issue, now that the code implementation PRs mentioned in the description have been merged before the code freeze (02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024).

This enhancement is now marked as tracked for code freeze for the 1.31 Code Freeze! 🎉

[tjons]

@RomanBednar in preparation for the next release, now that this KEP has been implemented, would you kindly update the KEP status to implemented and then close this out?

[tjons]

Hello 👋 1.32 Enhancements Lead here,

I'm closing milestone 1.31 now,
If you have more work on this enhancement to complete in v1.32, 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.32. Thanks!

/milestone clear

[tjons]

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

[RomanBednar]

Thank you @tjons I've opened the PR for changing KEP status here: #4864

There is no further work planned in 1.32.