Adding label:do-not-merge because PR changes docs prohibited to auto merge
See http://kubernetes.io/editdocs/ for information about editing docs

@eparis Is there any way to convince the bot we may touch this (for the last time)?

@luxas Don't worry about the label. We can just merge this by hand.

@luxas We need to add redirectors to the new location in kubernetes.github.io, also.

I don't think we should maintain it in two different places.
All scripts in kubernetes.github.io should also be deleted (of course, the commits that have been made should be ported over to kube-deploy), and the docs guide should describe how to use/setup the kube-deploy deployment. The source of truth should be in kube-deploy.

@bgrant0607 Does this sound like a good idea?

I think we should maintain the getting started guide (e.g. just the doc) in kubernets.github.io. That's the location where it is most user visible and discoverable. We can point to that documentation from kube-deploy.

@k8s-bot e2e test this please github issue: #IGNORE

@mikedanese Want to proceed with this one as the kube-deploy PR is in?

@k8s-bot unit test this please github issue: #IGNORE

GCE e2e build/test passed for commit dca3bd5.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Adding label:do-not-merge because PR changes docs prohibited to auto merge
See http://kubernetes.io/editdocs/ for information about editing docs

@mikedanese or @k8s-oncall
Mind a manual merge for this as the bot doesn't like the fact we're touching the old docs?