API gzip compression support

Enhancement Description

• One-line enhancement description (can be used as a release note): Graduate API gzip compression support to GA
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2338-graduate-API-gzip-compression-support-to-GA
  Kubernetes sometimes returns extremely large responses to clients outside of its local network, resulting in long delays for components that integrate with the cluster in the list/watch controller pattern. Kubernetes should properly support transparent gzip response encoding, while ensuring that the performance of the cluster does not regress for small requests.
• Discussion Link:
• Primary contact (assignee): @smarterclayton
• Responsible SIGs: sig-api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.8
  • Beta release target (x.y): 1.16
  • Stable release target (x.y): 1.33?
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s): Add feature gating to REST Compression kubernetes#46966
  • Docs (k/website) update PR(s):
• Beta
  • KEP (k/enhancements) update PR(s): Bring gzip compression for API server to GA #1115
  • Code (k/k) update PR(s): Replace HTTP compression with a more scoped impl, only use on responses > 128KB kubernetes#77449
  • Docs (k/website) update PR(s): Document API response compression website#30639
• GA
  • KEP (k/enhancements) update PR(s): KEP-2338 Graduate API gzip compression to GA #5070
  • Code (k/k) update PR(s):
    • v1.26 Reduce default gzip compression level from 4 to 1 in apiserver kubernetes#112299
    • v1.25 Add flag to disable compression for local traffic kubernetes#111507
    • v1.26 Add a "DisableCompression" option to kubeconfig kubernetes#112309
    • v1.26 Add --disable-compression flag to kubectl kubernetes#112580
    • v1.33 [v1.34]promote APIResponseCompression to GA kubernetes#129748
  • Docs (k/website) update PR(s):

Implementation History

• 1.7 Kubernetes added alpha implementation behind disabled flag
• Updated proposal with more scoped implementation for Beta in 1.16 that addresses prior issues

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

#2331 created for migrating the old keps into new template.

[lasomethingsomething]

/sig api-machinery

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

[sftim]

I'll mention kubernetes/website#30639 - a request to document this feature.

[sftim]

/reopen
I think we should either document it or deprecate it.