You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: