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. |
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 |
/remove-lifecycle stale |
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 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/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 |
Feature Description
The text was updated successfully, but these errors were encountered: