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.27
  • Beta release target (x.y): 1.28
  • Stable release target (x.y): 1.30?
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3333 Retroactive default StorageClass assignment #3337
  • Code (k/k) update PR(s):
    • WIP: PersistentVolume last phase transition time kubernetes#116469
  • Docs (k/website) update PR(s):

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!