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.

Are you sure that it works? I tried to use your code and it still has a problem with selecting the concrete service outside of the default namespace:

$ ./_output/local/bin/linux/amd64/kubectl create namespace kopytko                                                                                                                                       
namespace "kopytko" created
$ ./_output/local/bin/linux/amd64/kubectl --namespace=kopytko create -f ~/playground/k8s/downward-old.yaml                                                                                                 
pod "kubernetes-downwardapi-volume-example" created
$ ./_output/local/bin/linux/amd64/kubectl --namespace=kopytko create -f ~/playground/k8s/service.yaml 
service "my-service" created
$ ./_output/local/bin/linux/amd64/kubectl get --all-namespaces services                                                                                                                                  
NAMESPACE   NAME         CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
default     kubernetes   10.0.0.1     <none>        443/TCP   48m
kopytko     my-service   10.0.0.68    <none>        80/TCP    4m
$ ./_output/local/bin/linux/amd64/kubectl get --all-namespaces services my-service
error: namespace may not be empty when retrieving a resource by name

And the piece of code which shows this error seems to be untouched here.

@nhlfr : my PR was for describe not get - "kubectl describe --all-namespaces services" (and not "kubectl get --all-namespaces services")

Um, sorry. Then LGTM

Hey Dims!. I think it should be 'kubectl describe services --all-namespaces' in your doc patch instead of 'kubectl get services --all-namespaces'.

@rthallisey oops! thanks. fixed.

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.

@k8s-bot ok to test

Apologies, I missed this pr right when we went into code slush for 1.3. Looks good, will add tag when tests are green.

GCE e2e build/test passed for commit 1c8b8cf21ea1793729860db1abf88c7fa9dd81b5.

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

GCE e2e build/test passed for commit de7416d7e3442497144e07a66b5b6f13c865ab4c.

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

cc @johndmulhausen do you know why mergebot is blocking on docs?

@k8s-oncall Any tips on how i can unblock this PR?

cc @david-mcmahon @lavalamp Will this have to be manually merged?

Hopefully @johndmulhausen can clarify. AFAIK most docs are on the docs site, but I'm not sure why the bot still warns/blocks on some of the docs in the tree.

@johndmulhausen @eparis : i've submitted another PR for the bot to whitelist the cheatsheet.md - kubernetes-retired/contrib#1332

I do not believe that kubectl-cheatsheet.md belongs in the repo at all. This is not auto-generated and thus is an actual user doc which belongs in kubernetes.github.io. @erictune

GCE e2e build/test passed for commit c879e69.

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

@k8s-bot please test this: #IGNORE

@eparis I agree. Filed kubernetes/website#796

@erictune @eparis thanks!

@k8s-bot test this please, issue: #IGNORE

GCE e2e build/test passed for commit c879e69.

• 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 c879e69.

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

Automatic merge from submit-queue