add en pages

content/en/docs/reference/command-line-tools-reference/cloud-controller-manager.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 30
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 
 The Cloud controller manager is a daemon that embeds
@@ -14,9 +15,10 @@ the cloud specific control loops shipped with Kubernetes.
 cloud-controller-manager [flags]
 ```
 
-{{% /capture %}}
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -534,5 +536,5 @@ cloud-controller-manager [flags]
 
 
 
-{{% /capture %}}
+
 

content/en/docs/reference/command-line-tools-reference/feature-gates.md

@@ -1,17 +1,17 @@
 ---
 weight: 10
 title: Feature Gates
-content_template: templates/concept
+content_type: concept
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 This page contains an overview of the various feature gates an administrator
 can specify on different Kubernetes components.
 
 See [feature stages](#feature-stages) for an explanation of the stages for a feature.
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 ## Overview
 
 Feature gates are a set of key=value pairs that describe Kubernetes features.
@@ -511,8 +511,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `WinDSR`: Allows kube-proxy to create DSR loadbalancers for Windows.
 - `WinOverlay`: Allows kube-proxy to run in overlay mode for Windows.
 
-{{% /capture %}}
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * The [deprecation policy](/docs/reference/using-api/deprecation-policy/) for Kubernetes explains
   the project's approach to removing features and components.
-{{% /capture %}}
+

content/en/docs/reference/command-line-tools-reference/kube-apiserver.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 30
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 
 The Kubernetes API server validates and configures data
@@ -16,9 +17,10 @@ cluster's shared state through which all other components interact.
 kube-apiserver [flags]
 ```
 
-{{% /capture %}}
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -1082,5 +1084,5 @@ kube-apiserver [flags]
 
 
 
-{{% /capture %}}
+
 

content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 30
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 
 The Kubernetes controller manager is a daemon that embeds
@@ -20,9 +21,10 @@ controller, and serviceaccounts controller.
 kube-controller-manager [flags]
 ```
 
-{{% /capture %}}
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -897,5 +899,5 @@ kube-controller-manager [flags]
 
 
 
-{{% /capture %}}
+
 

content/en/docs/reference/command-line-tools-reference/kube-proxy.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 30
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 
 The Kubernetes network proxy runs on each node. This
@@ -19,9 +20,10 @@ with the apiserver API to configure the proxy.
 kube-proxy [flags]
 ```
 
-{{% /capture %}}
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -336,5 +338,5 @@ kube-proxy [flags]
 
 
 
-{{% /capture %}}
+
 

content/en/docs/reference/command-line-tools-reference/kube-scheduler.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 30
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 
 The Kubernetes scheduler is a policy-rich, topology-aware,
@@ -20,9 +21,10 @@ for more information about scheduling and the kube-scheduler component.
 kube-scheduler [flags]
 ```
 
-{{% /capture %}}
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -512,5 +514,5 @@ kube-scheduler [flags]
 
 
 
-{{% /capture %}}
+
 

content/en/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping.md

@@ -5,10 +5,10 @@ reviewers:
 - smarterclayton
 - awly
 title: TLS bootstrapping
-content_template: templates/concept
+content_type: concept
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 In a Kubernetes cluster, the components on the worker nodes - kubelet and kube-proxy - need to communicate with Kubernetes master components, specifically kube-apiserver.
 In order to ensure that communication is kept private, not interfered with, and ensure that each component of the cluster is talking to another trusted component, we strongly
@@ -24,9 +24,9 @@ found [here](https://github.com/kubernetes/kubernetes/pull/20439).
 This document describes the process of node initialization, how to set up TLS client certificate bootstrapping for
 kubelets, and how it works. 
 
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 
 ## Initialization Process
 When a worker node starts up, the kubelet does the following:
@@ -454,4 +454,4 @@ An issue is open referencing this [here](https://github.com/kubernetes/kubernete
 
 
 
-{{% /capture %}}
+

content/en/docs/reference/command-line-tools-reference/kubelet.md

@@ -4,7 +4,8 @@ content_template: templates/tool-reference
 weight: 28
 ---
 
-{{% capture synopsis %}}
+## {{% heading "synopsis" %}}
+
 
 The kubelet is the primary "node agent" that runs on each
 node. It can register the node with the apiserver using one of: the hostname; a flag to override the hostname; or specific logic for a cloud provider.
@@ -24,10 +25,11 @@ HTTP server: The kubelet can also listen for HTTP and respond to a simple API (u
 kubelet [flags]
 ```
 
-{{% /capture %}}
 
 
-{{% capture options %}}
+
+## {{% heading "options" %}}
+
 
    <table style="width: 100%; table-layout: fixed;">
 <colgroup>
@@ -1265,4 +1267,4 @@ kubelet [flags]
 </tbody>
 </table>
 
-{{% /capture %}}
+