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
It would be interesting to document how API versioning could be affected by canary deployment.
When performing a canary deployment, you will have a minimum of one pair of each component:
2 gloo deployments
2 gateway deployment
2 proxy resource
2 gateway proxy
But only one custom resources (i.e. VirtualService, RT, AuthConfig, ...) as you had it before running the deployment.
What would happen if the new release brings a change in the CRDs? How do the canary deployments (old version and new version) behave? can there be a possible conflict?
thank you
The text was updated successfully, but these errors were encountered:
From 1.9.0 we can have canary deployments.
It would be interesting to document how API versioning could be affected by canary deployment.
When performing a canary deployment, you will have a minimum of one pair of each component:
But only one custom resources (i.e. VirtualService, RT, AuthConfig, ...) as you had it before running the deployment.
What would happen if the new release brings a change in the CRDs? How do the canary deployments (old version and new version) behave? can there be a possible conflict?
thank you
The text was updated successfully, but these errors were encountered: