envoyproxy/envoy

Runtime configuration of HTTP fault injection per upstream cluster

Open

#10,173 opened on Feb 26, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: HTTP fault injection filter can have runtime settings per downstream cluster, but not upstream cluster.

Description: I'm trying to simulate a failure of an external service. In my case, fault injection filter should be configured as one of the egress http filters to inject delay or abort requests to the external service. I want to inject failure only to the requests to the specific upstream cluster (the external service) in runtime. But as described here, fault injection filter allows runtime setting only per downstream cluster by , not upstream cluster.

Thanks

Contributor guide

Research direction
Examine the implementation of runtime key configuration for downstream fault injection in Envoy's fault filter (source/extensions/filters/http/fault). Understand how the runtime keys are derived from downstream cluster names. Then design a similar mechanism for upstream clusters, considering that the fault filter may be configured per upstream cluster via route configuration. Look at how the filter accesses cluster information and modify accordingly.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy proxy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30