-
Notifications
You must be signed in to change notification settings - Fork 14.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
Document API response compression #30639
Comments
/triage accepted |
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 |
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. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
/remove-lifecycle rotten |
@sftim: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
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 |
@a-mccarthy I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on 🙂 |
/remove-lifecycle stale |
/assign |
@sftim what would be a good place to add the
Let me know and I'll add it. Thanks! |
(BTW, anyone is welcome to answer this question) |
@sftim, should I pick the content placement myself? Should I ask in Slack? What's the process? |
Do you know @tengqm? |
I'd prefer adding this to the reference because it is something happening behind the scene. Not all users are aware of it or even care about it. It is not something you have to know to interact with Kubernetes API. |
Thanks! I'll add it to |
This is a Feature Request
What would you like to be added
There is a feature gate,
APIResponseCompression
. There's barely documentation for this feature - mostly just kubernetes/kubernetes#46966 if you find it, I think, plus the source code.Why is this needed
Readers might want to know what kind of compression (eg HTTP hop-by-hop compression, HTTP end-to-end compression) the API Server might employ and under what circumstances.
Can a client turn it off? Can a client demand a compressed response?
Comments
/sig api-machinery
/sig docs
/kind feature
/priority backlog
/language en
The text was updated successfully, but these errors were encountered: