Make activeService optional for a blueGreen rollout #3162
ibuiltthis
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using Istio and routing traffic based on labels . This is useful as I can ensure that all pods in preview communicate together and all pods in active communicate together. I am able to set the labels on the pods during the rollout using the ativeMetadata and previewMetadata config below.
However I am still required to nominate a service for the activeService even though I don't want argo rollouts to modify the service in any way. I have created a workaround by creating a second service that isn't used but this messy and confusing. Is there a reason that argo rollout must modify an activeService during a rollout?
Beta Was this translation helpful? Give feedback.
All reactions