Skip to content
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

add opt-in compression support in storage for apimachinery #4481

Open
armstrongli opened this issue Feb 6, 2024 · 3 comments
Open

add opt-in compression support in storage for apimachinery #4481

armstrongli opened this issue Feb 6, 2024 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@armstrongli
Copy link

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:
  • 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.

@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Feb 6, 2024
@BenTheElder
Copy link
Member

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
Copy link
Member

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
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

5 participants