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.

Sign up for GitHub

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

Jump to bottom

GEP: Circuit breaking #3358

Open
youngnick opened this issue Sep 24, 2024 · 0 comments
Open

GEP: Circuit breaking #3358

youngnick opened this issue Sep 24, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@youngnick
Copy link
Contributor

What would you like to be added:
Gateway API should support some method of configuring circuit breaking settings. This could be a Policy, a filter, or some other method.

Note that this is useful for both north-south (ingress) and east-west (GAMMA) use cases, so will need both groups to be on board with the approach.
@youngnick youngnick added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Sep 24, 2024
@youngnick youngnick mentioned this issue Sep 24, 2024
Open
@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Gateway API Enhancement Proposals (GEPs)
Status: Proposed
Post-GA Refinement
Status: Triage
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shaneutt @youngnick