Shopify / toxiproxy

:alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing
https://github.com/shopify/toxiproxy
MIT License
10.64k stars 445 forks source link

Multiple upstreams support #258

Open freznicek opened 5 years ago

freznicek commented 5 years ago

What (proposal)

I'd like to get support of multiple upstream hosts in single proxy + definition of balancing strategy (at least round-robin and/or least/most-connected).

As of now (v2.1.4) there is no way how to specify multiple upstreams for single proxy at least in toxiproxy-cli and python toxiproxy client.

Why (use-case)

My use-case uses toxiproxy to test the application's behaviour when introduced a toxics between the application and any of depending applications (all in kubernetes). The way we introduce toxics w/o necessity of the application a change is to:

Given the strategy it is clear that toxiproxy proxy binds same port as dependent app has/binds (no port translation in place).

Here comes the trouble, there is the application which communicates with HA storage consisting of multiple hosts binding the same port (redis sentinel), for such case I'd like to create toxiproxy proxy with multiple upstreams to block none / all upstreams.

The current workaround I have is to use multiple toxiproxy instances, but it comes with additional orchestration cost.

Any suggestions how to deal with the scenario are welcome.

jalpa-pujara commented 11 months ago

Any update on this please?

Anu5399 commented 8 months ago

any update on this one ??