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
{{ message }}
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
We have the follow situation:
Our platform is multi pods services applications. View Image
We need to split traffic using app version (ex app label). When a user connect to the ingress, he is routed in version 1 or version2 on the first app based a criterial (header, %, etc etc)
From here, if user matches V1, the traffic is routed on all app version V1 inside kubernetes. (He use always v1 for all other Microservices).
In istio I use sourcelabel to achieve this. There is a easy way to implement the same routing with Nginx Mesh?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
We have the follow situation:
Our platform is multi pods services applications. View Image
We need to split traffic using app version (ex app label). When a user connect to the ingress, he is routed in version 1 or version2 on the first app based a criterial (header, %, etc etc)
From here, if user matches V1, the traffic is routed on all app version V1 inside kubernetes. (He use always v1 for all other Microservices).
In istio I use sourcelabel to achieve this. There is a easy way to implement the same routing with Nginx Mesh?
The text was updated successfully, but these errors were encountered: