Deploy preview ready!

Built with commit c22066e

https://deploy-preview-6642--kubernetes-io-master-staging.netlify.com

/assign @apelisse

@mengqiy The master branch is fine for this PR.

@steveperry-53 Are you going to use this script to update the imported docs for 1.9 release? Or if you want to keep the PRs that are manually crafted i.e. #6614 #6619 #6628?

@mengqiy I was thinking I would use this script, and make a new PR to replace #6614, #6619, and #6628. Does that sound reasonable? I'm running the script to do that right now.

SG. I guess you only need to run it once after you populate the config.yaml. IOW, I guess you will only need 1 PR.

One concern: if this PR is merged into master branch, will you guys do fast-forward (or something else) to make 1.9 branch have this program as well?

#6614, #6619, and #6628 can be used as reference to check if everything looks correct.

@mengqiy At this point, we should wait until after the 1.9 release to merge this PR. On Wednesday, 12/13, the plan is to merge kubernetes/website:release-1.9 into kubernetes/website:master. After that, we can merge this PR into master. In the meantime, I have cloned mengqiy/website:play, and am running the script to generate docs. I'll submit those generated docs in a PR to kubernetes/website:release-1.9. I should be able to do that tonight.

See #6658. Notice that in some topics, the synopsis appears twice. Example: kubectl options. For the 1.9 release, I'll just fix these manually.

Thanks for you feedback.
Can you provide me the config.yaml?
So I can reproduce it and check why it happens. And then fix it.

Thanks! I will dig it tomorrow or next Monday.

See #6658. Notice that in some topics, the synopsis appears twice.

Do you mean it appears once in synopsis and once in Example?

Example: kubectl options.

The link you gave actually links to kubefed options.

After digging this a bit, I found it's not the problem of this script. The generated doc looks the same. So if the format is wrong, then the issue is in the federation repo.

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@mengqiy Thanks for checking into this. My mistake on the link text; I meant it to say kubefed options. Are you ready for me to merge this PR now?

These are the files that had the double synopsis:

• kubectl.md
• kubefed.md
• kubefed_init.md
• kubefed_join.md
• kubefed_options.md
• kubefed_unjoin.md
• kubefed_version.md

The synopsis appeared once just below the title and once just below the Synopsis heading. This commit
shows the files where I removed the synopsis that appeared under the title.

When I get a chance, I'll take a look at the federation scripts, and see about getting those fixed.

Before I did the removal, the pages looked like this:

kubefed init

Initialize a federation control plane

Synopsis

Init initializes a federation control plane.

kubefed init
Initialize a federation control plane
Synopsis
Init initializes a federation control plane.

kubefed join
Join a cluster to a federation
Synopsis
Join adds a cluster to a federation.

The wording are not the same, so I think they not duplicate but they are generated from different origins with similar meaning.

@mengqiy Should I go ahead and merge this PR?

Please go ahead and merge it. :)
It should not have any risk.