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
Currently, setHeaderRoute adds a new route in the virtualService but only allows configuring a match with headerName and headerValue. It would be interesting to also allow configuring the method and path settings similar to setMirrorRoute.
Use Cases
Situations where the environment uses a common FQDN for more than one workload api.foo.local and routing is done using path /v1/bar, /v1/foo. With the current scenario, activating the setHeaderRoute will cause overlap and requests will be directed to the incorrect target.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
Currently,
setHeaderRoute
adds a new route in the virtualService but only allows configuring a match withheaderName
andheaderValue
. It would be interesting to also allow configuring themethod
andpath
settings similar tosetMirrorRoute
.Use Cases
Situations where the environment uses a common FQDN for more than one workload
api.foo.local
and routing is done using path/v1/bar, /v1/foo
. With the current scenario, activating thesetHeaderRoute
will cause overlap and requests will be directed to the incorrect target.Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: