-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Adding an e2e test for deployment #14594
Adding an e2e test for deployment #14594
Conversation
cc @ixdy to look at jenkins changes |
Unit, integration and GCE e2e build/test failed for commit 41b41937e1dc8a50fb96d32798ec0ba6c8f7ac1c. |
41b4193
to
d61ed52
Compare
Labelling this PR as size/L |
Unit, integration and GCE e2e test build/test passed for commit d61ed52. |
LGTM |
Adding LGTM tag as per comment above |
@k8s-oncall this is for v1.1 - Can I have a merge, plz? |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Unit, integration and GCE e2e test build/test passed for commit d61ed52. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
…#14594-upstream-release-1.1 Auto commit by PR queue bot
…y-pick-of-#14594-upstream-release-1.1 Auto commit by PR queue bot
…y-pick-of-#14594-upstream-release-1.1 Auto commit by PR queue bot
Ref #1743
This a basic test that just tests the end state (old pods should have vanished and new pods should be scaled to the desired replicas).
We are not testing that we dont break maxSurge and maxAvailability during the update.
Will add tests for that when we have updated deployment controller to raise events each time it scales up or down (being done by #14130)
cc @ghodss @ironcladlou