-
Notifications
You must be signed in to change notification settings - Fork 67
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
VerifyDeployments does not verify rolling updates are completed #119
Comments
Hit the same bug today. It's a shame that this plugin doesn't receive more love from Google. 3 years since initial release and we still have to rely on our own hackish Jenkins scripts to manage deployments on GCP :( |
I have actually looked into this and it looks like it could be very easy to fix. I have two patches almost ready, first uses |
@olamy are you the sole maintainer of this plugin now? If yes, I'm not sure if you can answer my old question above, but we've been running patched version of the plugin for a year now and I can provide a patch to this issue if you are interested. |
@ViliusS I would not qualify myself as a sole maintainer but doing some chore maintenance. |
Done. |
When using a deployment with a rolling update strategy, the verifyDeployments flag will not verify that all replicas have been updated. Instead when it sees that the minimum number of replicas is correct (which can happen multiple times during a rollout before all replicas have been updated) it will mark the deployment as complete.
Perhaps it would be possible to use
kubectl rollout status
to verify the deployment is complete?The text was updated successfully, but these errors were encountered: