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
Container Resource based Pod Autoscaling #1610
Comments
/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:
The 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 Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
1 similar comment
Hey @arjunrn, I'm following up on my previous update on this Enhancement being part of the Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
Hey @arjunrn, any plans for the Enhancements to be included in 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. Thanks, |
Hey @arjunrn, Unfortunately the deadline for the 1.19 Enhancement freeze has passed and the KEP is still in |
Marking to a deferred milestone after discussing with @arjunrn /milestone v1.20 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hi @arjunrn Enhancements Lead here. Are you still planning on bringing this to alpha in 1.20? Thanks |
@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: 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 👋, 1.20 Docs shadow here. Does this enhancement work planned for 1.20 require any new docs or modification to existing docs? 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, |
@kikisdeliveryservice yes both the implementation and the docs have been merged. |
Hi @arjunrn 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. |
@taniaduggal added the placeholder PR 🙏 |
Hi @annajung 👋, 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 all linked PRs are merged; this is based on the assumption that the "Implementation" PR in the description is the one that is equivalente to "Beta -> Code" . Updating the description to make this explicit would make this clearer. If the above assumption isn't correct, it could be that there are missing PRs linked above and/or they are not merged: this would change the status of this enhancement in terms of code freeze preparedness, and actions would need to be taken before the deadline. 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! |
Hey @fsmunoz , the required PRs for this to get to beta are listed in this catchall issue: kubernetes/kubernetes#115467 and haven't yet been merged. @arjunrn, are you able to update the implementation in the issue description to link to that issue? |
@gjtempleton The PR for the graduation to beta is already listed in the issue. It's the last link. I've also added it to the implementation line. |
I've updated the status above based on the provided information, thanks! |
Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md /milestone clear |
See: kubernetes/kubernetes#116326 (comment) All of the required PRs have already been @marosset Please get this enhancement back to v1.27. |
/milestone v1.27 I'm adding this back into v1.27 per the following slack discussion in slack at https://kubernetes.slack.com/archives/CJH2GBF7Y/p1678843008739849 Thanks @sanposhiho! |
For documentation updates in v1.27: |
Enhancement Description
The text was updated successfully, but these errors were encountered: