Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
/remove-lifecycle stale
@verult @vladimirvivien Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP
We plan to move to beta in 1.14. This feature already has a design proposal. Do we need to convert it to a kep?
@msau42 yes please convert it to a KEP! Also let me know if there are any outstanding PRs for this issue. Thanks
kep is here: #742
Didn't we already API review this?
If not, I guess it's me. :)
Didn't we already API review this?
If not, I guess it's me. :)
if so, should be quick, right? :)
Hey folks, I'm helping out with the docs for v1.14.
Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions or need additional guidance!
Hello @msau42, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks
docs pr: kubernetes/website#12889
This feature will remain beta in 1.15
Hey @vladimirvivien @verult @thockin @msau42 - I'm an enhancements shadow for 1.16. Are there plans for this feature to graduate alpha/beta/stable stages? Please let me know so it can be added to the 1.16 Tracking Spreadsheet.
Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.
I noticed there was no KEP linked in the issue description; as a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.
As a reminder; 1.16 milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.
Thanks!
This is remaining beta in 1.16
Hello @msau42, 1.17 Enhancement Shadow here! 🙂
I wanted to reach out to see if this enhancement will be graduating to stable in 1.17?
Please let me know so that this enhancement can be added to 1.17 tracking sheet.
Thank you!
🔔Friendly Reminder
The current release schedule is
A Kubernetes Enhancement Proposal (KEP) must meet the following criteria before Enhancement Freeze to be accepted into the release
Thank you.
HI @kcmartin, we intend to graduate this feature to GA in 1.17. I will be starting on the KEP update shortly.
KEP update: #1273
/milestone v1.17
/assign
API + feature gate PR: kubernetes/kubernetes#83474
Other misc CSI sidecar work tracked in: https://github.com/orgs/kubernetes-csi/projects/19
Hi @msau42 -- We're only 5 days away from the Enhancements Freeze (Tuesday, October 15, EOD PST). Another friendly reminder that to be able to graduate this in the 1.17 release, KEP must have graduation criteria defined, in an implementable state, and merged in.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hello @msau42 I'm one of the v1.17 docs shadows.
Does this enhancement for (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!
Since we're approaching Docs placeholder PR deadline on Nov 8th. Please try to get one in against k/website dev-1.17 branch.
Docs PR: kubernetes/website#17408
Hi @kevtaylor
I am one of the Enhancements Shadows for the 1.17 Release Team. We are very near to Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. I see that kubernetes/kubernetes#83474 was filed in relation to this. Is there any other PR related to this enhancement? If yes, can you please link them here?
Thank you in advance 😄
All the work to make the feature GA in 1.17 is done.
/close
Closed #557.
@msau42: Closing this issue.
In response to this:
All the work to make the feature GA in 1.17 is done.
/close
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.
/reopen
(reopening this issue in the interim)
Reopened #557.
@palnabarun: Reopened this issue.
In response to this:
/reopen
(reopening this issue in the interim)
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.
—