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, if a virtual service has more than one route you must include all of its routes within the rollout spec.
It would be beneficial to have argo rollouts change all the weights of all routes if no routes are specified.
Use Cases
If you have a virtual service with many routes you must keep your rollouts spec in sync with the routes spec, which could be challenging and prone to configuration errors.
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, if a virtual service has more than one route you must include all of its routes within the rollout spec.
It would be beneficial to have argo rollouts change all the weights of all routes if no routes are specified.
Use Cases
If you have a virtual service with many routes you must keep your rollouts spec in sync with the routes spec, which could be challenging and prone to configuration errors.
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: