Support new upstream api #69
Labels
Comments
|
Seconded. Would love the ability to add multiple upstreams/targets to an api via the config file. Use case is using kong to route upstream to containers in a rancher cluster without using DNS and being able to control what containers belong to what api (ie swapping container sets in a blue/green deploy scenario) |
dgarlitt
added a commit
to dgarlitt/kongfig
that referenced
this issue
Nov 14, 2017
This adds upstream and target capabilities to kongconfig as requested in: mybuilder#69
dgarlitt
added a commit
to dgarlitt/kongfig
that referenced
this issue
Nov 15, 2017
This adds upstream and target capabilities to kongconfig as requested in: mybuilder#69
dgarlitt
added a commit
to dgarlitt/kongfig
that referenced
this issue
Nov 15, 2017
This adds upstream and target capabilities to kongfig as requested in: mybuilder#69
dgarlitt
added a commit
to dgarlitt/kongfig
that referenced
this issue
Nov 16, 2017
This adds upstream and target capabilities to kongfig as requested in: mybuilder#69
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kong/kong#1735
The text was updated successfully, but these errors were encountered: