-
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
Drain pods created from ReplicaSets in 'kubectl drain' #23689
Drain pods created from ReplicaSets in 'kubectl drain' #23689
Conversation
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
2 similar comments
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Having some trouble getting the tests working, PTAL and let me know if I'm missing something |
@k8s-bot ok to test |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
@k8s-bot ok to test |
@ixdy k8s-bot isn't responding to me. Can you add me to the admin list? |
GCE e2e build/test passed for commit 36fc6836797ac3bf5dbe3a7de1c68f420c80f77f. |
Hm, of course that triggered it. I noticed that in the config your name is listed as JanetKuo, so maybe it cares about capitalization? I'll change it. |
@maclof can you please update the docs to match? |
@ixdy The Jenkins unit/integration link is giving me 404 (after redirects). Any idea what's going on? |
I've updated docs in this commit: maclof@cf5bc68 but for some reason it isn't showing up in this PR? o.o |
@maclof also looks like the test failed.
|
@@ -396,6 +436,8 @@ func TestDrain(t *testing.T) { | |||
return &http.Response{StatusCode: 200, Body: objBody(testapi.Extensions.Codec(), &ds)}, nil | |||
case m.isFor("GET", "/namespaces/default/jobs/job"): | |||
return &http.Response{StatusCode: 200, Body: objBody(testapi.Extensions.Codec(), &job)}, nil | |||
case m.isFor("GET", "/namespaces/default/replicasets/rs"): | |||
return &http.Response{StatusCode: 200, Body: objBody(testapi.Extensions.Codec(), &test.rcs[0])}, nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you want &test.replicaSets[0]
@mml thanks, no idea how I missed that one. |
cf5bc68
to
97267e3
Compare
GCE e2e build/test failed for commit 10c05ccb2ec13761fbb7931dfc812437c055be04. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test passed for commit f2fd9aee08fb9f7a331157311b0e5ed822d1e0f7. |
f2fd9ae
to
fdf4098
Compare
GCE e2e build/test passed for commit fdf4098. |
@mml I rebased this morning, but something weird seems to be going on with the GCE Node e2e? |
@mml |
k8s-bot test this issue: #24297 |
GCE e2e build/test passed for commit fdf4098. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit fdf4098. |
Automatic merge from submit-queue |
Is it possible to get this cherry-picked into This seems like a pretty big oversight, and pretty much makes using drain impossible in 1.2 since many things have now moved to Deployments/ReplicaSets by default. Ex: heapster/eventer in upstream, but I'm sure other users are now using Deployments for their own things. Now we basically need to choose between having drain, or using deployments, which is quite unfortunate. CC @mml |
…89-upstream-release-1.2 Drain pods created from ReplicaSets in 'kubectl drain'
Commit found in the "release-1.2" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…ck-of-#23689-upstream-release-1.2 Drain pods created from ReplicaSets in 'kubectl drain'
…ck-of-#23689-upstream-release-1.2 Drain pods created from ReplicaSets in 'kubectl drain'
Refer to my issue here: #23531