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

Support increasing the etcd size limit #864

Open
Sharpz7 opened this issue Dec 11, 2023 · 4 comments
Open

Support increasing the etcd size limit #864

Sharpz7 opened this issue Dec 11, 2023 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone

Comments

@Sharpz7
Copy link

Sharpz7 commented Dec 11, 2023

What would you like to be added?

See etcd-io/etcd#15354 (comment), this limit is not hard-imposed.

Why is this needed?

For testing the limits of what etcd can do with Kubernetes, KWOK is a great base for a performance testing framework.

@Sharpz7 Sharpz7 added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 11, 2023
@Sharpz7
Copy link
Author

Sharpz7 commented Dec 11, 2023

Please assign me, I will work on it soon

@wzshiming
Copy link
Member

/assign @Sharpz7

Thank you

@wzshiming wzshiming added this to the v0.5 milestone Dec 18, 2023
@wzshiming wzshiming modified the milestones: v0.5, v0.6 Dec 28, 2023
@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 Mar 27, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

4 participants