kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.39k stars 1.46k forks source link

Kubelet Evented PLEG for Better Performance #3386

Open harche opened 2 years ago

harche commented 2 years ago

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

harche commented 3 months ago

/reopen

k8s-ci-robot commented 3 months ago

@harche: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/3386#issuecomment-2174178249): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
tallclair commented 2 months ago

/remove-lifecycle rotten /triage accepted

kannon92 commented 3 weeks ago

What is our plans for this KEP in 1.32?

pacoxu commented 3 weeks ago

What is our plans for this KEP in 1.32?

@kannon92 The blocking issue can be fixed by https://github.com/kubernetes/kubernetes/pull/122778 which is still in review.

Ping @smarterclayton @derekwaynecarr @dchen1107 @SergeyKanzhelev

kannon92 commented 2 weeks ago

I'll bring this up in KEP planning.

If you have difficulties getting reviews, I would suggest adding this PR to the sig-node agenda and/or posting on the sig-node slack.

pacoxu commented 1 week ago

We have two blockers here if I understand correctly.

aojea commented 6 days ago

This feature is supposed to replace existing PLEG logic, but it has a track of instability and was also downgraded ... are we going to commit resources to replace existing PLEG logic with this feature? if not, should we not consider to remove it and once we are equipped start over?