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

Multiple upstreams support #258

Open
freznicek opened this issue Aug 22, 2019 · 2 comments
Open

Multiple upstreams support #258

freznicek opened this issue Aug 22, 2019 · 2 comments

Comments

@freznicek
Copy link

freznicek commented Aug 22, 2019

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:

  • run toxiproxy and load all proxies to the dependent applications
  • force the application (app under test) to route via launched toxiproxy (via local linux /etc/hosts resolver)

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
Copy link

Any update on this please?

@Anu5399
Copy link

Anu5399 commented Jan 28, 2024

any update on this one ??

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

3 participants