add en pages

content/en/docs/tasks/tls/certificate-rotation.md

@@ -3,22 +3,23 @@ reviewers:
 - jcbsmpsn
 - mikedanese
 title: Certificate Rotation
-content_template: templates/task
+content_type: task
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 This page shows how to enable and configure certificate rotation for the kubelet.
-{{% /capture %}}
+
 
 {{< feature-state for_k8s_version="v1.8" state="beta" >}}
 
-{{% capture prerequisites %}}
+## {{% heading "prerequisites" %}}
+
 
 * Kubernetes version 1.8.0 or later is required
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Overview
 
@@ -77,6 +78,6 @@ kubelet will retrieve the new signed certificate from the Kubernetes API and
 write that to disk. Then it will update the connections it has to the
 Kubernetes API to reconnect using the new certificate.
 
-{{% /capture %}}
+
 
 

content/en/docs/tasks/tls/managing-tls-in-a-cluster.md

@@ -1,13 +1,13 @@
 ---
 title: Manage TLS Certificates in a Cluster
-content_template: templates/task
+content_type: task
 reviewers:
 - mikedanese
 - beacham
 - liggit
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 Kubernetes provides a `certificates.k8s.io` API, which lets you provision TLS
 certificates signed by a Certificate Authority (CA) that you control. These CA
@@ -23,16 +23,17 @@ CA for this purpose, but you should never rely on this. Do not assume that
 these certificates will validate against the cluster root CA.
 {{< /note >}}
 
-{{% /capture %}}
 
 
-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Trusting TLS in a Cluster
 
@@ -222,4 +223,4 @@ enable it, pass the `--cluster-signing-cert-file` and
 `--cluster-signing-key-file` parameters to the controller manager with paths to
 your Certificate Authority's keypair.
 
-{{% /capture %}}
+