add opt-in compression support in storage for apimachinery

[armstrongli]

Enhancement Description

• One-line enhancement description (can be used as a release note):

add opt-in compression support in storage for apimachinery

• Kubernetes Enhancement Proposal:

• add opt-in compression support in storage factory kubernetes#122799
• add opt-in compression support in apiserver kubernetes#122829

• Discussion Link:
• Primary contact (assignee):
• Responsible SIGs:

/sig api-machinery

• Enhancement target (which target equals to which milestone):

the opt-in feature goes to GA directly

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

[BenTheElder]

Kubernetes Enhancement Proposal:
kubernetes/kubernetes#122799
kubernetes/kubernetes#122829

Those are not enhancement proposals.
https://github.com/kubernetes/enhancements/tree/master/keps#kubernetes-enhancement-proposals-keps

the opt-in feature goes to GA directly

This will be discussed in the enhancement proposal, but that seems ... unlikely

[kikisdeliveryservice]

Hi @armstrongli

Please ensure that you discuss your enhancement idea with the sponsoring sig before opening an enhancement in this repo.

After you do that and they give you the go-ahead, please update the Discussion Link of this issue per the instructions:

- Discussion Link: <!-- link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation -->

Thanks!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please 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 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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-sigs/prow repository.