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
Comments
/sig storage |
/milestone v1.27 |
@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:
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.27 |
Hello @RomanBednar Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
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 |
@RomanBednar if there's a PR for the KEP please tell me, I can have a look. |
@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:
This enhancement is ready to be traced for graduation to alpha in v1.27 /label tracked/yes |
@fsmunoz: Those labels are not set on the issue: In response to this:
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. |
Hi @RomanBednar 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! |
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:
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! |
@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? |
@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! |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):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.
The text was updated successfully, but these errors were encountered: