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
Allow informers for getting a stream of data instead of chunking #3157
Comments
Hi @p0lyn0mial ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd. This enhancements is targeting
The status of this enhancement is track as |
Hi @gracenng! Many thanks for the heads-up. Could you please double-check the last point? The KEP has the |
Hi @p0lyn0mial, Regarding your second point, I am tracking your KEP files and the first bullet will be checked when the PR is merged. Does that answer your question? |
Hi @p0lyn0mial , 1.24 Enhancements Team here. Reaching out as we're less than a week away from Enhancement Freeze on Thursday, February 3rd. |
Hi @gracenng, it looks like it won't make it to 1.24. Please leave me some instructions on how to update the KEP so it won't show up on your query. |
No worries I’ll take care of it
…On Mon, Jan 31, 2022 at 12:42 AM Lukasz Szaszkiewicz < ***@***.***> wrote:
Hi @gracenng <https://github.com/gracenng>, it looks like it won't make
it to 1.24. Please leave me some instructions on how to update the KEP so
it won't show up on your query.
—
Reply to this email directly, view it on GitHub
<#3157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKCRLOZTCK54ONCDRDEXZCTUYZDP3ANCNFSM5MHDCLRQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@p0lyn0mial how is feature going? we met a lot of server overloading scene(kube-apiserver oom or master oom), looking forward to this feature. if you need help,you can assign some tasks to me. |
@Dingshujie BTW, if you have more than a few hundred nodes, then this fix will probably help to reduce API server load kubernetes/kubernetes#109381 . (If you have more than a few thousand nodes it will definitely help). It solves a bug where the kubelets would keep doing the same listing calls over and over again (typically immediately after a restart of the API server). Obvoiusly, other list issues are possible too, so that fix won't solve them all for you. But it might help. |
@JohnRusk thanks, i already cherry-pick this to 1.23 branch. but this fixs can't slove the situation that custom-defined operator list issues. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
/milestone v1.26 |
Hello @p0lyn0mial, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancement and make sure the |
/label lead-opted-in |
Hello @p0lyn0mial 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Friday, 6th October 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
Hi @p0lyn0mial , checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as Let me know if I missed anything. Thanks! |
As #4207 is now merged the status of this enhancement can be marked as |
Hey there @p0lyn0mial ! 👋, v1.29 Docs team shadow here. |
Hey there @p0lyn0mial, The deadline to open a placeholder PR against k/website for required documentation is Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you! |
Hey there @p0lyn0mial !Could you please update me on the status of docs for this enhancement? Thank you! |
@taniaduggal Hey, I am planning to write a blog post about the feature. However, at this point, it looks like I won't be able to enable this feature for a control plane component as I was planning, due to additional requirements arising late in the cycle. |
Hi @p0lyn0mial, 1.29 Enhancements team here- thanks for letting us know, I'll remove this KEP from the tracking board. |
@p0lyn0mial It seems the feature gate still needs to be updated. |
No - we didn't went beta waiting for a better more generic enablement mechanism [feature gates for client-go]. |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
/sig api-machinery
/sig scalability
The text was updated successfully, but these errors were encountered: