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 subset traffic splitting support virtualservice with a single destinationrule. In the case of a virtual with multiple destination/subset, argo rollout could support one destination. Is there a workaround for this except break the virtualservice? The VS is like this:
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
-
Currently subset traffic splitting support virtualservice with a single destinationrule. In the case of a virtual with multiple destination/subset, argo rollout could support one destination. Is there a workaround for this except break the virtualservice? The VS is like this:
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
name: cms-test-gateway-vs
namespace: eu1-test
spec:
http:
prefix: /admin/cmstest/
name: cms-test-admin-routes
route:
host: cms-test-service
port:
number: 8895
subset: admin
prefix: /cmstest/
name: cms-test-default-routes
route:
host: cms-test-service
port:
number: 8895
subset: public
Beta Was this translation helpful? Give feedback.
All reactions