The vagrant guide was dropped from main repo, but was not moved into the docs.
This brings it in, updates formatting for the jekyll site and adds menu links.
Also:
* Cleanup pasted yaml and instead embed file
* Clarify Service test sections by including busybox exec commands as part of the preformatted section
Of course AWS does not "run on CoreOS", so under "Running Kubernetes" the title should not be "AWS on CoreOS".
This is highly irritating when browsing the docs the first time.
The title should either be: "Kubernetes with AWS provider on CoreOS", or "CoreOS on AWS".
I picked the latter form, and fixed a couple of non-optimal titles in this fashion.
I also changed "Vagrant or VMware" to "CoreOS on Vagrant", because the article is mostly about CoreOS, including other platforms (btw. VMWare is just a Vagrant provider in this context).
Also note that there is a little navigation bug because the article "/docs/getting-started-guides/coreos/" is linked twice: when clicked, the other link is selected too in the navigation (under certain circumstances). It may make sense to split the article in 2 files: one about Vagrant only, one about AWS and GCE.
I removed the "libvirt or KVM" link, because the article is already linked under "On Bare Metal", where it fits better. It has nothing special to do with libvirt and KVM and doesn't mention any of both.
A newline between `[]` and `()` caused markdown rendering issues when parsed with `kramdown` (Jekyll's markdown parser) strangely enough this was not present on github.com but only on kubernetes.io.
This change moves the newline between _in_ and `rkt.go` to preserve the line length somewhat.
Split the descriptions for LivenessProbe and ReadinessProbe into two sections - one explaining the pure technical details and the other explaining how/why you'd use them.
One could be bitten by having unexpected newline characters in base64 encoded secrets (reference: https://github.com/kubernetes/kubernetes/issues/23404).
Calling `echo -n` will omit the trailing newline character.
`
The echo utility writes any specified operands, separated by single blank (` ') characters and followed by
a newline (`\n') character, to the standard output.
The following option is available:
-n Do not print the trailing newline character. This may also be achieved by appending `\c' to the end
of the string, as is done by iBCS2 compatible systems. Note that this option as well as the effect
of `\c' are implementation-defined in IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
Applications aiming for maximum portability are strongly encouraged to use printf(1) to suppress the
newline character.
`
DrDePhobia
paulzim
Pavel Strashkin
AlginMaduro
Terrence Ryan
johndmulhausen
Jeremy Wilken
Rick
Michael Grosser
Brian Grant
Aaron Crickenberger
Phillip Wittrock
Khalid Dermoumi
Andrey Kurilin
Pau Ruŀlan
Karl Herler
Brian Grant
Elson O Rodriguez
Sebastian
Janet Kuo
Carson A
Robert Bailey
Sam Ghods
Josh Hoak
Joonathan Mägi