Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test".
(Note: "add to whitelist" is no longer supported. Please update configurations in kubernetes/test-infra/jenkins/job-configs/kubernetes-jenkins-pull instead.)

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.

You'll need to generate docs and such: hack/update-all.sh. If that fails, you can try update-generated-docs.sh, but I'm not certain that will get everything.

you should also add "fixes kubernetes/website#501" to the PR message.

@andreykurilin PR needs rebase

Sorry, github didn't send a notification when you re-pushed. Tag me when you update. Also, double check that link.

@deads2k, PR is rebased

The link: http://kubernetes.io/images/docs/kubectl_drain.svg still 404's for me. Should I be seeing something?

@deads2k I have separate PR to kubernetes.github.io and it doesn't merged yet. Also it hasn't reviews.

see kubernetes/website#521

Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test".
(Note: "add to whitelist" is no longer supported. Please update configurations in kubernetes/test-infra/jenkins/job-configs/kubernetes-jenkins-pull instead.)

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.

Alright, the link works now. Run the hack/update-all.sh again. #25736 (comment)

@bgrant0607 @kubernetes/kubectl Any guidance on providing deep links from CLI help? I've seen products decide in both directions and neither is clearly better in my mind.

@deads2k It looks like I do not need to run any updaters. See 1d25410

We need to make a consistent decision here for #25810 as well. Adding SVG links to what are effectively man pages is not the end of the world, but it's an unusual step. Links to help from man pages makes sense, but in our case the help we would be linking to is exactly what is in the man page.

@smarterclayton I agree consistency is important.

We need to think holistically about what we'd like to do with kubectl help.

We're collecting ideas here:
https://github.com/kubernetes/community/wiki/Roadmap:-kubectl#improve-help--error-messages--output

Among other things, we'll probably need to start to embed formatting. I'm thinking we should write the text in a form (markdown?) that can be post-processed for the various ways in which the text would be published/viewed.

I don't have particular concerns about the image links.

Fine with that as well.

I don't have particular concerns about the image links.

Alright, if I get the choice I'd prefer to include the link. Rebase once more for merge?

@deads2k done

GCE e2e build/test passed for commit c7f7c0a6f58754c47fe3b160eae0ba04cc9bc87b.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

GCE e2e build/test passed for commit 21b218c.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

GCE e2e build/test passed for commit 21b218c.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from submit-queue