/sig autoscaling
Hey there @arjunrn -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?
In order to have this part of the release:
implementable
stateThe current release schedule is:
If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 馃憤
Thanks!
Hey @arjunrn, I'm following up on my previous update on this Enhancement being part of the v1.19
release.
Do you happen to have any update on the possiblity of this being included in the release v1.19
?
Thanks again for your time and contributions. 馃枛
Hey @arjunrn, I'm following up on my previous update on this Enhancement being part of the v1.19
release.
Do you happen to have any update on the possiblity of this being included in the release v1.19
?
Thanks again for your time and contributions. 馃枛
Hey @arjunrn, any plans for the Enhancements to be included in v1.19
? Please let me know so that I can update the tracking sheet to show the inclusion state.
_Enhancements freeze is on May 19_
Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template.
Please take this opportunity to reformat your KEP and also answer the questions added to the template in that PR.
Thanks,
馃枛
Hey @arjunrn, Unfortunately the deadline for the 1.19 Enhancement freeze has passed and the KEP is still in provisional
state. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception.
Marking to a deferred milestone after discussing with @arjunrn
/milestone v1.20
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
/remove-lifecycle stale
Hi @arjunrn
Enhancements Lead here. Are you still planning on bringing this to alpha in 1.20?
Thanks
Kirsten
@kikisdeliveryservice Yes, I'm still working on it and hope to have the feature merged in time for 1.20
Great thanks for the update!
Hi @arjunrn,
1.20 Enhancement shadow here 馃憢.
Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze
As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.
Thank you!
@kinarashah Updated the description with the implementation and docs PR links.
That's awesome, thank you for getting them up so quickly!
Hello @arjunrn :wave:, 1.20 Docs shadow here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20
branch in the k/website
repo.
This PR can be just a placeholder at this time and must be created before Nov 6th
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
Hey @arjunrn
Just to confirm : This is now finished for 1.20 correct?
_Just a reminder that Code Freeze is coming up tomorrow Thursday, November 12th. All PRs must be merged by that date, otherwise an Exception is required._
Thanks,
Kirsten
@kikisdeliveryservice yes both the implementation and the docs have been merged.
Most helpful comment
@kinarashah Updated the description with the implementation and docs PR links.