Fix update documentation reference to doc location

[samos123]

It seems docs were moved from kubernetes repo and now
live in the website repo. I've updated the prequisite to
reflect this change.

---

This change is

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[samos123]

I signed it!

[googlebot]

CLAs look good, thanks!

[janetkuo]

We don't need the whole repo but just the files in https://github.com/kubernetes/kubernetes.github.io/tree/master/docs/user-guide/update-demo

cc @kubernetes/docs should we link to master or to a specific branch such as https://github.com/kubernetes/kubernetes.github.io/tree/release-1.4/docs/user-guide/update-demo

[samos123]

Agree on linking to specific branch. Will fix that in next patch.

afaik there is no easy way to just copy the update-demo folder unless we upload it as an independent archive somewhere. Currently the demo requires you to run kubectl proxy on a whole directory so it's not as easy as just linking to 2 files.

For the kubectl create commands we can use kubectl create -f http://location-to-yaml-file.yaml but let's do that as separate patch.

Note though: This patch is only about fixing broken stuff not about improving the update-demo docs in general. I don't want it to get bloated. Currently update docs are broken because doc location moved from kubernetes repo to kubernetes.github.io repo and this should get fixed first.

[janetkuo]

Since we're not using ./cluster/kube-up.sh in this doc anymore we should remove ./cluster/kube-down.sh in L87 as well

[samos123]

Agree. Will fix in next patch.

[janetkuo]

Thanks for submitting the fix! I have a few comments.

[samos123]

I've submitted a new patch that solves the issues you pointed out in the comments.

[samos123]

@janetkuo it looks like we will also need to create a release-1.3 branch as there is none currently but many docs refer to the release-1.3 branch

[janetkuo]

it looks like we will also need to create a release-1.3 branch as there is none currently but many docs refer to the release-1.3 branch

We recently deleted release-1.3 branch, and it breaks these {{page.docsbranch}} links :( @kubernetes/docs
Thanks for reporting this!

[janetkuo]

The change LGTM but the link needs to be reviewed by the tech writers

[devin-donnelly]

I'm not sure what this include is supposed to accomplish, but we're not hosting versioned docs or anything. We never actually were; GitHub pages doesn't let you host multiple branches. Everything was being cloned to a dummy organization.

You can probably go ahead and take it out.

[samos123]

@devin-donnelly the kubernetes repo no longer contains the user-guide docs. As a result cd kubernetes is no longer accurate as the rest of the update demo documentation assumes the user docs are under the docs directory. So this patch(include) is fixing the issue that that current assumptions are incorrect.

@devin-donnelly Now what do you specifically want taken out? Only the -b {{page.docsbranch}} part? Or the whole git clone statement?

Please be as specific as possible. I usually do not write docs and just happened to stumble upon an issue with the docs which I fixed in this patch..

[jeffmendoza]

I'd prefer we just change to kubectl create -f https://github...

[samos123]

@jeffmendoza I originally thought about doing that also and went with that first, but then noticed that we also have a command to run kubectl proxy --www=docs/user-guide/update-demo/local/ &. So you also need to update that command. Hence I think it's better to fix only the assumption and keep the guide as is.

[devin-donnelly]

I'd rather go with @jeffmendoza 's suggestion.

[samos123]

@devin-donnelly I too prefer jeff's suggestions and would happily update the patch to accommodate improvements, but currently @jeffmendoza has not yet provided an answer to the issue with his suggestion.

Please provide a way to run kubectl proxy without cloning the repo. If there is a way to run kubectl proxy without cloning the repo, then we can utilize jeff's suggestion, if there is no such way then I suggest to use this patch as is and clone the user docs repo in the assumption step.

[jeffmendoza]

Ah, yes. The proxy command requires the files to be local.

LGTM Thanks!