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
The current Istio canary strategy allows specifying only a single VirtualService. This is not sufficient for advanced setups where the routes are divided into multiple VirtualService resources - like north-south route VS, east-west route VS, and delegate VS.
Use Cases
In Salesforce, we use multiple VirtualService resources linked to a single service. Each service port also gets its own specialized delegate VirtualService. The blue/green route for our use-case would actually stay in the multiple delegates. When the Service undergoes a blue/green rollout, we want to update all the linked VirutalService resources.
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
The current Istio canary strategy allows specifying only a single
VirtualService
. This is not sufficient for advanced setups where the routes are divided into multipleVirtualService
resources - like north-south route VS, east-west route VS, and delegate VS.Use Cases
In Salesforce, we use multiple
VirtualService
resources linked to a single service. Each service port also gets its own specialized delegateVirtualService
. The blue/green route for our use-case would actually stay in the multiple delegates. When the Service undergoes a blue/green rollout, we want to update all the linkedVirutalService
resources.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: