Skip to content

RFC: Support dynamic reconfiguration of "buckets" #1956

Open

Description

@mattmoor

/area API
/kind feature

I mentioned this in slack, but given that we already support being promoted to and demoted from "leader" dynamically, could we support dynamically changing the bucket count by:

  1. Demoting all the current buckets,
  2. Promoting new buckets as we gain ownership of them.

I haven't looked deeply into what this would entail at a code level yet, but I wanted to float the idea for broader discussion.

Activity

  1. github-actions commented on Mar 11, 2021

    @github-actions
    Contributor

    This issue is stale because it has been open for 90 days with no
    activity. It will automatically close after 30 more days of
    inactivity. Reopen the issue with /reopen. Mark the issue as
    fresh by adding the comment /remove-lifecycle stale.

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 11, 2021
  3. vdemeester commented on Feb 14, 2024

    @vdemeester
    Contributor

    @mattmoor @dprotaso could we re-open that issue ? I think it's still a valid thing to work on 👼🏼

  4. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 20, 2024
  5. github-actions commented on May 20, 2024

    @github-actions
    Contributor

    This issue is stale because it has been open for 90 days with no
    activity. It will automatically close after 30 more days of
    inactivity. Reopen the issue with /reopen. Mark the issue as
    fresh by adding the comment /remove-lifecycle stale.

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 20, 2024
  7. vdemeester commented on Jun 19, 2024

    @vdemeester
    Contributor

    /reopen
    /lifecycle frozen

  8. knative-prow commented on Jun 19, 2024

    @knative-prow

    @vdemeester: Reopened this issue.

    Details

    In response to this:

    /reopen
    /lifecycle frozen

    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.

  9. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/APIkind/featurelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions