add en pages

2020-05-30 15:10:23 -04:00
parent 1502e0281d
commit ecc27bbbe7
347 changed files with 2900 additions and 2537 deletions
@@ -3,10 +3,10 @@ reviewers:
 - luxas
 - jbeda
 title: Implementation details
-content_template: templates/concept
+content_type: concept
 weight: 100
 ---
-{{% capture overview %}}
+<!-- overview -->

 {{< feature-state for_k8s_version="v1.10" state="stable" >}}

@@ -14,9 +14,9 @@ weight: 100
 However, it might not be obvious _how_ kubeadm does that.

 This document provides additional details on what happen under the hood, with the aim of sharing knowledge on Kubernetes cluster best practices.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 ## Core design principles

 The cluster that `kubeadm init` and `kubeadm join` set up should be:
@@ -531,4 +531,4 @@ Please note that:

 1. To make dynamic kubelet configuration work, flag `--dynamic-config-dir=/var/lib/kubelet/config/dynamic` should be specified in `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf`

-{{% /capture %}}
+
@@ -3,10 +3,10 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm config
-content_template: templates/concept
+content_type: concept
 weight: 50
 ---
-{{% capture overview %}}
+<!-- overview -->
 During `kubeadm init`, kubeadm uploads the `ClusterConfiguration` object to your cluster
 in a ConfigMap called `kubeadm-config` in the `kube-system` namespace. This configuration is then read during
 `kubeadm join`, `kubeadm reset` and `kubeadm upgrade`. To view this ConfigMap call `kubeadm config view`.
@@ -19,9 +19,9 @@ In Kubernetes v1.13.0 and later to list/pull kube-dns images instead of the Core
 the `--config` method described [here](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon)
 has to be used.

-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 ## kubeadm config view {#cmd-config-view}
 {{< include "generated/kubeadm_config_view.md" >}}

@@ -40,8 +40,9 @@ has to be used.
 ## kubeadm config images pull {#cmd-config-images-pull}
 {{< include "generated/kubeadm_config_images_pull.md" >}}

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) to upgrade a Kubernetes cluster to a newer version
-{{% /capture %}}
+
@@ -3,14 +3,14 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm init
-content_template: templates/concept
+content_type: concept
 weight: 20
 ---
-{{% capture overview %}}
+<!-- overview -->
 This command initializes a Kubernetes control-plane node.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->

 {{< include "generated/kubeadm_init.md" >}}

@@ -255,12 +255,13 @@ it does not allow the root CA hash to be validated with
 `--discovery-token-ca-cert-hash` (since it's not generated when the nodes are
 provisioned). For details, see the [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm init phase](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/) to understand more about
 `kubeadm init` phases
 * [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster
 * [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) to upgrade a Kubernetes cluster to a newer version
 * [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/) to revert any changes made to this host by `kubeadm init` or `kubeadm join`
-{{% /capture %}}
+
@@ -3,14 +3,14 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm join
-content_template: templates/concept
+content_type: concept
 weight: 30
 ---
-{{% capture overview %}}
+<!-- overview -->
 This command initializes a Kubernetes worker node and joins it to the cluster.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 {{< include "generated/kubeadm_join.md" >}}

 ### The join workflow {#join-workflow}
@@ -276,10 +276,11 @@ kubeadm config print join-defaults

 For details on individual fields in `JoinConfiguration` see [the godoc](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#JoinConfiguration).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes control-plane node
 * [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token/) to manage tokens for `kubeadm join`
 * [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/) to revert any changes made to this host by `kubeadm init` or `kubeadm join`
-{{% /capture %}}
+
@@ -3,14 +3,14 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm reset
-content_template: templates/concept
+content_type: concept
 weight: 60
 ---
-{{% capture overview %}}
+<!-- overview -->
 Performs a best effort revert of changes made by `kubeadm init` or `kubeadm join`.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 {{< include "generated/kubeadm_reset.md" >}}

 ### Reset workflow {#reset-workflow}
@@ -35,9 +35,10 @@ etcdctl del "" --prefix
 ```

 See the [etcd documentation](https://github.com/coreos/etcd/tree/master/etcdctl) for more information.
-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes control-plane node
 * [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster
-{{% /capture %}}
+
@@ -3,10 +3,10 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm token
-content_template: templates/concept
+content_type: concept
 weight: 70
 ---
-{{% capture overview %}}
+<!-- overview -->

 Bootstrap tokens are used for establishing bidirectional trust between a node joining
 the cluster and a control-plane node, as described in [authenticating with bootstrap tokens](/docs/reference/access-authn-authz/bootstrap-tokens/).
@@ -14,9 +14,9 @@ the cluster and a control-plane node, as described in [authenticating with boots
 `kubeadm init` creates an initial token with a 24-hour TTL. The following commands allow you to manage
 such a token and also to create and manage new ones.

-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 ## kubeadm token create {#cmd-token-create}
 {{< include "generated/kubeadm_token_create.md" >}}

@@ -28,8 +28,9 @@ such a token and also to create and manage new ones.

 ## kubeadm token list {#cmd-token-list}
 {{< include "generated/kubeadm_token_list.md" >}}
-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster
-{{% /capture %}}
+
@@ -3,15 +3,15 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm upgrade
-content_template: templates/concept
+content_type: concept
 weight: 40
 ---
-{{% capture overview %}}
+<!-- overview -->
 `kubeadm upgrade` is a user-friendly command that wraps complex upgrading logic
 behind one command, with support for both planning an upgrade and actually performing it.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->

 ## kubeadm upgrade guidance

@@ -46,8 +46,9 @@ reports of unexpected results.
 ## kubeadm upgrade node {#cmd-upgrade-node}
 {{< include "generated/kubeadm_upgrade_node.md" >}}

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * [kubeadm config](/docs/reference/setup-tools/kubeadm/kubeadm-config/) if you initialized your cluster using kubeadm v1.7.x or lower, to configure your cluster for `kubeadm upgrade`
-{{% /capture %}}
+
@@ -3,13 +3,13 @@ reviewers:
 - luxas
 - jbeda
 title: kubeadm version
-content_template: templates/concept
+content_type: concept
 weight: 80
 ---
-{{% capture overview %}}
+<!-- overview -->
 This command prints the version of kubeadm.
-{{% /capture %}}

-{{% capture body %}}
+
+<!-- body -->
 {{< include "generated/kubeadm_version.md" >}}
-{{% /capture %}}
+