-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Memory Manager #1769
Comments
@cezaryzukowski: The label(s) 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. |
/sig node |
/kind kep |
/milestone v1.19 |
@cezaryzukowski: 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 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. |
Hey there @cezaryzukowski @bg-chun -- 1.19 Enhancements Lead here. I wanted to check in and see if you think this Enhancement will be graduating to Alpha in 1.19? In order to have this part of the release:
As an additional note, #1620 merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled since the KEP PR is in flight. 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! 🙂 The current release schedule is:
|
@cezaryzukowski @bg-chun -- Unfortunately, the deadline for the 1.19 Enhancement freeze has passed. 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. |
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 @cezaryzukowski @bg-chun ! Enhancements Lead here, do you still intend to do any work on this (alpha/beta/stable) for 1.20? Thanks! |
Hi @kikisdeliveryservice, yes w plan Alpha for v1.20 as a target. PS We planned Alpha for v1.19, but we couldn't make it. |
Thanks for the update @cezaryzukowski ! As a reminder the KEP PR should also include a kep.yaml file, please see here for the templates: If you could also update the description to reflect alpha in 1.20 that would be great. Best, /milestone v1.20 |
As a reminder Enhancements Freeze is next week ** Tuesday October 6th**. By that time your completed KEP PR will need to merge. If you have any questions, please let me know Best, |
Update: the PR merged! 👍 |
@kikisdeliveryservice Many thanks for your support. Do we need to do anything else beyond "KEP merged" to have this feature in v1.20? |
Hi @cezaryzukowski at the moment, no. 😄 But you do have to keep to all of the remaining milestone deadlines such as Code Freeze (Nov 12th) and Test Freeze(Nov 23rd) as well as the Docs Placeholder PR deadline of Nov 6th. As you go forward, also please link all PRs related to this enhancement on this issue. Lmk if you have any questions!!! I'll be here 😄 and will remind you of upcoming important dates. |
That's grand, we know the exact schedule. With respect to "Docs Placeholder PR", is there any template or guideline on how to prepare the docs? |
Hi @cezaryzukowski ! So the placeholder PR is very simple. See: https://kubernetes.io/docs/contribute/new-content/new-features/#open-a-placeholder-pr. This tells the docs team that you intend on adding feature documentation. Later on you'll add that full documentation and work with the docs team. You just need to do the placeholder by Nov. 6th but the sooner the better =) Also, going forward, please link the placeholder PR and any k/k PRs back to this issue so the team can track them. If you have any questions, let me know 😸 Just to recap: Thanks! |
Hello @rashansmith I opened a placeholder PR kubernetes/website#48578 |
Thank you @jenshu for the reminder.
I do not have permission to edit the original issue description. we're tracking the recent work here:
@ffromani WDYT?
At this point there's none. |
@Tal-or thanks, I've updated the issue description to add the missing PR |
Too early to tell. Let's reconvene after sig-node meeting 2024/Oct/29 |
WIP. Initial commit in order to have a feature blog placeholder PR see: kubernetes/enhancements#1769 (comment) Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Docs update for the Kubelet Memory Manager GA graduation Issue: kubernetes/enhancements#1769 Signed-off-by: Francesco Romani <fromani@redhat.com>
Docs update for the Kubelet Memory Manager GA graduation Issue: kubernetes/enhancements#1769 Signed-off-by: Francesco Romani <fromani@redhat.com>
Docs update for the Kubelet Memory Manager GA graduation Issue: kubernetes/enhancements#1769 Signed-off-by: Francesco Romani <fromani@redhat.com>
Hello @rashansmith, The blog is ready for review: kubernetes/website#48578 |
Hello @Tal-or 👋, v1.32 Enhancements team here. With all the implementation (code related) PRs merged as per the issue description:
This enhancement is now marked as Please note that KEPs targeting |
Hello @rashansmith, Wanted to make sure the blog: kubernetes/website#48578 review is not missed for this release cycle. |
/reopen A github workflow autoclosed when I set to done 🙃 sorry for the noise |
@haircommander: Reopened this 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-sigs/prow repository. |
Docs update for the Kubelet Memory Manager GA graduation Issue: kubernetes/enhancements#1769 Signed-off-by: Francesco Romani <fromani@redhat.com>
Hi @Tal-or, 👋 1.33 Enhancements lead here, Now that this KEP has graduated to |
/remove-label lead-opted-in |
Enhancement Description
k/enhancements
) update PR(s): Submitting a KEP for production readiness approval #2456k/k
) update PR(s): Memory manager kubernetes#95479k/website
) update(s): The Memory Manager official documentation website#26730k/enhancements
) update PR(s): Graduate memory manager to beta #2708k/k
) update PR(s):k/website
) update(s):k/enhancements
) update PR(s): KEP-1769: Graduate Memory Manager to GA #4251k/k
) update PR(s):k/website
) update(s):The text was updated successfully, but these errors were encountered: