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

Chaos Engineering/Fault Injection #3575

Open
howardjohn opened this issue Jan 29, 2025 · 3 comments
Open

Chaos Engineering/Fault Injection #3575

howardjohn opened this issue Jan 29, 2025 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@howardjohn
Copy link
Contributor

What would you like to be added:

An API to inject faults into routes. Typically a fault may be a delay, an HTTP response, or others.

Why this is needed:

Fault injection / Chaos engineering is a somewhat common engineering practice to intentional introduce errors into the system to simulate disaster recovery and other reliability mechanisms.

Prior art:

Slightly related to #2826

@howardjohn howardjohn added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 29, 2025
@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 11, 2025
@shaneutt shaneutt moved this to Triage in Gateway API Pipeline Feb 11, 2025
@shaneutt
Copy link
Member

shaneutt commented Feb 11, 2025

How do you see this being implemented, as a testing library that we provide to implementations or just an API?

@howardjohn
Copy link
Contributor Author

No, just a HTTPRoute filter or policy. Like https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPFaultInjection, for example. Then users or tooling can utilize that to build a holistic chaos engineering strategy

@shaneutt
Copy link
Member

No, just a HTTPRoute filter or policy. Like https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPFaultInjection, for example. Then users or tooling can utilize that to build a holistic chaos engineering strategy

Ok, just wanted to be sure. The API specification for this sounds good, but the reason I asked about test libs is that I wouldn't be opposed to discussing having some standard "Gateway API Fault Injection" tooling. 🤔

In any case, I'm supportive of further discussing and working towards a proposal here.

@shaneutt shaneutt added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 12, 2025
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. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Status: Triage
Development

No branches or pull requests

2 participants