enhancements
enhancements copied to clipboard
Kubelet Evented PLEG for Better Performance
Enhancement Description
- One-line enhancement description (can be used as a release note): Kubelet Evented PLEG for Better Performance
- Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3386-kubelet-evented-pleg/README.md
- Discussion Link: https://kubernetes.slack.com/archives/C03HA69L6R1 ,https://github.com/kubernetes/kubernetes/pull/110165
- Primary contact (assignee): @harche, @haircommander, @ruiwen-zhao
- Responsible SIGs: sig-node
- Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.25
- Beta1 release target (x.y): 1.27 (default false)
- Revert to alpha: 1.30 (v1.27.9γv1.28.6γv1.29.1)
- Beta release target (x.y):
- Stable release target (x.y):
- [x] Alpha
- [x] API Changes - https://github.com/kubernetes/kubernetes/pull/111642
- [x] KEP (
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3387 - [x] Code (
k/k
) update PR(s): https://github.com/kubernetes/kubernetes/pull/111384
- [x] Beta (default disabled)
- [x] KEP (
k/enhancements
) update- PR(s): https://github.com/kubernetes/enhancements/pull/3817
- [x] Code (
k/k
) update PR(s):- https://github.com/kubernetes/kubernetes/pull/115967
- https://github.com/kubernetes/test-infra/pull/28366
- https://github.com/kubernetes/test-infra/pull/28592
- [x] Docs (
k/website
) updates(s):- https://github.com/kubernetes/website/pull/39913
- [x] KEP (
- [ ] Revert to alpha
- [ ] KEP (
k/enhancements
) update PR(s): - [ ] Code (
k/k
) update PR(s):- [x] v1.30(backported): https://github.com/kubernetes/kubernetes/pull/122697
- [x] v1.29: https://github.com/kubernetes/kubernetes/pull/120942
- [x] v1.30: https://github.com/kubernetes/kubernetes/pull/122475/
- [ ] Docs (
k/website
) update(s):
- [ ] KEP (
- [ ] Beta
- [ ] Issues to fix before re-promoting it to beta:
- [ ] https://github.com/kubernetes/kubernetes/issues/121003
- [ ] https://github.com/kubernetes/kubernetes/issues/121349 WIP in : https://github.com/kubernetes/kubernetes/pull/122124
- [ ] KEP (
k/enhancements
) update PR(s): - [ ] Code (
k/k
) update PR(s): - [ ] Docs (
k/website
) update(s):
- [ ] Issues to fix before re-promoting it to beta:
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
/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 alpha
for 1.25 (correct me, if otherwise)
Here's where this enhancement currently stands:
- [X] KEP file using the latest template has been merged into the k/enhancements repo.
- [X] KEP status is marked as
implementable
- [X] KEP has a updated detailed test plan section filled out
- [X] KEP has up to date graduation criteria
- [X] KEP has a production readiness review that has been completed and merged into k/enhancements.
Looks like for this one, we would need to update the following:
- update the
kep.yaml
file in the merged KEP to addlatest-milestone: "v1.25β
For note, the status of this enhancement is marked as at risk
. Thank you for keeping the issue description up-to-date!
I opened https://github.com/kubernetes/enhancements/pull/3410 to target at 1.25
/sig node
With KEP PR https://github.com/kubernetes/enhancements/pull/3410 merged, the enhancement is ready for the 1.25 Enhancements Freeze.
For note, the status is now marked as tracked
. Thank you so much! π
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:
- [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
- [ ] All PRs are fully merged by the code freeze deadline.
- https://github.com/kubernetes/kubernetes/pull/111384
I was able to find the following draft k/k PRs for the KEP:
- https://github.com/kubernetes/kubernetes/pull/110911
- https://github.com/kubernetes/kubernetes/pull/110912
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 at-risk
.
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 - https://github.com/kubernetes/kubernetes/pull/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 at risk
Thank you
API Changes PR - https://github.com/kubernetes/kubernetes/pull/111642
Hello :wave:, 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 (I'm doing this on behalf of @ruiwen-zhao / SIG-node)
/stage alpha /label tracked/yes /remove-label tracked/no
/milestone v1.26 /label lead-opted-in
(this is a carry over from prior release, hope it makes alpha)
Hello @harche, @haircommander, and @ruiwen-zhao π, 1.26 Enhancements team here.
Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.
This enhancement is targeting for stage alpha
for 1.26 (correct me, if otherwise)
Here's where this enhancement currently stands:
- [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
- [ ] KEP status is marked as
implementable
forlatest-milestone: 1.26
- [ ] KEP readme has a updated detailed test plan section filled out
- [ ] KEP readme has up to date graduation criteria
- [X] KEP has a production readiness review that has been completed and merged into k/enhancements.
For this KEP, we would need to open a PR to make changes to the KEP yaml and KEP readme.
The status of this enhancement is marked as at risk
. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
@rhockenbury Link to the PR - https://github.com/kubernetes/enhancements/pull/3575
Thanks, please plan to get https://github.com/kubernetes/enhancements/pull/3575 merged up before enhancements freeze.
@rhockenbury https://github.com/kubernetes/enhancements/pull/3575 is now merged and it should check all the boxes in https://github.com/kubernetes/enhancements/issues/3386#issuecomment-1266093148
Thanks, I have it marked as tracked
now.
Hey @harche @ruiwen-zhao @haircommander π,
Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.
Please ensure the following items are completed:
- [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the issue description above(for tracking purposes). If there are any other PRs beyond:
https://github.com/kubernetes/kubernetes/issues/111384 and https://github.com/kubernetes/kubernetes/issues/111642 please include them in the issue description too. - [ ] All PRs are fully merged by the code freeze deadline.
As always, we are here to help should questions come up. Thanks :)
Hello @harche ! ππΎ,
@katmutua 1.26 Release Docs shadow here. This enhancement is marked as βNeeds Docsβ for 1.26 release.
Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9.
Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. As a reminder, please link all of your docs PR to this issue so we can easily track it.
@katmutua Considering this feature is just alpha, I am not sure if we need to have docs.
cc @haircommander @ruiwen-zhao
Hi @harche , here Carol from the Doc Lead of 1.26, I think we need to update the Kubernetes documentation features with alpha, for example here cc @reylejano
@harche ,
For 1.26, since this enhancement has a feature gate of EventedPLEG
, this should be added to the feature gates page in the Feature gates for Alpha or Beta features table:
https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features
Thanks @katmutua @krol3 and @reylejano. I have created a doc PR https://github.com/kubernetes/website/pull/37715 to add EventedPLEG
in the features table.
cc @swghosh @rphillips
Hey @harche @ruiwen-zhao @haircommander π, just a quick check-in again before 1.26 code freeze at 17:00 PDT Tuesday 8th November 2022 i.e tomorrow. Looks like we would at least need to get the code PR/s: https://github.com/kubernetes/kubernetes/pull/111384 (any other PRs?) merged before the code-freeze.
With https://github.com/kubernetes/kubernetes/pull/111384 merged, we have this marked as tracked
for code freeze.
Hey @harche @ruiwen-zhao @haircommander wave, just a quick check-in again before 1.26 code freeze at 17:00 PDT Tuesday 8th November 2022 i.e tomorrow. Looks like we would at least need to get the code PR/s: kubernetes/kubernetes#111384 (any other PRs?) merged before the code-freeze.
Not directly a code PR, but there is this doc PR - https://github.com/kubernetes/website/pull/37715