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
Kubelet Evented PLEG for Better Performance #3386
Comments
/sig-node |
Hello @harche 👋, 1.25 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022. For note, This enhancement is targeting for stage Here's where this enhancement currently stands:
Looks like for this one, we would need to update the following:
For note, the status of this enhancement is marked as |
I opened #3410 to target at 1.25 |
/sig node |
With KEP PR #3410 merged, the enhancement is ready for the 1.25 Enhancements Freeze. For note, the status is now marked as |
Hello @haircommander @harche 👋 Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure the following items are completed:
I was able to find the following draft k/k PRs for the KEP: Please verify, if there are any additional k/k PRs besides the ones listed above. Please plan to get the open/draft k/k merged by the code freeze deadline. The status of the enhancement is currently marked as Thank you for keeping the issue description up-to-date! |
Thanks @Priyankasaggu11929 for reaching out. I am planning to raise a PR by coming Monday. |
@Priyankasaggu11929 I just raised a PR - kubernetes/kubernetes#111384 |
Hello @harche 👋 Just a gentle reminder from the enhancement team as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022 (which is almost 2 days from now) Please plan to have the open k/k PR merged before then. The status of this enhancement is currently marked as Thank you |
API Changes PR - kubernetes/kubernetes#111642 |
Hello 👋, 1.25 Enhancements Lead here. Unfortunately, this enhancement did not meet the code freeze criteria because there are still unmerged k/k code PRs. If you still wish to progress this enhancement in v1.25, please file an exception request. Thank you so much! /milestone clear |
@Priyankasaggu11929 Request for the exception has been raised - https://groups.google.com/g/kubernetes-sig-node/c/H_jmCppaurU/m/vwOzc-EFAAAJ |
/milestone v1.26 |
/label lead-opted-in |
/milestone v1.27 |
@harche: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads] 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. |
Hello @harche, @haircommander, @ruiwen-zhao 👋, Enhancements team here. 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:
For this enhancement, it looks like #3386 will address the remaining requirements. The status of this enhancement is marked as |
@marosset We are aiming to graduate this feature to |
@marosset I see that this enhancement has been moved to 1.27 tracking board but the tag on this issue still says |
|
This enhancement meets all of the requirements to be included in v1.27 and is now tracked for the release. |
Hi @harche, @haircommander, @ruiwen-zhao 👋, 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 following PRs are open and need to be merged before code freeze: Please let me know if there are any other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
Hi @harche 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. |
Thanks @taniaduggal. I have created a PR in k8s/website - kubernetes/website#39913 |
Wanted to post it here: https://kubernetes.slack.com/archives/C05KQLJEWHX/p1692383024035069 We see from Containerd that events may overflow and not being send to kubelet. Which will lead to wrong results. Before moving this forward we need to understand how is it happened and whether we see it in other cases. Loosing events will result in bad outcome and hard to troubleshoot bugs |
Enhancement Description
k/enhancements
) update PR(s): KEP-3386: Kubelet Evented PLEG for Better Performance #3387k/k
) update PR(s): Add Support for Evented PLEG kubernetes#111384k/enhancements
) updatek/k
) update PR(s):k/website
) updates(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: