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
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 linkerd?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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 linkerd?
Beta Was this translation helpful? Give feedback.
All reactions