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

Feature Request: HTTP path filter parameter for faults #5033

Open
dldldlepl opened this issue Jan 27, 2025 · 1 comment
Open

Feature Request: HTTP path filter parameter for faults #5033

dldldlepl opened this issue Jan 27, 2025 · 1 comment

Comments

@dldldlepl
Copy link

Pod Chaos faults, which are used to modify HTTP requests and responses, are right now not supporting a parameter to filter the requests based on the HTTP path. Therefore, experiments like pod-http-latency, pod-http-reset-peer, pod-http-status-code, pod-http-modify-body, pod-http-chaos are always applied to all the requests no matter what the path is. This is a feature request to add a parameter to filter the requests based on the HTTP path.

This would allow to apply the faults only to the requests that match the specified path. It would be useful to simulate scenarios where an application with multiple endpoints fails only on a subset of them. With e.g. a regular expression, it could be possible to match multiple paths at once and apply the fault to those requests.

Furthermore, it would allow to keep the liveness and readiness probes working while the other endpoints are failing creating more realistic scenarios. As often, when the liveness and readiness probes are not removed/disabled the pods are restarted, and then the chaos is not realistic anymore to the real example, where only a subset of the endpoints are failing.

A similar question was already asked in the discussions section: #4423, where also a feature request, was considered to get created but I couldn't find it.

@Denish3436
Copy link
Contributor

Hi @dldldlepl assign to me, I want to work on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants