-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-apply old canary selector label to canary service is rollout is aborted #2781
Comments
Is this just a missing condition of this #2540 |
@zachaller probably? This is a rollout not using any service mesh. Just number of pods to control %. |
@zachaller I started looking into this, but it looks like the issue is higher up - it exits early if there is no TrafficRouting Reconcilers found. I think the the solution would be in modifying the reconcileStableAndCanaryService: https://github.com/zachaller/argo-rollouts/blob/820f516bd1aa0b003e9ebc956528053d8f69e8a8/rollout/service.go#L256 see related pr |
Signed-off-by: mitchell amihod <[email protected]>
Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 * remove redundant block of code Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 * remove redundant block of code Signed-off-by: mitchell amihod <[email protected]>
…ting is used fixes argoproj#2781 * remove redundant block of code Signed-off-by: mitchell amihod <[email protected]>
… on rollout abort argoproj#2781 (argoproj#2818)" This reverts commit 3c5ac36. Signed-off-by: Alexandre Gaudreault <[email protected]>
… on rollout abort argoproj#2781 (argoproj#2818)" This reverts commit 3c5ac36. Signed-off-by: Zach Aller <[email protected]>
… on rollout abort argoproj#2781 (argoproj#2818)" This reverts commit 3c5ac36. Signed-off-by: Zach Aller <[email protected]>
(Not sure if this is a bug or enhancement)is bug.Summary
When AR manages a canary service, it manages the selectors to ensure the canary service points at the canary pods.
Once a rollout is fully promoted, the service continues to point at the stable pods. So if you have something pointing at the service, it continues to operate.
If you abort a rollout, the canary service selector label is not rolled back as well, leading to a 'dead'; service. I would like to change this behaviour that when you rollback, the selector should be restored as well.
Use Cases
Whats interesting about how this works is that is allows you to rig up a fully canary path for your services assuming a certain naming convention.
eg: canary.ingress.example.com > canary-service.ns.svc.local > another-service.ns.svc.local
You can then have a trigger that whenever a request comes in to host
canary.ingress.example.com
that you hit up all thecanary-*
service endpoints internally. If other services are running a canary at the moment, great! if not, also great, since everything will respond on that code path.Wanted to check if this is desired before doing the work.
Let me know if this needs more details.
[edit] Since this seems to be a bug (#2540) a few more details
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: