-
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
Support paged LIST queries from the Kubernetes API #365
Comments
/cc |
This work is part of the SLO improvements we have for kubernetes - helping us meet the requirements of much denser clusters. The key goal for alpha is to prove that it will help us reach the next scale limit for Kubernetes, and will take work across several releases to get there. |
Automatic merge from submit-queue Design for consistent API chunking in Kubernetes In order to reduce the memory allocation impact of very large LIST operations against the Kubernetes apiserver, it should be possible to receive a single large resource list as many individual page requests to the server. Part of kubernetes/enhancements#365. Taken from kubernetes/kubernetes#49338. Original discussion in kubernetes/kubernetes#2349
@smarterclayton @kubernetes/sig-api-machinery-feature-requests @kubernetes/sig-scalability-feature-requests can you confirm that this feature targets 1.8? If yes, please, update the features tracking spreadsheet with the feature data, otherwise, let's remove this item from 1.8 milestone. Thanks |
Yes, it was delivered for 1.8. |
Beta for 1.9 |
Goals for 1.9 - expose in CLI for get.go |
@smarterclayton 👋 Please open a documentation PR and add a link to the 1.9 tracking spreadsheet. Thanks in advance! |
@smarterclayton Bump for docs ☝️ /cc @idvoretskyi |
@smarterclayton @kubernetes/sig-api-machinery-feature-requests @kubernetes/sig-scalability-feature-requests any updates on the docs status? A friendly reminder on docs deadline tomorrow. /cc @zacharysarah |
Bah, I knew I forgot something yesterday. Ended up having to write more
API docs since there wasn't a graceful place to hang the topic.
kubernetes/website#6540
…On Thu, Nov 30, 2017 at 4:09 PM, Ihor Dvoretskyi ***@***.***> wrote:
@smarterclayton <https://github.com/smarterclayton>
@kubernetes/sig-api-machinery-feature-requests
<https://github.com/orgs/kubernetes/teams/sig-api-machinery-feature-requests>
@kubernetes/sig-scalability-feature-requests
<https://github.com/orgs/kubernetes/teams/sig-scalability-feature-requests>
any updates on the docs status?
A friendly reminder on docs deadline tomorrow.
/cc @zacharysarah <https://github.com/zacharysarah>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#365 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p8hXe9e85TlEoQ876BfHH-TVeDQIks5s7xl2gaJpZM4OktK6>
.
|
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. |
/label lead-opted-in |
/milestone v1.29 |
/label lead-opted-in |
Hello @wojtek-t 👋, 1.29 Enhancements team here! Just checking in as we approach enhancements freeze on 01:00 UTC, 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 |
@npolshakova - fixed in #4235 - PTAL |
Thanks! With the addressed, this enhancement is now |
Hey there @smarterclayton 👋, v1.29 Docs team shadow here. |
Hey there @smarterclayton , 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! |
@taniaduggal - documentation PR has already been merged: kubernetes/website#42800 |
Hey again @wojtek-t 👋 1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: . Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): Please make sure to update the issue description with the correct milestone and link the KEP pr in the description as well. This KEP is currently marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
The main PR is: kubernetes/kubernetes#119503 and it was already linked to this issue above... We're code complete for this release now. |
Thanks! Can you update the issue description as well for tracking purposes? It looks a little out of date right now:
|
done |
Hi @wojtek-t, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. |
Thanks @wojtek-t! Can the issue description be updated as well if you get a chance?
|
Hello @wojtek-t 👋, 1.29 Enhancements team here. With kubernetes/kubernetes#119503 merged, all the implementation(code related) PRs are now merged and this enhancement is now marked as Just a reminder, the test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all (if any) test PRs are merged in by then. Please let me know if there are any test PRs we should track. Thanks! |
Hi @wojtek-t, 👋 1.30 Enhancements lead here |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
Feature Description
The text was updated successfully, but these errors were encountered: