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
Argo Rollouts removes any subset level DestinationRoutes in a VirtualService that it not modifying during a Canary Rollout.
I have a VirtualService where I want to route a certain percentage to a newer system while maintaining a canary release for a legacy service.
In the following case below, Argo Rollouts will remove the DestinationRoutes with host rollout-alpha-example following a rollout. Ideally, I'd also want the flexibility to define a maxWeight in which Rollouts would setWeight up to the maxWeight for a HTTP DestinationRoute.
dnguy078
changed the title
Istio
Istio Subset-level traffic splitting remove other DestinationRoutes not managed by Rollouts
Oct 25, 2023
dnguy078
changed the title
Istio Subset-level traffic splitting remove other DestinationRoutes not managed by Rollouts
Istio Subset-level traffic splitting removes other DestinationRoutes
Oct 25, 2023
Checklist:
Describe the bug
rollout-alpha-example
following a rollout. Ideally, I'd also want the flexibility to define a maxWeight in which Rollouts would setWeight up to the maxWeight for a HTTP DestinationRoute.Rollout.yaml
To Reproduce
kubectl argo rollouts set image rollout-example "*=argoproj/rollouts-demo:yellow"
rollout-alpha-example
Expected behavior
spec.strategy.trafficRouting.istio.destinationRule.name
Screenshots
Version
v1.6.0
Logs
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: