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

I'm confused. Why can't we switch from StrictFifo to BestEffortFiFo, or from BestEffortFiFo to StrictFifo for a clusterQueue that's in use? #1877

Closed
3 tasks
fjding opened this issue Mar 21, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@fjding
Copy link
Contributor

fjding commented Mar 21, 2024

What would you like to be added:

Why is this needed:

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@fjding fjding added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 21, 2024
@fjding fjding changed the title I'm a bit confused. Why can't we switch from StrictFifo to BestEffortFiFo, or from BestEffortFiFo to StrictFifo for a clusterQueue that's in use? I'm confused. Why can't we switch from StrictFifo to BestEffortFiFo, or from BestEffortFiFo to StrictFifo for a clusterQueue that's in use? Mar 21, 2024
@alculquicondor
Copy link
Contributor

/close

Duplicate of #1873

@k8s-ci-robot
Copy link
Contributor

@alculquicondor: Closing this issue.

In response to this:

/close

Duplicate of #1873

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.

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.
Projects
None yet
Development

No branches or pull requests

3 participants