Create new documentation based on user stories

[luxas]

Instead of having a lot of documentation in one reference page, have multiple pages discoverable directly from the getting started guide with various user stories. Pages with docs we should create are below:

• Running e2e tests against kubeadm clusters
  • Assignee: @timothysc, @liztio
• Customizing control plane arguments with kubeadm - Target 1.11
  • Assignee: @neolit123; PR kubeadm-setup: add page about control plane flags website#9067
• Securing your kubeadm cluster further - Target 1.12
  • Assignee: @luxas
• Configuring the kubelets in your cluster and using an other CRI runtime than docker - Target 1.11
  • Packaging kubeadm & running on non-system systems
    • Assignee: @luxas
• Customizing the proxy and dns addons installed by default - Target 1.12
  • Assignee: @neolit123
• Testing prerelease versions of Kubernetes with kubeadm (not main website, but kubeadm repo)
  • Assignee: @fabriziopandini; PR testing-pre-releases #890
• Upgrading your v1alpha1 Configuration file to v1alpha2 - Target 1.11
  • Assignee: @luxas
• kubelet-kubeadm integration since 1.11:
  • Assignee: @neolit123; PR Kubeadm kubelet integration doc website#9652

cc @timothysc @neolit123 @fabriziopandini @liztio @chuckha @detiber

[neolit123]

Customizing control plane arguments with kubeadm

i can try taking a stab at this.

[neolit123]

WIP for Customizing control plane arguments with kubeadm:
https://docs.google.com/document/d/1KuDHonX_5-tZqTO17muBtDOFQKLmMN0K1eXh-q24Ny8/edit?usp=sharing

[neolit123]

https://docs.google.com/document/d/1KuDHonX_5-tZqTO17muBtDOFQKLmMN0K1eXh-q24Ny8/edit?usp=sharing

so in terms of adding more to that page:

1. i was thinking of inlining a etcd yaml config example. linking to godocs for a reference:
   https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#Etcd
   also expanding on:

	// ExtraArgs are extra arguments provided to the etcd binary
	// when run inside a static pod.
	ExtraArgs map[string]string `json:"extraArgs,omitempty"

https://coreos.com/etcd/docs/latest/v2/configuration.html

[timothysc]

/assign @liztio

[neolit123]

should we change the milestone and labels for this?
@timothysc

from the meeting (06.06.2018):

kubeadm user stories: #849
[Lubomir] should we do this now or in the next few weeks?
[Jennifer] docs folks don’t have time for this in 1.11 right now. Best to do this anytime after 1.11 is out the door.

[timothysc]

We can leave this one open for now just for todo list, but pr in bulk on the copy-edit issues.

[Bradamant3]

Question about the last item, Upgrading your v1alpha1 Configuration file to v1alpha2 (I realize it's unassigned still, but it's targeted for 1.11): per conversation in sig-docs about documenting alpha features, should this content go into kubernetes/kubeadm instead of the main docs?

[neolit123]

shouldn't Packaging kubeadm & running on non-system systems be about non-systemd systems?

[timothysc]

Closing this one as we addressed some/most and we'll open new issues for 1.12.