add en pages

2020-05-30 15:10:23 -04:00
parent 1502e0281d
commit ecc27bbbe7
347 changed files with 2900 additions and 2537 deletions
@@ -2,20 +2,20 @@
 title: Tasks
 main_menu: true
 weight: 50
-content_template: templates/concept
+content_type: concept
 ---

 {{< toc >}}

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

 This section of the Kubernetes documentation contains pages that
 show how to do individual tasks. A task page shows how to do a
 single thing, typically by giving a short sequence of steps.

-{{% /capture %}}

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

 ## Web UI (Dashboard)

@@ -73,11 +73,12 @@ Configure and schedule NVIDIA GPUs for use as a resource by nodes in a cluster.

 Configure and schedule huge pages as a schedulable resource in a cluster.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 If you would like to write a task page, see
 [Creating a Documentation Pull Request](/docs/home/contribute/create-pull-request/).

-{{% /capture %}}
+
@@ -1,17 +1,17 @@
 ---
 title: Accessing Clusters
 weight: 20
-content_template: templates/concept
+content_type: concept
 ---

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

 This topic discusses multiple ways to interact with clusters.

-{{% /capture %}}


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

 ## Accessing for the first time with kubectl

@@ -376,4 +376,3 @@ There are several different proxies you may encounter when using Kubernetes:
 Kubernetes users will typically not need to worry about anything other than the first two types.  The cluster admin
 will typically ensure that the latter types are setup correctly.

-{{% /capture %}}
@@ -1,25 +1,26 @@
 ---
 title: Communicate Between Containers in the Same Pod Using a Shared Volume
-content_template: templates/task
+content_type: task
 weight: 110
 ---

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

 This page shows how to use a Volume to communicate between two Containers running
 in the same Pod. See also how to allow processes to communicate by [sharing process namespace](/docs/tasks/configure-pod-container/share-process-namespace/) between containers.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ##  Creating a Pod that runs two Containers

@@ -108,10 +109,10 @@ The output shows that nginx serves a web page written by the debian container:

    Hello from the debian container

-{{% /capture %}}


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

 ## Discussion

@@ -127,10 +128,11 @@ The Volume in this exercise provides a way for Containers to communicate during
 the life of the Pod. If the Pod is deleted and recreated, any data stored in
 the shared Volume is lost.

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about
 [patterns for composite containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns).
@@ -147,7 +149,7 @@ the shared Volume is lost.

 * See [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core).

-{{% /capture %}}
+



@@ -1,6 +1,6 @@
 ---
 title: Configure Access to Multiple Clusters
-content_template: templates/task
+content_type: task
 weight: 30
 card:
  name: tasks
@@ -8,7 +8,7 @@ card:
 ---


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

 This page shows how to configure access to multiple clusters by using
 configuration files. After your clusters, users, and contexts are defined in
@@ -21,15 +21,16 @@ a *kubeconfig file*. This is a generic way of referring to configuration files.
 It does not mean that there is a file named `kubeconfig`.
 {{< /note >}}

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Define clusters, users, and contexts

@@ -369,14 +370,15 @@ export KUBECONFIG=$KUBECONFIG_SAVED
 $Env:KUBECONFIG=$ENV:KUBECONFIG_SAVED
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * [Organizing Cluster Access Using kubeconfig Files](/docs/concepts/configuration/organize-cluster-access-kubeconfig/)
 * [kubectl config](/docs/reference/generated/kubectl/kubectl-commands#config)

-{{% /capture %}}
+



@@ -3,27 +3,28 @@ reviewers:
 - bprashanth
 - davidopp
 title: Configure Your Cloud Provider's Firewalls
-content_template: templates/task
+content_type: task
 weight: 90
 ---

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

 Many cloud providers (e.g. Google Compute Engine) define firewalls that help prevent inadvertent
 exposure to the internet.  When exposing a service to the external world, you may need to open up
 one or more ports in these firewalls to serve traffic.  This document describes this process, as
 well as any provider specific details that may be necessary.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Restrict Access For LoadBalancer Service

@@ -106,4 +107,4 @@ the wilds of the internet.

 {{< /note >}}

-{{% /capture %}}
+
@@ -1,13 +1,13 @@
 ---
 title: Configure DNS for a Cluster
 weight: 120
-content_template: templates/concept
+content_type: concept
 ---

-{{% capture overview %}}
+<!-- overview -->
 Kubernetes offers a DNS cluster addon, which most of the supported environments enable by default. In Kubernetes version 1.11 and later, CoreDNS is recommended and is installed by default with kubeadm.
-{{% /capture %}}
-{{% capture body %}}
+
+<!-- body -->
 For more information on how to configure CoreDNS for a Kubernetes cluster, see the [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers/). An example demonstrating how to use Kubernetes DNS with kube-dns, see the [Kubernetes DNS sample plugin](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns).

-{{% /capture %}}
+
@@ -1,30 +1,32 @@
 ---
 title: Connect a Front End to a Back End Using a Service
-content_template: templates/tutorial
+content_type: tutorial
 weight: 70
 ---

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

 This task shows how to create a frontend and a backend
 microservice. The backend microservice is a hello greeter. The
 frontend and backend are connected using a Kubernetes
 {{< glossary_tooltip term_id="service" >}} object.

-{{% /capture %}}


-{{% capture objectives %}}
+
+## {{% heading "objectives" %}}
+

 * Create and run a microservice using a {{< glossary_tooltip term_id="deployment" >}} object.
 * Route traffic to the backend using a frontend.
 * Use a Service object to connect the frontend application to the
  backend application.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -34,10 +36,10 @@ frontend and backend are connected using a Kubernetes
  support this, you can use a Service of type
  [NodePort](/docs/concepts/services-networking/service/#nodeport) instead.

-{{% /capture %}}


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

 ## Creating the backend using a Deployment

@@ -201,9 +203,10 @@ The output shows the message generated by the backend:
 {"message":"Hello"}
 ```

-{{% /capture %}}

-{{% capture cleanup %}}
+
+## {{% heading "cleanup" %}}
+

 To delete the Services, enter this command:

@@ -213,13 +216,14 @@ To delete the Deployments, the ReplicaSets and the Pods that are running the bac

    kubectl delete deployment frontend hello

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about [Services](/docs/concepts/services-networking/service/)
 * Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/)

-{{% /capture %}}
+


@@ -1,11 +1,11 @@
 ---
 title: Create an External Load Balancer
-content_template: templates/task
+content_type: task
 weight: 80
 ---


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

 This page shows how to create an External Load Balancer.

@@ -24,15 +24,16 @@ services externally-reachable URLs, load balance the traffic, terminate SSL etc.
 please check the [Ingress](/docs/concepts/services-networking/ingress/)
 documentation.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Configuration file

@@ -199,4 +200,4 @@ Once the external load balancers provide weights, this functionality can be adde

 Internal pod to pod traffic should behave similar to ClusterIP services, with equal probability across all pods.

-{{% /capture %}}
+
@@ -1,25 +1,26 @@
 ---
 title: Set up Ingress on Minikube with the NGINX Ingress Controller
-content_template: templates/task
+content_type: task
 weight: 100
 ---

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

 An [Ingress](/docs/concepts/services-networking/ingress/) is an API object that defines rules which allow external access 
 to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress.

 This page shows you how to set up a simple Ingress which routes requests to Service web or web2 depending on the HTTP URI.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Create a Minikube cluster

@@ -275,13 +276,14 @@ The following file is an Ingress resource that sends traffic to your Service via

    {{< note >}}If you are running Minikube locally, you can visit hello-world.info and hello-world.info/v2 from your browser.{{< /note >}}

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Read more about [Ingress](/docs/concepts/services-networking/ingress/)
 * Read more about [Ingress Controllers](/docs/concepts/services-networking/ingress-controllers/)
 * Read more about [Services](/docs/concepts/services-networking/service/)

-{{% /capture %}}
+

@@ -1,23 +1,24 @@
 ---
 title: List All Container Images Running in a Cluster
-content_template: templates/task
+content_type: task
 weight: 100
 ---

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

 This page shows how to use kubectl to list all of the Container images
 for Pods running in a cluster.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 In this exercise you will use kubectl to fetch all of the Pods
 running in a cluster, and format the output to pull out the list
@@ -108,19 +109,20 @@ kubectl get pods --all-namespaces -o go-template --template="{{range .items}}{{r



-{{% /capture %}}

-{{% capture discussion %}}

-{{% /capture %}}
+<!-- discussion -->
+
+
+
+## {{% heading "whatsnext" %}}

-{{% capture whatsnext %}}

 ### Reference

 * [Jsonpath](/docs/user-guide/jsonpath/) reference guide
 * [Go template](https://golang.org/pkg/text/template/) reference guide

-{{% /capture %}}
+


@@ -1,29 +1,30 @@
 ---
 title: Use Port Forwarding to Access Applications in a Cluster
-content_template: templates/task
+content_type: task
 weight: 40
 min-kubernetes-server-version: v1.10
 ---

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

 This page shows how to use `kubectl port-forward` to connect to a Redis
 server running in a Kubernetes cluster. This type of connection can be useful
 for database debugging.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 * Install [redis-cli](http://redis.io/topics/rediscli).

-{{% /capture %}}


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

 ## Creating Redis deployment and service

@@ -179,10 +180,10 @@ for database debugging.
    PONG
    ```

-{{% /capture %}}


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

 ## Discussion

@@ -196,9 +197,10 @@ The support for UDP protocol is tracked in
 [issue 47862](https://github.com/kubernetes/kubernetes/issues/47862).
 {{< /note >}}

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Learn more about [kubectl port-forward](/docs/reference/generated/kubectl/kubectl-commands/#port-forward).
-{{% /capture %}}
+
@@ -1,35 +1,37 @@
 ---
 title: Use a Service to Access an Application in a Cluster
-content_template: templates/tutorial
+content_type: tutorial
 weight: 60
 ---

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

 This page shows how to create a Kubernetes Service object that external
 clients can use to access an application running in a cluster. The Service
 provides load balancing for an application that has two running instances.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


-{{% capture objectives %}}
+
+## {{% heading "objectives" %}}
+

 * Run two instances of a Hello World application.
 * Create a Service object that exposes a node port.
 * Use the Service object to access the running application.

-{{% /capture %}}


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

 ## Creating a service for an application running in two pods

@@ -130,10 +132,11 @@ As an alternative to using `kubectl expose`, you can use a
 [service configuration file](/docs/concepts/services-networking/service/)
 to create a Service.

-{{% /capture %}}


-{{% capture cleanup %}}
+
+## {{% heading "cleanup" %}}
+

 To delete the Service, enter this command:

@@ -144,11 +147,12 @@ the Hello World application, enter this command:

    kubectl delete deployment hello-world

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Learn more about
 [connecting applications with services](/docs/concepts/services-networking/connect-applications-service/).
-{{% /capture %}}
+
@@ -4,7 +4,7 @@ reviewers:
 - mikedanese
 - rf232
 title: Web UI (Dashboard)
-content_template: templates/concept
+content_type: concept
 weight: 10
 card:
  name: tasks
@@ -12,7 +12,7 @@ card:
  title: Use the Web UI Dashboard
 ---

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

 Dashboard is a web-based Kubernetes user interface. You can use Dashboard to deploy containerized applications to a Kubernetes cluster, troubleshoot your containerized application, and manage the cluster resources. You can use Dashboard to get an overview of applications running on your cluster, as well as for creating or modifying individual Kubernetes resources (such as Deployments, Jobs, DaemonSets, etc). For example, you can scale a Deployment, initiate a rolling update, restart a pod or deploy new applications using a deploy wizard.

@@ -20,10 +20,10 @@ Dashboard also provides information on the state of Kubernetes resources in your

 ![Kubernetes Dashboard UI](/images/docs/ui-dashboard.png)

-{{% /capture %}}


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

 ## Deploying the Dashboard UI

@@ -162,11 +162,12 @@ Pod lists and detail pages link to a logs viewer that is built into Dashboard. T

 ![Logs viewer](/images/docs/ui-dashboard-logs-view.png)

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 For more information, see the
 [Kubernetes Dashboard project page](https://github.com/kubernetes/dashboard).

-{{% /capture %}}
+
@@ -4,17 +4,18 @@ reviewers:
 - lavalamp
 - cheftako
 - chenopis
-content_template: templates/task
+content_type: task
 weight: 10
 ---

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

 Configuring the [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) allows the Kubernetes apiserver to be extended with additional APIs, which are not part of the core Kubernetes APIs. 

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -26,9 +27,9 @@ Reusing the same CA for different client types can negatively impact the cluster
 {{< /caution >}}
 {{< /note >}}

-{{% /capture %}}

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

 ## Authentication Flow

@@ -222,7 +223,7 @@ If you are not running kube-proxy on a host running the API server, then you mus

    --enable-aggregator-routing=true

-{{% /capture %}}
+

 ### Register APIService objects

@@ -275,11 +276,12 @@ spec:
 ...
 ```

-{{% capture whatsnext %}}
+## {{% heading "whatsnext" %}}
+

 * [Setup an extension api-server](/docs/tasks/access-kubernetes-api/setup-extension-api-server/) to work with the aggregation layer.
 * For a high level overview, see [Extending the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation/).
 * Learn how to [Extend the Kubernetes API Using Custom Resource Definitions](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/).

-{{% /capture %}}
+

@@ -3,19 +3,20 @@ title: Versions in CustomResourceDefinitions
 reviewers:
 - sttts
 - liggitt
-content_template: templates/task
+content_type: task
 weight: 30
 min-kubernetes-server-version: v1.16
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page explains how to add versioning information to
 [CustomResourceDefinitions](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1beta1-apiextensions), to indicate the stability
 level of your CustomResourceDefinitions or advance your API to a new version with conversion between API representations. It also describes how to upgrade an object from one version to another.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}}

@@ -23,9 +24,9 @@ You should have a initial understanding of [custom resources](/docs/concepts/api

 {{< version-check >}}

-{{% /capture %}}

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

 ## Overview

@@ -961,4 +962,4 @@ The following is an example procedure to upgrade from `v1beta1` to `v1`.
    storage version, which is `v1`.
 2. Remove `v1beta1` from the CustomResourceDefinition `status.storedVersions` field.

-{{% /capture %}}
+
@@ -6,18 +6,19 @@ reviewers:
 - liggitt
 - roycaihw
 - sttts
-content_template: templates/task
+content_type: task
 weight: 20
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to install a
 [custom resource](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
 into the Kubernetes API by creating a
 [CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1beta1-apiextensions).
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -25,9 +26,9 @@ into the Kubernetes API by creating a

 * Read about [custom resources](/docs/concepts/api-extension/custom-resources/).

-{{% /capture %}}

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

 ## Create a CustomResourceDefinition

@@ -568,9 +569,9 @@ See [Custom resource definition versioning](/docs/tasks/access-kubernetes-api/cu
 for more information about serving multiple versions of your
 CustomResourceDefinition and migrating your objects from one version to another.

-{{% /capture %}}

-{{% capture discussion %}}
+
+<!-- discussion -->
 ## Advanced topics

 ### Finalizers
@@ -1448,13 +1449,13 @@ NAME                          AGE
 crontabs/my-new-cron-object   3s
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * See [CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1-apiextensions-k8s-io).

 * Serve [multiple versions](/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning/) of a
  CustomResourceDefinition.

-{{% /capture %}}
@@ -1,14 +1,15 @@
 ---
 title: Use an HTTP Proxy to Access the Kubernetes API
-content_template: templates/task
+content_type: task
 weight: 40
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to use an HTTP proxy to access the Kubernetes API.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -19,9 +20,9 @@ a Hello world application by entering this command:
 kubectl run node-hello --image=gcr.io/google-samples/node-hello:1.0 --port=8080
 ```

-{{% /capture %}}

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

 ## Using kubectl to start a proxy server

@@ -81,10 +82,11 @@ The output should look similar to this:
            ...
    }

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Learn more about [kubectl proxy](/docs/reference/generated/kubectl/kubectl-commands#proxy).
-{{% /capture %}}
+


@@ -4,25 +4,26 @@ reviewers:
 - lavalamp
 - cheftako
 - chenopis
-content_template: templates/task
+content_type: task
 weight: 15
 ---

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

 Setting up an extension API server to work the aggregation layer allows the Kubernetes apiserver to be extended with additional APIs, which are not part of the core Kubernetes APIs. 

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 * You must [configure the aggregation layer](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/) and enable the apiserver flags.

-{{% /capture %}}

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

 ## Setup an extension api-server to work with the aggregation layer

@@ -46,15 +47,16 @@ Alternatively, you can use an existing 3rd party solution, such as [apiserver-bu
 1. Create a Kubernetes apiservice. The CA cert above should be base64 encoded, stripped of new lines and used as the spec.caBundle in the apiservice. This should not be namespaced. If using the [kube-aggregator API](https://github.com/kubernetes/kube-aggregator/), only pass in the PEM encoded CA bundle because the base 64 encoding is done for you.
 1. Use kubectl to get your resource. It should return "No resources found." Which means that everything worked but you currently have no objects of that resource type created yet.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * If you haven't already, [configure the aggregation layer](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/) and enable the apiserver flags.
 * For a high level overview, see [Extending the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation).
 * Learn how to [Extend the Kubernetes API Using Custom Resource Definitions](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/).

-{{% /capture %}}
+



@@ -1,18 +1,19 @@
 ---
 title: Access Clusters Using the Kubernetes API
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to access clusters using the Kubernetes API.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Accessing the Kubernetes API

@@ -449,5 +450,5 @@ The output will be similar to this:
 }
 ```

-{{% /capture %}}
+

@@ -1,18 +1,19 @@
 ---
 title: Access Services Running on Clusters
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to connect to services running on the Kubernetes cluster.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Accessing services running on the cluster

@@ -132,6 +133,6 @@ You may be able to put an apiserver proxy URL into the address bar of a browser.
  - Some web apps may not work, particularly those with client side javascript that construct URLs in a
    way that is unaware of the proxy path prefix.

-{{% /capture %}}
+


@@ -1,21 +1,22 @@
 ---
 title: Change the default StorageClass
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to change the default Storage Class that is used to
 provision volumes for PersistentVolumeClaims that have no special requirements.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Why change the default storage class?

@@ -93,10 +94,11 @@ for details about addon manager and how to disable individual addons.
      gold (default)   kubernetes.io/gce-pd      1d
      ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Learn more about [PersistentVolumes](/docs/concepts/storage/persistent-volumes/).
-{{% /capture %}}
+


@@ -1,20 +1,21 @@
 ---
 title: Change the Reclaim Policy of a PersistentVolume
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to change the reclaim policy of a Kubernetes
 PersistentVolume.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Why change reclaim policy of a PersistentVolume

@@ -80,9 +81,10 @@ kubectl patch pv <your-pv-name> -p "{\"spec\":{\"persistentVolumeReclaimPolicy\"
    `default/claim3` has reclaim policy `Retain`. It will not be automatically
    deleted when a user deletes claim `default/claim3`.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Learn more about [PersistentVolumes](/docs/concepts/storage/persistent-volumes/).
 * Learn more about [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims).

@@ -91,6 +93,6 @@ kubectl patch pv <your-pv-name> -p "{\"spec\":{\"persistentVolumeReclaimPolicy\"
 * [PersistentVolume](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#persistentvolume-v1-core)
 * [PersistentVolumeClaim](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#persistentvolumeclaim-v1-core)
 * See the `persistentVolumeReclaimPolicy` field of [PersistentVolumeSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#persistentvolumeclaim-v1-core).
-{{% /capture %}}
+


@@ -3,20 +3,20 @@ reviewers:
 - lavalamp
 - thockin
 title: Cluster Management
-content_template: templates/concept
+content_type: concept
 ---

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

 This document describes several topics related to the lifecycle of a cluster: creating a new cluster,
 upgrading your cluster's
 master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a
 running cluster.

-{{% /capture %}}


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

 ## Creating and configuring a Cluster

@@ -224,4 +224,4 @@ kubectl convert -f pod.yaml --output-version v1

 For more options, please refer to the usage of [kubectl convert](/docs/reference/generated/kubectl/kubectl-commands#convert) command.

-{{% /capture %}}
+
@@ -3,10 +3,10 @@ reviewers:
 - davidopp
 - madhusudancs
 title: Configure Multiple Schedulers
-content_template: templates/task
+content_type: task
 ---

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

 Kubernetes ships with a default scheduler that is described [here](/docs/admin/kube-scheduler/).
 If the default scheduler does not suit your needs you can implement your own scheduler.
@@ -19,16 +19,17 @@ document. Please refer to the kube-scheduler implementation in
 [pkg/scheduler](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/pkg/scheduler)
 in the Kubernetes source directory for a canonical example.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Package the scheduler

@@ -219,9 +220,9 @@ kubectl create -f pod3.yaml
 kubectl get pods
 ```

-{{% /capture %}}

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

 ### Verifying that the pods were scheduled using the desired schedulers

@@ -241,4 +242,4 @@ verify that the pods were scheduled by the desired schedulers.
 kubectl get events
 ```

-{{% /capture %}}
+
@@ -3,23 +3,24 @@ reviewers:
 - mml
 - wojtek-t
 title: Operating etcd clusters for Kubernetes
-content_template: templates/task
+content_type: task
 ---

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

 {{< glossary_definition term_id="etcd" length="all" prepend="etcd is a ">}}

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Prerequisites

@@ -238,4 +239,4 @@ To urgently fix this bug for Kubernetes 1.15 or earlier, build a custom kube-api

 See ["kube-apiserver 1.13.x refuses to work when first etcd-server is not available"](https://github.com/kubernetes/kubernetes/issues/72102).

-{{% /capture %}}
+
@@ -3,18 +3,19 @@ reviewers:
 - johnbelamaric
 title: Using CoreDNS for Service Discovery
 min-kubernetes-server-version: v1.9
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page describes the CoreDNS upgrade process and how to install CoreDNS instead of kube-dns.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## About CoreDNS

@@ -89,14 +90,15 @@ There is a helpful [guideline and walkthrough](https://github.com/coredns/deploy
 When resource utilisation is a concern, it may be useful to tune the configuration of CoreDNS. For more details, check out the
 [documentation on scaling CoreDNS](https://github.com/coredns/deployment/blob/master/kubernetes/Scaling_CoreDNS.md).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 You can configure [CoreDNS](https://coredns.io) to support many more use cases than
 kube-dns by modifying the `Corefile`. For more information, see the
 [CoreDNS site](https://coredns.io/2017/05/08/custom-dns-entries-for-kubernetes/).

-{{% /capture %}}
+


@@ -4,10 +4,10 @@ reviewers:
 - sjenning
 - ConnorDoyle
 - balajismaniam
-content_template: templates/task
+content_type: task
 ---

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

 {{< feature-state for_k8s_version="v1.12" state="beta" >}}

@@ -18,16 +18,17 @@ acceptably. The kubelet provides methods to enable more complex workload
 placement policies while keeping the abstraction free from explicit placement
 directives.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## CPU Management Policies

@@ -211,4 +212,4 @@ and `requests` are set equal to `limits` when not explicitly specified. And the
 container's resource limit for the CPU resource is an integer greater than or
 equal to one. The `nginx` container is granted 2 exclusive CPUs.

-{{% /capture %}}
+
@@ -4,13 +4,14 @@ reviewers:
 - danwinship
 title: Declare Network Policy
 min-kubernetes-server-version: v1.8
-content_template: templates/task
+content_type: task
 ---
-{{% capture overview %}}
+<!-- overview -->
 This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/concepts/services-networking/network-policies/) to declare network policies that govern how pods communicate with each other.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -25,9 +26,9 @@ Make sure you've configured a network provider with network policy support. Ther
 {{< note >}}
 The above list is sorted alphabetically by product name, not by recommendation or preference. This example is valid for a Kubernetes cluster using any of these providers.
 {{< /note >}}
-{{% /capture %}}

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

 ## Create an `nginx` deployment and expose it via a service

@@ -146,4 +147,4 @@ Connecting to nginx (10.100.0.16:80)
 remote file exists
 ```

-{{% /capture %}}
+
@@ -4,18 +4,18 @@ reviewers:
 - thockin
 - wlan0
 title: Developing Cloud Controller Manager
-content_template: templates/concept
+content_type: concept
 ---

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

 {{< feature-state for_k8s_version="v1.11" state="beta" >}}

 {{< glossary_definition term_id="cloud-controller-manager" length="all" prepend="The cloud-controller-manager is">}}

-{{% /capture %}}

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

 ## Background

@@ -41,4 +41,4 @@ controller manager as your starting point.

 For in-tree cloud providers, you can run the in-tree cloud controller manager as a {{< glossary_tooltip term_id="daemonset" >}} in your cluster. See [Cloud Controller Manager Administration](/docs/tasks/administer-cluster/running-cloud-controller/) for more details.

-{{% /capture %}}
+
@@ -3,24 +3,25 @@ reviewers:
 - bowei
 - zihongz
 title: Customizing DNS Service
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page explains how to configure your DNS Pod and customize the
 DNS resolution process. In Kubernetes version 1.11 and later, CoreDNS is at GA
 and is installed by default with kubeadm. See [CoreDNS ConfigMap options](#coredns-configmap-options) 
 and [Using CoreDNS for Service Discovery](/docs/tasks/administer-cluster/coredns/).
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 * Kubernetes version 1.6 or later. To work with CoreDNS, version 1.9 or later.
 * The appropriate add-on: kube-dns or CoreDNS. To install with kubeadm,
 see [the kubeadm reference documentation](/docs/reference/setup-tools/kubeadm/kubeadm-alpha/#cmd-phase-addon).
-{{% /capture %}}

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

 ## Introduction

@@ -213,9 +214,9 @@ their destination DNS servers:
 See [ConfigMap options](#configmap-options) for
 details about the configuration option format.

-{{% /capture %}}

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

 #### Effects on Pods

@@ -302,7 +303,7 @@ data:
    ["172.16.0.1"]
 ```

-{{% /capture %}}
+

 ## CoreDNS configuration equivalent to kube-dns

@@ -3,20 +3,21 @@ reviewers:
 - bowei
 - zihongz
 title:  Debugging DNS Resolution
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page provides hints on diagnosing DNS problems.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 * Kubernetes version 1.6 and above.
 * The cluster must be configured to use the `coredns` (or `kube-dns`) addons.
-{{% /capture %}}

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

 ### Create a simple Pod to use as a test environment

@@ -273,5 +274,5 @@ for more information.
 ## What's next
 - [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).

-{{% /capture %}}
+

@@ -1,14 +1,15 @@
 ---
 title: Autoscale the DNS Service in a Cluster
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to enable and configure autoscaling of the DNS service in
 your Kubernetes cluster.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -16,9 +17,9 @@ your Kubernetes cluster.

 * Make sure [Kubernetes DNS](/docs/concepts/services-networking/dns-pod-service/) is enabled.

-{{% /capture %}}

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

 ## Determine whether DNS horizontal autoscaling is already enabled {#determining-whether-dns-horizontal-autoscaling-is-already-enabled}

@@ -201,9 +202,9 @@ The common path for this dns-autoscaler is:
 After the manifest file is deleted, the Addon Manager will delete the
 dns-autoscaler Deployment.

-{{% /capture %}}

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

 ## Understanding how DNS horizontal autoscaling works

@@ -226,10 +227,11 @@ the autoscaler Pod.
 * The autoscaler provides a controller interface to support two control
 patterns: *linear* and *ladder*.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Read about [Guaranteed Scheduling For Critical Add-On Pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/).
 * Learn more about the
 [implementation of cluster-proportional-autoscaler](https://github.com/kubernetes-incubator/cluster-proportional-autoscaler).
-{{% /capture %}}
+
@@ -3,19 +3,20 @@ reviewers:
 - bowei
 - freehan
 title: Enabling EndpointSlices
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page provides an overview of enabling EndpointSlices in Kubernetes.
-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
  {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Introduction

@@ -55,9 +56,10 @@ existing Endpoints functionality, EndpointSlices include new bits of information
 such as topology. They will allow for greater scalability and extensibility of
 network endpoints in your cluster.

-{{% capture whatsnext %}}
+## {{% heading "whatsnext" %}}
+

 * Read about [EndpointSlices](/docs/concepts/services-networking/endpoint-slices/)
 * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)

-{{% /capture %}}
+
@@ -4,19 +4,20 @@ reviewers:
 - johnbelamaric
 - imroc
 title: Enabling Service Topology
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page provides an overview of enabling Service Topology in Kubernetes.
-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
  {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Introduction

@@ -45,10 +46,11 @@ To enable service topology, enable the `ServiceTopology` and `EndpointSlice` fea
 ```


-{{% capture whatsnext %}}
+## {{% heading "whatsnext" %}}
+

 * Read about the [Service Topology](/docs/concepts/services-networking/service-topology) concept
 * Read about [Endpoint Slices](/docs/concepts/services-networking/endpoint-slices)
 * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)

-{{% /capture %}}
+
@@ -2,23 +2,24 @@
 reviewers:
 - smarterclayton
 title: Encrypting Secret Data at Rest
-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: 1.13
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to enable and configure encryption of secret data at rest.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 * etcd v3.0 or later is required

-{{% /capture %}}

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

 ## Configuration and determining whether encryption at rest is already enabled

@@ -215,4 +216,4 @@ kubectl get secrets --all-namespaces -o json | kubectl replace -f -
 ```
 to force all secrets to be decrypted.

-{{% /capture %}}
+
@@ -1,26 +1,27 @@
 ---
 title: Advertise Extended Resources for a Node
-content_template: templates/task
+content_type: task
 ---


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

 This page shows how to specify extended resources for a Node.
 Extended resources allow cluster administrators to advertise node-level
 resources that would otherwise be unknown to Kubernetes.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ## Get the names of your Nodes

@@ -189,10 +190,11 @@ kubectl describe node <your-node-name> | grep dongle

 (you should not see any output)

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For application developers

@@ -204,4 +206,4 @@ kubectl describe node <your-node-name> | grep dongle
 * [Configure Minimum and Maximum CPU Constraints for a Namespace](/docs/tasks/administer-cluster/cpu-constraint-namespace/)


-{{% /capture %}}
+
@@ -4,10 +4,10 @@ reviewers:
 - filipg
 - piosz
 title: Guaranteed Scheduling For Critical Add-On Pods
-content_template: templates/concept
+content_type: concept
 ---

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

 In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
 there are a number of add-ons which, for various reasons, must run on a regular cluster node (rather than the Kubernetes master).
@@ -19,14 +19,14 @@ vacated by the evicted critical add-on pod or the amount of resources available
 Note that marking a pod as critical is not meant to prevent evictions entirely; it only prevents the pod from becoming permanently unavailable.
 For static pods, this means it can't be evicted, but for non-static pods, it just means they will always be rescheduled.

-{{% /capture %}}


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


 ### Marking pod as critical

 To mark a Pod as critical, set priorityClassName for that Pod to `system-cluster-critical` or `system-node-critical`. `system-node-critical` is the highest available priority, even higher than `system-cluster-critical`.

-{{% /capture %}}
+
@@ -2,26 +2,27 @@
 reviewers:
 - jszczepkowski
 title: Set up High-Availability Kubernetes Masters
-content_template: templates/task
+content_type: task
 ---

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

 {{< feature-state for_k8s_version="v1.5" state="alpha" >}}

 You can replicate Kubernetes masters in `kube-up` or `kube-down` scripts for Google Compute Engine.
 This document describes how to use kube-up/down scripts to manage highly available (HA) masters and how HA masters are implemented for use with GCE.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Starting an HA-compatible cluster

@@ -118,9 +119,9 @@ If the cluster is large, it may take a long time to duplicate its state.
 This operation may be sped up by migrating etcd data directory, as described [here](https://coreos.com/etcd/docs/latest/admin_guide.html#member-migration)
 (we are considering adding support for etcd data dir migration in future).

-{{% /capture %}}

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

 ## Implementation notes

@@ -173,4 +174,4 @@ To make such deployment secure, communication between etcd instances is authoriz

 [Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/cluster-lifecycle/ha_master.md)

-{{% /capture %}}
+
@@ -1,19 +1,20 @@
 ---
 title: IP Masquerade Agent User Guide
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to configure and enable the ip-masq-agent.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

-{{% capture discussion %}}
+
+<!-- discussion -->
 ## IP Masquerade Agent User Guide

 The ip-masq-agent configures iptables rules to hide a pod's IP address behind the cluster node's IP address. This is typically done when sending traffic to destinations outside the cluster's pod [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) range.
@@ -53,9 +54,9 @@ MASQUERADE  all  --  anywhere             anywhere             /* ip-masq-agent:

 By default, in GCE/Google Kubernetes Engine starting with Kubernetes version 1.7.0, if network policy is enabled or you are using a cluster CIDR not in the 10.0.0.0/8 range, the ip-masq-agent will run in your cluster.  If you are running in another environment, you can add the ip-masq-agent [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) to your cluster:

-{{% /capture %}}

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

 ## Create an ip-masq-agent
 To create an ip-masq-agent, run the following kubectl command:
@@ -110,4 +111,4 @@ nonMasqueradeCIDRs:
 resyncInterval: 60s
 masqLinkLocal: true
 ```
-{{% /capture %}}
+
@@ -2,13 +2,14 @@
 reviewers:
 - smarterclayton
 title: Using a KMS provider for data encryption
-content_template: templates/task
+content_type: task
 ---
-{{% capture overview %}}
+<!-- overview -->
 This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -18,9 +19,9 @@ This page shows how to configure a Key Management Service (KMS) provider and plu

 {{< feature-state for_k8s_version="v1.12" state="beta" >}}

-{{% /capture %}}

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

 The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd. The data is encrypted using a data encryption key (DEK); a new DEK is generated for each encryption. The DEKs are encrypted with a key encryption key (KEK) that is stored and managed in a remote KMS. The KMS provider uses gRPC to communicate with a specific KMS 
 plugin. The KMS plugin, which is implemented as a gRPC server and deployed on the same host(s) as the Kubernetes master(s), is responsible for all communication with the remote KMS.
@@ -183,4 +184,4 @@ To disable encryption at rest:
 ```
 kubectl get secrets --all-namespaces -o json | kubectl replace -f -
 ```
-{{% /capture %}}
+
@@ -4,20 +4,21 @@ reviewers:
 - patricklang
 title: Adding Windows nodes
 min-kubernetes-server-version: 1.17
-content_template: templates/tutorial
+content_type: tutorial
 weight: 30
 ---

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

 {{< feature-state for_k8s_version="v1.18" state="beta" >}}

 You can use Kubernetes to run a mixture of Linux and Windows nodes, so you can mix Pods that run on Linux on with Pods that run on Windows. This page shows how to register Windows nodes to your cluster.

-{{% /capture %}}


-{{% capture prerequisites %}} {{< version-check >}}
+
+## {{% heading "prerequisites" %}}
+ {{< version-check >}}

 * Obtain a [Windows Server 2019 license](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing)
 (or higher) in order to configure the Windows node that hosts Windows containers.
@@ -25,18 +26,19 @@ If you are using VXLAN/Overlay networking you must have also have [KB4489899](ht

 * A Linux-based Kubernetes kubeadm cluster in which you have access to the control plane (see [Creating a single control-plane cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)).

-{{% /capture %}}


-{{% capture objectives %}}
+
+## {{% heading "objectives" %}}
+

 * Register a Windows node to the cluster
 * Configure networking so Pods and Services on Linux and Windows can communicate with each other

-{{% /capture %}}


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

 ## Getting Started: Adding a Windows Node to Your Cluster

@@ -176,10 +178,11 @@ kubectl -n kube-system get pods -l app=flannel

 Once the flannel Pod is running, your node should enter the `Ready` state and then be available to handle workloads.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 - [Upgrading Windows kubeadm nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes)

-{{% /capture %}}
+
@@ -2,25 +2,26 @@
 reviewers:
 - sig-cluster-lifecycle
 title: Certificate Management with kubeadm
-content_template: templates/task
+content_type: task
 weight: 10
 ---

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

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

 Client certificates generated by [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/) expire after 1 year. This page explains how to manage certificate renewals with kubeadm.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 You should be familiar with [PKI certificates and requirements in Kubernetes](/docs/setup/best-practices/certificates/).

-{{% /capture %}}

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

 ## Using custom certificates {#custom-certificates}

@@ -242,4 +243,4 @@ After a certificate is signed using your preferred method, the certificate and t
 [cert-cas]: /docs/setup/best-practices/certificates/#single-root-ca
 [cert-table]: /docs/setup/best-practices/certificates/#all-certificates

-{{% /capture %}}
+
@@ -2,12 +2,12 @@
 reviewers:
 - sig-cluster-lifecycle
 title: Upgrading kubeadm clusters
-content_template: templates/task
+content_type: task
 weight: 20
 min-kubernetes-server-version: 1.18
 ---

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

 This page explains how to upgrade a Kubernetes cluster created with kubeadm from version
 1.17.x to version 1.18.x, and from version 1.18.x to 1.18.y (where `y > x`).
@@ -26,9 +26,10 @@ The upgrade workflow at high level is the following:
 1. Upgrade additional control plane nodes.
 1. Upgrade worker nodes.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 - You need to have a kubeadm Kubernetes cluster running version 1.17.0 or later.
 - [Swap must be disabled](https://serverfault.com/questions/684771/best-way-to-disable-swap-in-linux).
@@ -44,9 +45,9 @@ The upgrade workflow at high level is the following:
  or between PATCH versions of the same MINOR. That is, you cannot skip MINOR versions when you upgrade.
  For example, you can upgrade from 1.y to 1.y+1, but not from 1.y to 1.y+2.

-{{% /capture %}}

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

 ## Determine which version to upgrade to

@@ -395,7 +396,7 @@ kubectl get nodes

 The `STATUS` column should show `Ready` for all your nodes, and the version number should be updated.

-{{% /capture %}}
+

 ## Recovering from a failure state

@@ -1,29 +1,30 @@
 ---
 title: Upgrading Windows nodes
 min-kubernetes-server-version: 1.17
-content_template: templates/task
+content_type: task
 weight: 40
 ---

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

 {{< feature-state for_k8s_version="v1.18" state="beta" >}}

 This page explains how to upgrade a Windows node [created with kubeadm](/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes).

-{{% /capture %}}


-{{% capture prerequisites %}} 
+
+## {{% heading "prerequisites" %}}
+ 
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 * Familiarize yourself with [the process for upgrading the rest of your kubeadm
 cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to
 upgrade the control plane nodes before upgrading your Windows nodes.

-{{% /capture %}}


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

 ## Upgrading worker nodes

@@ -90,4 +91,4 @@ again replacing {{< param "fullversion" >}} with your desired version:
    ```


-{{% /capture %}}
+
@@ -3,10 +3,10 @@ reviewers:
 - mtaufen
 - dawnchen
 title: Set Kubelet parameters via a config file
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 {{< feature-state for_k8s_version="v1.10" state="beta" >}}

 A subset of the Kubelet's configuration parameters may be
@@ -16,15 +16,16 @@ This functionality is considered beta in v1.10.
 Providing parameters via a config file is the recommended approach because
 it simplifies node deployment and configuration management.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 - A v1.10 or higher Kubelet binary must be installed for beta functionality.

-{{% /capture %}}

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

 ## Create the config file

@@ -67,9 +68,9 @@ If `--config` is provided and the values are not specified via the command line,
 defaults for the `KubeletConfiguration` version apply.
 In the above example, this version is `kubelet.config.k8s.io/v1beta1`.

-{{% /capture %}}

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

 ## Relationship to Dynamic Kubelet Config

@@ -77,6 +78,6 @@ If you are using the [Dynamic Kubelet Configuration](/docs/tasks/administer-clus
 feature, the combination of configuration provided via `--config` and any flags which override these values
 is considered the default "last known good" configuration by the automatic rollback mechanism.

-{{% /capture %}}
+


@@ -1,9 +1,9 @@
 ---
 title: Limit Storage Consumption
-content_template: templates/task
+content_type: task
 ---

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

 This example demonstrates an easy way to limit the amount of storage consumed in a namespace.

@@ -11,15 +11,16 @@ The following resources are used in the demonstration: [ResourceQuota](/docs/con
 [LimitRange](/docs/tasks/administer-cluster/memory-default-namespace/),
 and [PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/).

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

-{{% capture steps %}}
+
+<!-- steps -->
 ## Scenario: Limiting Storage Consumption

 The cluster-admin is operating a cluster on behalf of a user population and the admin wants to control
@@ -77,9 +78,9 @@ spec:
    requests.storage: "5Gi"
 ```

-{{% /capture %}}

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

 ## Summary

@@ -87,6 +88,6 @@ A limit range can put a ceiling on how much storage is requested while a resourc
 consumed by a namespace through claim counts and cumulative storage capacity. The allows a cluster-admin to plan their
 cluster's storage budget without risk of any one project going over their allotment.

-{{% /capture %}}
+


@@ -1,11 +1,11 @@
 ---
 title: Configure Minimum and Maximum CPU Constraints for a Namespace
-content_template: templates/task
+content_type: task
 weight: 40
 ---


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

 This page shows how to set minimum and maximum values for the CPU resources used by Containers
 and Pods in a namespace. You specify minimum and maximum CPU values in a
@@ -13,19 +13,20 @@ and Pods in a namespace. You specify minimum and maximum CPU values in a
 object. If a Pod does not meet the constraints imposed by the LimitRange, it cannot be created
 in the namespace.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 Your cluster must have at least 1 CPU available for use to run the task examples.

-{{% /capture %}}


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

 ## Create a namespace

@@ -239,9 +240,10 @@ Delete your namespace:
 kubectl delete namespace constraints-cpu-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -266,7 +268,7 @@ kubectl delete namespace constraints-cpu-example
 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)


-{{% /capture %}}
+



@@ -1,10 +1,10 @@
 ---
 title: Configure Default CPU Requests and Limits for a Namespace
-content_template: templates/task
+content_type: task
 weight: 20
 ---

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

 This page shows how to configure default CPU requests and limits for a namespace.
 A Kubernetes cluster can be divided into namespaces. If a Container is created in a namespace
@@ -12,14 +12,15 @@ that has a default CPU limit, and the Container does not specify its own CPU lim
 the Container is assigned the default CPU limit. Kubernetes assigns a default CPU request
 under certain conditions that are explained later in this topic.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Create a namespace

@@ -163,9 +164,10 @@ Delete your namespace:
 kubectl delete namespace default-cpu-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -189,6 +191,6 @@ kubectl delete namespace default-cpu-example

 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)

-{{% /capture %}}
+


@@ -1,11 +1,11 @@
 ---
 title: Configure Minimum and Maximum Memory Constraints for a Namespace
-content_template: templates/task
+content_type: task
 weight: 30
 ---


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

 This page shows how to set minimum and maximum values for memory used by Containers
 running in a namespace. You specify minimum and maximum memory values in a
@@ -13,19 +13,20 @@ running in a namespace. You specify minimum and maximum memory values in a
 object. If a Pod does not meet the constraints imposed by the LimitRange,
 it cannot be created in the namespace.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 Each node in your cluster must have at least 1 GiB of memory.

-{{% /capture %}}


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

 ## Create a namespace

@@ -239,9 +240,10 @@ Delete your namespace:
 kubectl delete namespace constraints-mem-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -265,7 +267,7 @@ kubectl delete namespace constraints-mem-example

 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)

-{{% /capture %}}
+



@@ -1,27 +1,28 @@
 ---
 title: Configure Default Memory Requests and Limits for a Namespace
-content_template: templates/task
+content_type: task
 weight: 10
 ---

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

 This page shows how to configure default memory requests and limits for a namespace.
 If a Container is created in a namespace that has a default memory limit, and the Container
 does not specify its own memory limit, then the Container is assigned the default memory limit.
 Kubernetes assigns a default memory request under certain conditions that are explained later in this topic.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 Each node in your cluster must have at least 2 GiB of memory.

-{{% /capture %}}

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

 ## Create a namespace

@@ -170,9 +171,10 @@ Delete your namespace:
 kubectl delete namespace default-mem-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -196,6 +198,6 @@ kubectl delete namespace default-mem-example

 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)

-{{% /capture %}}
+


@@ -1,30 +1,31 @@
 ---
 title: Configure Memory and CPU Quotas for a Namespace
-content_template: templates/task
+content_type: task
 weight: 50
 ---


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

 This page shows how to set quotas for the total amount memory and CPU that
 can be used by all Containers running in a namespace. You specify quotas in a
 [ResourceQuota](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcequota-v1-core)
 object.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 Each node in your cluster must have at least 1 GiB of memory.

-{{% /capture %}}


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

 ## Create a namespace

@@ -146,9 +147,10 @@ Delete your namespace:
 kubectl delete namespace quota-mem-cpu-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -172,7 +174,7 @@ kubectl delete namespace quota-mem-cpu-example

 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)

-{{% /capture %}}
+



@@ -1,28 +1,29 @@
 ---
 title: Configure a Pod Quota for a Namespace
-content_template: templates/task
+content_type: task
 weight: 60
 ---


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

 This page shows how to set a quota for the total number of Pods that can run
 in a namespace. You specify quotas in a
 [ResourceQuota](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcequota-v1-core)
 object.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ## Create a namespace

@@ -107,9 +108,10 @@ Delete your namespace:
 kubectl delete namespace quota-pod-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -133,7 +135,7 @@ kubectl delete namespace quota-pod-example

 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)

-{{% /capture %}}
+



@@ -3,10 +3,10 @@ reviewers:
 - derekwaynecarr
 - janetkuo
 title: Namespaces Walkthrough
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 Kubernetes {{< glossary_tooltip text="namespaces" term_id="namespace" >}}
 help different projects, teams, or customers to share a Kubernetes cluster.

@@ -19,16 +19,17 @@ Use of multiple namespaces is optional.

 This example demonstrates how to use Kubernetes namespaces to subdivide your cluster.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Prerequisites

@@ -295,4 +296,4 @@ At this point, it should be clear that the resources users create in one namespa
 As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
 authorization rules for each namespace.

-{{% /capture %}}
+
@@ -3,19 +3,20 @@ reviewers:
 - derekwaynecarr
 - janetkuo
 title: Share a Cluster with Namespaces
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to view, work in, and delete {{< glossary_tooltip text="namespaces" term_id="namespace" >}}. The page also shows how to use Kubernetes namespaces to subdivide your cluster.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 * Have an [existing Kubernetes cluster](/docs/setup/).
 * Have a basic understanding of Kubernetes _[Pods](/docs/concepts/workloads/pods/pod/)_, _[Services](/docs/concepts/services-networking/service/)_, and _[Deployments](/docs/concepts/workloads/controllers/deployment/)_.
-{{% /capture %}}

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

 ## Viewing namespaces

@@ -252,9 +253,9 @@ At this point, it should be clear that the resources users create in one namespa
 As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
 authorization rules for each namespace.

-{{% /capture %}}

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

 ## Understanding the motivation for using namespaces

@@ -304,12 +305,13 @@ is local to a namespace.  This is useful for using the same configuration across
 multiple namespaces such as Development, Staging and Production.  If you want to reach
 across namespaces, you need to use the fully qualified domain name (FQDN).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Learn more about [setting the namespace preference](/docs/concepts/overview/working-with-objects/namespaces/#setting-the-namespace-preference).
 * Learn more about [setting the namespace for a request](/docs/concepts/overview/working-with-objects/namespaces/#setting-the-namespace-for-a-request)
 * See [namespaces design](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/design-proposals/architecture/namespaces.md).
-{{% /capture %}}
+


@@ -2,19 +2,20 @@
 reviewers:
 - caseydavenport
 title: Use Calico for NetworkPolicy
-content_template: templates/task
+content_type: task
 weight: 10
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows a couple of quick ways to create a Calico cluster on Kubernetes.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 Decide whether you want to deploy a [cloud](#creating-a-calico-cluster-with-google-kubernetes-engine-gke) or [local](#creating-a-local-calico-cluster-with-kubeadm) cluster.
-{{% /capture %}}

-{{% capture steps %}}
+
+<!-- steps -->
 ## Creating a Calico cluster with Google Kubernetes Engine (GKE)

 **Prerequisite**: [gcloud](https://cloud.google.com/sdk/docs/quickstarts).
@@ -44,10 +45,11 @@ Decide whether you want to deploy a [cloud](#creating-a-calico-cluster-with-goog
 To get a local single-host Calico cluster in fifteen minutes using kubeadm, refer to the 
 [Calico Quickstart](https://docs.projectcalico.org/latest/getting-started/kubernetes/).

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Once your cluster is running, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy.
-{{% /capture %}}
+

@@ -3,23 +3,24 @@ reviewers:
 - danwent
 - aanm
 title: Use Cilium for NetworkPolicy
-content_template: templates/task
+content_type: task
 weight: 20
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to use Cilium for NetworkPolicy.

 For background on Cilium, read the [Introduction to Cilium](https://docs.cilium.io/en/stable/intro).
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

-{{% capture steps %}}
+
+<!-- steps -->
 ## Deploying Cilium on Minikube for Basic Testing

 To get familiar with Cilium easily you can follow the
@@ -75,9 +76,9 @@ For detailed instructions around deploying Cilium for production, see:
 This documentation includes detailed requirements, instructions and example
 production DaemonSet files.

-{{% /capture %}}

-{{% capture discussion %}}
+
+<!-- discussion -->
 ##  Understanding Cilium components

 Deploying a cluster with Cilium adds Pods to the `kube-system` namespace. To see
@@ -98,14 +99,15 @@ cilium-6rxbd    1/1     Running   0          1m
 A `cilium` Pod runs on each node in your cluster and enforces network policy
 on the traffic to/from Pods on that node using Linux BPF.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Once your cluster is running, you can follow the
 [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/)
 to try out Kubernetes NetworkPolicy with Cilium.
 Have fun, and if you have questions, contact us using the
 [Cilium Slack Channel](https://cilium.herokuapp.com/).
-{{% /capture %}}
+


@@ -2,25 +2,27 @@
 reviewers:
 - murali-reddy
 title: Use Kube-router for NetworkPolicy
-content_template: templates/task
+content_type: task
 weight: 30
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to use [Kube-router](https://github.com/cloudnativelabs/kube-router) for NetworkPolicy.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 You need to have a Kubernetes cluster running. If you do not already have a cluster, you can create one by using any of the cluster installers like Kops, Bootkube, Kubeadm etc.
-{{% /capture %}}

-{{% capture steps %}}
+
+<!-- steps -->
 ## Installing Kube-router addon
 The Kube-router Addon comes with a Network Policy Controller that watches Kubernetes API server for any NetworkPolicy and pods updated and configures iptables rules and ipsets to allow or block traffic as directed by the policies. Please follow the [trying Kube-router with cluster installers](https://www.kube-router.io/docs/user-guide/#try-kube-router-with-cluster-installers) guide to install Kube-router addon.
-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Once you have installed the Kube-router addon, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy.
-{{% /capture %}}
+


@@ -2,23 +2,24 @@
 reviewers:
 - chrismarino
 title: Romana for NetworkPolicy
-content_template: templates/task
+content_type: task
 weight: 40
 ---

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

 This page shows how to use Romana for NetworkPolicy.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 Complete steps 1, 2, and 3 of the [kubeadm getting started guide](/docs/getting-started-guides/kubeadm/).

-{{% /capture %}}

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

 ## Installing Romana with kubeadm

@@ -32,12 +33,13 @@ To apply network policies use one of the following:
    * [Example of Romana network policy](https://github.com/romana/core/blob/master/doc/policy.md).
 * The NetworkPolicy API.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Once you have installed Romana, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy.

-{{% /capture %}}
+


@@ -2,23 +2,24 @@
 reviewers:
 - bboreham
 title: Weave Net for NetworkPolicy
-content_template: templates/task
+content_type: task
 weight: 50
 ---

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

 This page shows how to use Weave Net for NetworkPolicy.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 You need to have a Kubernetes cluster. Follow the [kubeadm getting started guide](/docs/getting-started-guides/kubeadm/) to bootstrap one.

-{{% /capture %}}

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

 ## Install the Weave Net addon

@@ -48,12 +49,13 @@ weave-net-pmw8w                         2/2       Running   0          9d

 Each Node has a weave Pod, and all Pods are `Running` and `2/2 READY`. (`2/2` means that each Pod has `weave` and `weave-npc`.)

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Once you have installed the Weave Net addon, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy. If you have any question, contact us at [#weave-community on Slack or Weave User Group](https://github.com/weaveworks/weave#getting-help).

-{{% /capture %}}
+


@@ -4,21 +4,22 @@ reviewers:
 - zihongz
 - sftim
 title: Using NodeLocal DNSCache in Kubernetes clusters
-content_template: templates/task
+content_type: task
 ---
-
-{{% capture overview %}}
+ 
+<!-- overview -->
 {{< feature-state for_k8s_version="v1.18" state="stable" >}}
 This page provides an overview of NodeLocal DNSCache feature in Kubernetes.
-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

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

 ## Introduction

@@ -88,4 +89,4 @@ This feature can be enabled using the following steps:
 Once enabled, node-local-dns Pods will run in the kube-system namespace on each of the cluster nodes. This Pod runs [CoreDNS](https://github.com/coredns/coredns) in cache mode, so all CoreDNS metrics exposed by the different plugins will be available on a per-node basis.

 You can disable this feature by removing the DaemonSet, using `kubectl delete -f <manifest>` . You should also revert any changes you made to the kubelet configuration.
- {{% /capture %}}
+ 
@@ -4,10 +4,10 @@ reviewers:
 - vishh
 - timstclair
 title: Configure Out of Resource Handling
-content_template: templates/concept
+content_type: concept
 ---

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

 This page explains how to configure out of resource handling with `kubelet`.

@@ -16,10 +16,10 @@ are low. This is especially important when dealing with incompressible
 compute resources, such as memory or disk space. If such resources are exhausted,
 nodes become unstable.

-{{% /capture %}}


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

 ## Eviction Policy

@@ -372,4 +372,4 @@ to prevent system OOMs, and promote eviction of workloads so cluster state can r
 The Pod eviction may evict more Pods than needed due to stats collection timing gap. This can be mitigated by adding
 the ability to get root container stats on an on-demand basis [(https://github.com/google/cadvisor/issues/1247)](https://github.com/google/cadvisor/issues/1247) in the future.

-{{% /capture %}}
+
@@ -1,10 +1,10 @@
 ---
 title: Configure Quotas for API Objects
-content_template: templates/task
+content_type: task
 ---


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

 This page shows how to configure quotas for API objects, including
 PersistentVolumeClaims and Services. A quota restricts the number of
@@ -13,17 +13,18 @@ You specify quotas in a
 [ResourceQuota](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcequota-v1-core)
 object.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ## Create a namespace

@@ -140,9 +141,10 @@ Delete your namespace:
 kubectl delete namespace quota-object-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For cluster administrators

@@ -167,7 +169,7 @@ kubectl delete namespace quota-object-example
 * [Configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/)


-{{% /capture %}}
+



@@ -3,11 +3,11 @@ reviewers:
 - mtaufen
 - dawnchen
 title: Reconfigure a Node's Kubelet in a Live Cluster
-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: v1.11
 ---

-{{% capture overview %}}
+<!-- overview -->
 {{< feature-state for_k8s_version="v1.11" state="beta" >}}

 [Dynamic Kubelet Configuration](https://github.com/kubernetes/enhancements/issues/281)
@@ -25,9 +25,10 @@ of nodes before rolling them out cluster-wide. Advice on configuring specific
 fields is available in the inline `KubeletConfiguration`
 [type documentation](https://github.com/kubernetes/kubernetes/blob/release-1.11/pkg/kubelet/apis/kubeletconfig/v1beta1/types.go).
 {{< /warning >}}
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 You need to have a Kubernetes cluster.
 You also need kubectl v1.11 or higher, configured to communicate with your cluster.
 {{< version-check >}}
@@ -43,9 +44,9 @@ because there are manual alternatives.

 For each node that you're reconfiguring, you must set the kubelet
 `--dynamic-config-dir` flag to a writable directory.
-{{% /capture %}}

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

 ## Reconfiguring the kubelet on a running node in your cluster

@@ -311,9 +312,9 @@ empty, since all config sources have been reset to `nil`, which indicates that
 the local default config is `assigned`, `active`, and `lastKnownGood`, and no
 error is reported.

-{{% /capture %}}

-{{% capture discussion %}}
+
+<!-- discussion -->
 ## `kubectl patch` example

 You can change a Node's configSource using several different mechanisms.
@@ -374,9 +375,9 @@ internal failure, see Kubelet log for details | The kubelet encountered some int

 {{< /table >}}

-{{% /capture %}}
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 - For more information on configuring the kubelet via a configuration file, see
 [Set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file).
 - See the reference documentation for [`NodeConfigSource`](https://kubernetes.io/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#nodeconfigsource-v1-core)
-{{% /capture %}}
@@ -4,11 +4,11 @@ reviewers:
 - derekwaynecarr
 - dashpole
 title: Reserve Compute Resources for System Daemons
-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: 1.8
 ---

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

 Kubernetes nodes can be scheduled to `Capacity`. Pods can consume all the
 available capacity on a node by default. This is an issue because nodes
@@ -22,19 +22,20 @@ compute resources for system daemons. Kubernetes recommends cluster
 administrators to configure `Node Allocatable` based on their workload density
 on each node.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 Your Kubernetes server must be at or later than version 1.17 to use
 the kubelet command line option `--reserved-cpus` to set an
 [explicitly reserved CPU list](#explicitly-reserved-cpu-list).

-{{% /capture %}}

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

 ## Node Allocatable

@@ -226,9 +227,9 @@ more features are added. Over time, kubernetes project will attempt to bring
 down utilization of node system daemons, but that is not a priority as of now.
 So expect a drop in `Allocatable` capacity in future releases.

-{{% /capture %}}

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

 ## Example Scenario

@@ -251,4 +252,3 @@ If `kube-reserved` and/or `system-reserved` is not enforced and system daemons
 exceed their reservation, `kubelet` evicts pods whenever the overall node memory
 usage is higher than `31.5Gi` or `storage` is greater than `90Gi`

-{{% /capture %}}
@@ -4,10 +4,10 @@ reviewers:
 - thockin
 - wlan0
 title: Cloud Controller Manager Administration
-content_template: templates/concept
+content_type: concept
 ---

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

 {{< feature-state state="beta" for_k8s_version="v1.11" >}}

@@ -15,10 +15,10 @@ Since cloud providers develop and release at a different pace compared to the Ku

 The `cloud-controller-manager` can be linked to any cloud provider that satisfies [cloudprovider.Interface](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go). For backwards compatibility, the [cloud-controller-manager](https://github.com/kubernetes/kubernetes/tree/master/cmd/cloud-controller-manager) provided in the core Kubernetes project uses the same cloud libraries as `kube-controller-manager`. Cloud providers already supported in Kubernetes core are expected to use the in-tree cloud-controller-manager to transition out of Kubernetes core.

-{{% /capture %}}


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

 ## Administration

@@ -82,9 +82,10 @@ A good example of this is the TLS bootstrapping feature in the Kubelet. TLS boot

 As this initiative evolves, changes will be made to address these issues in upcoming releases.

-{{% /capture %}}
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 To build and develop your own cloud controller manager, read [Developing Cloud Controller Manager](/docs/tasks/administer-cluster/developing-cloud-controller-manager/).

-{{% /capture %}}
+
@@ -5,14 +5,15 @@ reviewers:
 - foxish
 - kow3ns
 title: Safely Drain a Node while Respecting the PodDisruptionBudget
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to safely drain a node, respecting the PodDisruptionBudget you have defined.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 This task assumes that you have met the following prerequisites:

@@ -24,9 +25,9 @@ This task assumes that you have met the following prerequisites:
     and [Configured PodDisruptionBudgets](/docs/tasks/run-application/configure-pdb/) for
     applications that need them.

-{{% /capture %}}

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

 ## Use `kubectl drain` to remove a node from service

@@ -151,13 +152,14 @@ In this case, there are two potential solutions:
 Kubernetes does not specify what the behavior should be in this case; it is up to the
 application owners and cluster owners to establish an agreement on behavior in these cases.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Follow steps to protect your application by [configuring a Pod Disruption Budget](/docs/tasks/run-application/configure-pdb/).
 * Learn more about [maintenance on a node](/docs/tasks/administer-cluster/cluster-management/#maintenance-on-a-node).

-{{% /capture %}}
+


@@ -5,23 +5,24 @@ reviewers:
 - ericchiang
 - destijl
 title: Securing a Cluster
-content_template: templates/task
+content_type: task
 ---

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

 This document covers topics related to protecting a cluster from accidental or malicious access
 and provides recommendations on overall security.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Controlling access to the Kubernetes API

@@ -254,6 +255,6 @@ Join the [kubernetes-announce](https://groups.google.com/forum/#!forum/kubernete
 group for emails about security announcements. See the [security reporting](/security/)
 page for more on how to report vulnerabilities.

-{{% /capture %}}
+


@@ -2,25 +2,26 @@
 title: Using sysctls in a Kubernetes Cluster
 reviewers:
 - sttts
-content_template: templates/task
+content_type: task
 ---

-{{% capture overview %}}
+<!-- overview -->
 {{< feature-state for_k8s_version="v1.12" state="beta" >}}

 This document describes how to configure and use kernel parameters within a
 Kubernetes cluster using the {{< glossary_tooltip term_id="sysctl" >}}
 interface.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Listing all Sysctl Parameters

@@ -140,9 +141,9 @@ spec:
      value: "65536"
  ...
 ```
-{{% /capture %}}

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

 {{< warning >}}
 Due to their nature of being _unsafe_, the use of _unsafe_ sysctls
@@ -210,4 +211,4 @@ spec:
 ...
 ```

-{{% /capture %}}
+
@@ -8,11 +8,11 @@ reviewers:
 - nolancon
 - bg-chun

-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: v1.18
 ---

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

 {{< feature-state state="beta" for_k8s_version="v1.18" >}}

@@ -22,15 +22,16 @@ In order to extract the best performance, optimizations related to CPU isolation

 _Topology Manager_ is a Kubelet component that aims to co-ordinate the set of components that are responsible for these optimizations.
 
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## How Topology Manager Works

@@ -216,4 +217,4 @@ Using this information the Topology Manager calculates the optimal hint for the

 3. The Device Manager and the CPU Manager are the only components to adopt the Topology Manager's HintProvider interface. This means that NUMA alignment can only be achieved for resources managed by the CPU Manager and the Device Manager. Memory or Hugepages are not considered by the Topology Manager for NUMA alignment.

-{{% /capture %}}
+
@@ -1,20 +1,21 @@
 ---
 title: Assign CPU Resources to Containers and Pods
-content_template: templates/task
+content_type: task
 weight: 20
 ---

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

 This page shows how to assign a CPU *request* and a CPU *limit* to
 a container. Containers cannot use more CPU than the configured limit.
 Provided the system has CPU time free, a container is guaranteed to be
 allocated as much CPU as it requests.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -48,10 +49,10 @@ NAME
 v1beta1.metrics.k8s.io
 ```

-{{% /capture %}}


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

 ## Create a namespace

@@ -239,9 +240,10 @@ Delete your namespace:
 kubectl delete namespace cpu-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+


 ### For app developers
@@ -266,4 +268,4 @@ kubectl delete namespace cpu-example

 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)

-{{% /capture %}}
+
@@ -1,19 +1,20 @@
 ---
 title: Assign Memory Resources to Containers and Pods
-content_template: templates/task
+content_type: task
 weight: 10
 ---

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

 This page shows how to assign a memory *request* and a memory *limit* to a
 Container. A Container is guaranteed to have as much memory as it requests,
 but is not allowed to use more memory than its limit.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -46,9 +47,9 @@ NAME
 v1beta1.metrics.k8s.io
 ```

-{{% /capture %}}

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

 ## Create a namespace

@@ -330,9 +331,10 @@ Delete your namespace. This deletes all the Pods that you created for this task:
 kubectl delete namespace mem-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For app developers

@@ -356,7 +358,7 @@ kubectl delete namespace mem-example

 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)

-{{% /capture %}}
+



@@ -1,22 +1,23 @@
 ---
 title: Assign Pods to Nodes using Node Affinity
 min-kubernetes-server-version: v1.10
-content_template: templates/task
+content_type: task
 weight: 120
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to assign a Kubernetes Pod to a particular node using Node Affinity in a
 Kubernetes cluster.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Add a label to a node

@@ -112,9 +113,10 @@ This means that the pod will prefer a node that has a `disktype=ssd` label.
    nginx    1/1       Running   0          13s    10.200.0.4   worker0
    ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 Learn more about
 [Node Affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity).
-{{% /capture %}}
+
@@ -1,21 +1,22 @@
 ---
 title: Assign Pods to Nodes
-content_template: templates/task
+content_type: task
 weight: 120
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to assign a Kubernetes Pod to a particular node in a
 Kubernetes cluster.
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Add a label to a node

@@ -94,10 +95,11 @@ You can also schedule a pod to one specific node via setting `nodeName`.

 Use the configuration file to create a pod that will get scheduled on `foo-node` only.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Learn more about [labels and selectors](/docs/concepts/overview/working-with-objects/labels/).
 * Learn more about [nodes](/docs/concepts/architecture/nodes/).
-{{% /capture %}}
+

@@ -1,27 +1,28 @@
 ---
 title: Attach Handlers to Container Lifecycle Events
-content_template: templates/task
+content_type: task
 weight: 140
 ---

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

 This page shows how to attach handlers to Container lifecycle events. Kubernetes supports
 the postStart and preStop events. Kubernetes sends the postStart event immediately
 after a Container is started, and it sends the preStop event immediately before the
 Container is terminated.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ## Define postStart and preStop handlers

@@ -56,11 +57,11 @@ The output shows the text written by the postStart handler:

    Hello from the postStart handler

-{{% /capture %}}



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

 ## Discussion

@@ -82,10 +83,11 @@ This means that the preStop hook is not invoked when the Pod is *completed*.
 This limitation is tracked in [issue #55087](https://github.com/kubernetes/kubernetes/issues/55807).
 {{< /note >}}

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/).
 * Learn more about the [lifecycle of a Pod](/docs/concepts/workloads/pods/pod-lifecycle/).
@@ -97,6 +99,6 @@ This limitation is tracked in [issue #55087](https://github.com/kubernetes/kuber
 * [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core)
 * See `terminationGracePeriodSeconds` in [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)

-{{% /capture %}}
+


@@ -1,10 +1,10 @@
 ---
 title: Configure GMSA for Windows Pods and containers
-content_template: templates/task
+content_type: task
 weight: 20
 ---

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

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

@@ -12,9 +12,10 @@ This page shows how to configure [Group Managed Service Accounts](https://docs.m

 In Kubernetes, GMSA credential specs are configured at a Kubernetes cluster-wide scope as Custom Resources. Windows Pods, as well as individual containers within a Pod, can be configured to use a GMSA for domain based functions (e.g. Kerberos authentication) when interacting with other Windows services. As of v1.16, the Docker runtime supports GMSA for Windows workloads.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 You need to have a Kubernetes cluster and the `kubectl` command-line tool must be configured to communicate with your cluster. The cluster is expected to have Windows worker nodes. This section covers a set of initial steps required once for each cluster:

@@ -43,9 +44,9 @@ A [script](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission

 The [YAML template](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/gmsa-webhook.yml.tpl) used by the script may also be used to deploy the webhooks and associated objects manually (with appropriate substitutions for the parameters)

-{{% /capture %}}

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

 ## Configure GMSAs and Windows nodes in Active Directory
 Before Pods in Kubernetes can be configured to use GMSAs, the desired GMSAs need to be provisioned in Active Directory as described in the [Windows GMSA documentation](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#BKMK_Step1). Windows worker nodes (that are part of the Kubernetes cluster) need to be configured in Active Directory to access the secret credentials associated with the desired GMSA as described in the [Windows GMSA documentation](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#to-add-member-hosts-using-the-set-adserviceaccount-cmdlet)
@@ -252,4 +253,4 @@ If the above command corrects the error, you can automate the step by adding the

 If you add the `lifecycle` section show above to your Pod spec, the Pod will execute the commands listed to restart the `netlogon` service until the `nltest.exe /query` command exits without error.

-{{% /capture %}}
+
@@ -1,10 +1,10 @@
 ---
 title: Configure Liveness, Readiness and Startup Probes
-content_template: templates/task
+content_type: task
 weight: 110
 ---

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

 This page shows how to configure liveness, readiness and startup probes for containers.

@@ -25,15 +25,16 @@ it succeeds, making sure those probes don't interfere with the application start
 This can be used to adopt liveness checks on slow starting containers, avoiding them
 getting killed by the kubelet before they are up and running.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Define a liveness command

@@ -360,9 +361,10 @@ For a TCP probe, the kubelet makes the probe connection at the node, not in the
 means that you can not use a service name in the `host` parameter since the kubelet is unable
 to resolve it.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about
 [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
@@ -373,6 +375,6 @@ You can also read the API references for:
 * [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core)
 * [Probe](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#probe-v1-core)

-{{% /capture %}}
+


@@ -1,10 +1,10 @@
 ---
 title: Configure a Pod to Use a PersistentVolume for Storage
-content_template: templates/task
+content_type: task
 weight: 60
 ---

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

 This page shows you how to configure a Pod to use a
 {{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}}
@@ -20,9 +20,10 @@ PersistentVolume.

 1. You create a Pod that uses the above PersistentVolumeClaim for storage.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * You need to have a Kubernetes cluster that has only one Node, and the
 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}}
@@ -33,9 +34,9 @@ do not already have a single-node cluster, you can create one by using
 * Familiarize yourself with the material in
 [Persistent Volumes](/docs/concepts/storage/persistent-volumes/).

-{{% /capture %}}

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

 ## Create an index.html file on your Node

@@ -237,10 +238,10 @@ sudo rmdir /mnt/data

 You can now close the shell to your Node.

-{{% /capture %}}


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

 ## Access control

@@ -270,10 +271,11 @@ When a Pod consumes a PersistentVolume, the GIDs associated with the
 PersistentVolume are not present on the Pod resource itself.
 {{< /note >}}

-{{% /capture %}}


-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about [PersistentVolumes](/docs/concepts/storage/persistent-volumes/).
 * Read the [Persistent Storage design document](https://git.k8s.io/community/contributors/design-proposals/storage/persistent-storage.md).
@@ -285,6 +287,6 @@ PersistentVolume are not present on the Pod resource itself.
 * [PersistentVolumeClaim](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#persistentvolumeclaim-v1-core)
 * [PersistentVolumeClaimSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#persistentvolumeclaimspec-v1-core)

-{{% /capture %}}
+


@@ -1,24 +1,25 @@
 ---
 title: Configure a Pod to Use a ConfigMap
-content_template: templates/task
+content_type: task
 weight: 150
 card:
  name: tasks
  weight: 50
 ---

-{{% capture overview %}}
+<!-- overview -->
 ConfigMaps allow you to decouple configuration artifacts from image content to keep containerized applications portable. This page provides a series of usage examples demonstrating how to create ConfigMaps and configure Pods using data stored in ConfigMaps.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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


 ## Create a ConfigMap
@@ -628,9 +629,9 @@ When a ConfigMap already being consumed in a volume is updated, projected keys a
 A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive ConfigMap updates.
 {{< /note >}}

-{{% /capture %}}

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

 ## Understanding ConfigMaps and Pods

@@ -680,9 +681,10 @@ data:

 - You can't use ConfigMaps for {{< glossary_tooltip text="static pods" term_id="static-pod" >}}, because the Kubelet does not support this.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).

-{{% /capture %}}
+
@@ -1,22 +1,23 @@
 ---
 title: Configure Pod Initialization
-content_template: templates/task
+content_type: task
 weight: 130
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to use an Init Container to initialize a Pod before an
 application Container runs.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Create a Pod that has an Init Container

@@ -78,9 +79,10 @@ The output shows that nginx is serving the web page that was written by the init
      <p>Kubernetes is open source giving you the freedom to take advantage ...</p>
      ...

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about
 [communicating between Containers running in the same Pod](/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/).
@@ -88,6 +90,6 @@ The output shows that nginx is serving the web page that was written by the init
 * Learn more about [Volumes](/docs/concepts/storage/volumes/).
 * Learn more about [Debugging Init Containers](/docs/tasks/debug-application-cluster/debug-init-containers/)

-{{% /capture %}}
+


@@ -3,11 +3,11 @@ reviewers:
 - jpeeler
 - pmorie
 title: Configure a Pod to Use a Projected Volume for Storage
-content_template: templates/task
+content_type: task
 weight: 70
 ---

-{{% capture overview %}}
+<!-- overview -->
 This page shows how to use a [`projected`](/docs/concepts/storage/volumes/#projected) Volume to mount
 several existing volume sources into the same directory. Currently, `secret`, `configMap`, `downwardAPI`,
 and `serviceAccountToken` volumes can be projected.
@@ -15,13 +15,14 @@ and `serviceAccountToken` volumes can be projected.
 {{< note >}}
 `serviceAccountToken` is not a volume type.
 {{< /note >}}
-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-{{% /capture %}}

-{{% capture steps %}}
+
+<!-- steps -->
 ## Configure a projected volume for a pod

 In this exercise, you create username and password {{< glossary_tooltip text="Secrets" term_id="secret" >}} from local files. You then create a Pod that runs one container, using a [`projected`](/docs/concepts/storage/volumes/#projected) Volume to mount the Secrets into the same shared directory.
@@ -77,9 +78,10 @@ kubectl delete pod test-projected-volume
 kubectl delete secret user pass
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * Learn more about [`projected`](/docs/concepts/storage/volumes/#projected) volumes.
 * Read the [all-in-one volume](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/design-proposals/node/all-in-one-volume.md) design document.
-{{% /capture %}}
+
@@ -1,24 +1,25 @@
 ---
 title: Configure RunAsUserName for Windows pods and containers
-content_template: templates/task
+content_type: task
 weight: 20
 ---

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

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

 This page shows how to use the `runAsUserName` setting for Pods and containers that will run on Windows nodes. This is roughly equivalent of the Linux-specific `runAsUser` setting, allowing you to run applications in a container as a different username than the default.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 You need to have a Kubernetes cluster and the kubectl command-line tool must be configured to communicate with your cluster. The cluster is expected to have Windows worker nodes where pods with containers running Windows workloads will get scheduled.

-{{% /capture %}}

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

 ## Set the Username for a Pod

@@ -114,12 +115,12 @@ Examples of acceptable values for the `runAsUserName` field: `ContainerAdministr

 For more information about these limtations, check [here](https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and) and [here](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/new-localuser?view=powershell-5.1).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * [Guide for scheduling Windows containers in Kubernetes](/docs/setup/production-environment/windows/user-guide-windows-containers/)
 * [Managing Workload Identity with Group Managed Service Accounts (GMSA)](/docs/setup/production-environment/windows/user-guide-windows-containers/#managing-workload-identity-with-group-managed-service-accounts)
 * [Configure GMSA for Windows pods and containers](/docs/tasks/configure-pod-container/configure-gmsa/)

-{{% /capture %}}
@@ -4,11 +4,11 @@ reviewers:
 - liggitt
 - thockin
 title: Configure Service Accounts for Pods
-content_template: templates/task
+content_type: task
 weight: 90
 ---

-{{% capture overview %}}
+<!-- overview -->
 A service account provides an identity for processes that run in a Pod.

 {{< note >}}
@@ -23,16 +23,17 @@ authenticated by the apiserver as a particular User Account (currently this is
 usually `admin`, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver.
 When they do, they are authenticated as a particular Service Account (for example, `default`).

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Use the Default Service Account to access the API server.

@@ -370,9 +371,10 @@ override the `jwks_uri` in the OpenID Provider Configuration so that it points
 to the public endpoint, rather than the API server's address, by passing the
 `--service-account-jwks-uri` flag to the API server. Like the issuer URL, the
 JWKS URI is required to use the `https` scheme.
-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 See also:

@@ -380,4 +382,4 @@ See also:
 - [Service Account Signing Key Retrieval KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/20190730-oidc-discovery.md)
 - [OIDC Discovery Spec](https://openid.net/specs/openid-connect-discovery-1_0.html)

-{{% /capture %}}
+
@@ -1,10 +1,10 @@
 ---
 title: Configure a Pod to Use a Volume for Storage
-content_template: templates/task
+content_type: task
 weight: 50
 ---

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

 This page shows how to configure a Pod to use a Volume for storage.

@@ -14,15 +14,16 @@ consistent storage that is independent of the Container, you can use a
 [Volume](/docs/concepts/storage/volumes/). This is especially important for stateful
 applications, such as key-value stores (such as Redis) and databases. 

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Configure a volume for a Pod

@@ -126,9 +127,10 @@ of `Always`.
    kubectl delete pod redis
    ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * See [Volume](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#volume-v1-core).

@@ -140,6 +142,6 @@ GCE and EBS on EC2, which are preferred for critical data and will handle
 details such as mounting and unmounting the devices on the nodes. See
 [Volumes](/docs/concepts/storage/volumes/) for more details.

-{{% /capture %}}
+


@@ -1,19 +1,20 @@
 ---
 title: Assign Extended Resources to a Container
-content_template: templates/task
+content_type: task
 weight: 40
 ---

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

 {{< feature-state state="stable" >}}

 This page shows how to assign extended resources to a Container.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -21,10 +22,10 @@ Before you do this exercise, do the exercise in
 [Advertise Extended Resources for a Node](/docs/tasks/administer-cluster/extended-resource-node/).
 That will configure one of your Nodes to advertise a dongle resource.

-{{% /capture %}}


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

 ## Assign an extended resource to a Pod

@@ -127,9 +128,10 @@ kubectl delete pod extended-resource-demo
 kubectl delete pod extended-resource-demo-2
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 ### For application developers

@@ -140,4 +142,4 @@ kubectl delete pod extended-resource-demo-2

 * [Advertise Extended Resources for a Node](/docs/tasks/administer-cluster/extended-resource-node/)

-{{% /capture %}}
+
@@ -1,26 +1,27 @@
 ---
 title: Pull an Image from a Private Registry
-content_template: templates/task
+content_type: task
 weight: 100
 ---

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

 This page shows how to create a Pod that uses a Secret to pull an image from a
 private Docker registry or repository.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 * To do this exercise, you need a
 [Docker ID](https://docs.docker.com/docker-id/) and password.

-{{% /capture %}}

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

 ## Log in to Docker

@@ -200,9 +201,10 @@ kubectl apply -f my-private-reg-pod.yaml
 kubectl get pod private-reg
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * Learn more about [Secrets](/docs/concepts/configuration/secret/).
 * Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
@@ -211,5 +213,5 @@ kubectl get pod private-reg
 * See [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core).
 * See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).

-{{% /capture %}}
+

@@ -1,27 +1,28 @@
 ---
 title: Configure Quality of Service for Pods
-content_template: templates/task
+content_type: task
 weight: 30
 ---


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

 This page shows how to configure Pods so that they will be assigned particular
 Quality of Service (QoS) classes. Kubernetes uses QoS classes to make decisions about
 scheduling and evicting Pods.

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}


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

 ## QoS classes

@@ -235,9 +236,10 @@ Delete your namespace:
 kubectl delete namespace qos-example
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+


 ### For app developers
@@ -263,7 +265,7 @@ kubectl delete namespace qos-example
 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)

 * [Control Topology Management policies on a node](/docs/tasks/administer-cluster/topology-manager/)
-{{% /capture %}}
+



@@ -4,11 +4,11 @@ reviewers:
 - mikedanese
 - thockin
 title: Configure a Security Context for a Pod or Container
-content_template: templates/task
+content_type: task
 weight: 80
 ---

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

 A security context defines privilege and access control settings for
 a Pod or Container. Security context settings include, but are not limited to:
@@ -37,15 +37,16 @@ for a comprehensive list.
 For more information about security mechanisms in Linux, see
 [Overview of Linux Kernel Security Features](https://www.linux.com/learn/overview-linux-kernel-security-features)

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Set the security context for a Pod

@@ -409,9 +410,10 @@ kubectl delete pod security-context-demo-3
 kubectl delete pod security-context-demo-4
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 * [PodSecurityContext](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podsecuritycontext-v1-core)
 * [SecurityContext](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#securitycontext-v1-core)
@@ -423,4 +425,4 @@ kubectl delete pod security-context-demo-4
  document](https://git.k8s.io/community/contributors/design-proposals/auth/no-new-privs.md)


-{{% /capture %}}
+
@@ -5,11 +5,11 @@ reviewers:
 - verb
 - yujuhong
 - dchen1107
-content_template: templates/task
+content_type: task
 weight: 160
 ---

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

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

@@ -21,15 +21,16 @@ You can use this feature to configure cooperating containers, such as a log
 handler sidecar container, or to troubleshoot container images that don't
 include debugging utilities like a shell.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Configure a Pod

@@ -93,9 +94,9 @@ events {
    worker_connections  1024;
 ```

-{{% /capture %}}

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

 ## Understanding Process Namespace Sharing

@@ -117,6 +118,6 @@ containers, though, so it's important to understand these differences:
   `/proc/$pid/root` link.** This makes debugging easier, but it also means
   that filesystem secrets are protected only by filesystem permissions.

-{{% /capture %}}
+


@@ -3,10 +3,10 @@ reviewers:
 - jsafrane
 title: Create static Pods
 weight: 170
-content_template: templates/task
+content_type: task
 ---

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


 *Static Pods* are managed directly by the kubelet daemon on a specific node,
@@ -30,9 +30,10 @@ Pods to run a Pod on every node, you should probably be using a
 instead.
 {{< /note >}}

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -41,10 +42,10 @@ and that your nodes are running the Fedora operating system.
 Instructions for other distributions or Kubernetes installations may vary.


-{{% /capture %}}


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

 ## Create a static pod {#static-pod-creation}

@@ -236,4 +237,4 @@ CONTAINER ID        IMAGE         COMMAND                CREATED           ...
 e7a62e3427f1        nginx:latest  "nginx -g 'daemon of   27 seconds ago
 ```

-{{% /capture %}}
+
@@ -2,26 +2,27 @@
 reviewers:
 - cdrage
 title: Translate a Docker Compose File to Kubernetes Resources
-content_template: templates/task
+content_type: task
 weight: 200
 ---

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

 What's Kompose? It's a conversion tool for all things compose (namely Docker Compose) to container orchestrators (Kubernetes or OpenShift).

 More information can be found on the Kompose website at [http://kompose.io](http://kompose.io).

-{{% /capture %}}


-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

-{{% /capture %}}

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

 ## Install Kompose

@@ -200,9 +201,9 @@ you need is an existing `docker-compose.yml` file.
      $ curl http://192.0.2.89
      ```

-{{% /capture %}}

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

 ## User Guide

@@ -606,4 +607,4 @@ Kompose supports Docker Compose versions: 1, 2 and 3. We have limited support on

 A full list on compatibility between all three versions is listed in our [conversion document](https://github.com/kubernetes/kompose/blob/master/docs/conversion.md) including a list of all incompatible Docker Compose keys.

-{{% /capture %}}
+
@@ -3,11 +3,11 @@ reviewers:
 - soltysh
 - sttts
 - ericchiang
-content_template: templates/concept
+content_type: concept
 title: Auditing
 ---

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

 Kubernetes auditing provides a security-relevant chronological set of records documenting
 the sequence of activities that have affected system by individual users, administrators
@@ -22,10 +22,10 @@ answer the following questions:
 - from where was it initiated?
 - to where was it going?

-{{% /capture %}}


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

 [Kube-apiserver][kube-apiserver] performs auditing. Each request on each stage
 of its execution generates an event, which is then pre-processed according to
@@ -503,12 +503,13 @@ plugin which supports full-text search and analytics.
 [logstash_install_doc]: https://www.elastic.co/guide/en/logstash/current/installing-logstash.html
 [kube-aggregator]: /docs/concepts/api-extension/apiserver-aggregation

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Visit [Auditing with Falco](/docs/tasks/debug-application-cluster/falco).

 Learn about [Mutating webhook auditing annotations](/docs/reference/access-authn-authz/extensible-admission-controllers/#mutating-webhook-auditing-annotations).

-{{% /capture %}}
+
@@ -4,11 +4,11 @@ reviewers:
 - feiskyer
 - mrunalp
 title: Debugging Kubernetes nodes with crictl
-content_template: templates/task
+content_type: task
 ---


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

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

@@ -17,15 +17,16 @@ You can use it to inspect and debug container runtimes and applications on a
 Kubernetes node. `crictl` and its source are hosted in the
 [cri-tools](https://github.com/kubernetes-incubator/cri-tools) repository.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 `crictl` requires a Linux operating system with a CRI runtime.

-{{% /capture %}}

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

 ## Installing crictl

@@ -347,12 +348,12 @@ CONTAINER ID        IMAGE               CREATED              STATE
 3e025dd50a72d       busybox             About a minute ago   Running             busybox             0
 ```

-{{% /capture %}}


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

 See [kubernetes-incubator/cri-tools](https://github.com/kubernetes-incubator/cri-tools)
 for more information.

-{{% /capture %}}
+
@@ -2,20 +2,20 @@
 reviewers:
 - janetkuo
 - thockin
-content_template: templates/concept
+content_type: concept
 title: Application Introspection and Debugging
 ---

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

 Once your application is running, you'll inevitably need to debug problems with it.
 Earlier we described how you can use `kubectl get pods` to retrieve simple status information about
 your pods. But there are a number of ways to get even more information about your application.

-{{% /capture %}}


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

 ## Using `kubectl describe pod` to fetch details about pods

@@ -387,9 +387,10 @@ status:
    systemUUID: ABE5F6B4-D44B-108B-C46A-24CCE16C8B6E
 ```

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Learn about additional debugging tools, including:

@@ -400,4 +401,4 @@ Learn about additional debugging tools, including:
 * [Connecting to containers via port forwarding](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/)
 * [Inspect Kubernetes node with crictl](/docs/tasks/debug-application-cluster/crictl/)

-{{% /capture %}}
+
@@ -3,19 +3,19 @@ reviewers:
 - mikedanese
 - thockin
 title: Troubleshoot Applications
-content_template: templates/concept
+content_type: concept
 ---

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

 This guide is to help users debug applications that are deployed into Kubernetes and not behaving correctly.
 This is *not* a guide for people who want to debug their cluster.  For that you should check out
 [this guide](/docs/admin/cluster-troubleshooting).

-{{% /capture %}}


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

 ## Diagnosing the problem

@@ -161,12 +161,13 @@ check:
   * Can you connect to your pods directly?  Get the IP address for the Pod, and try to connect directly to that IP.
   * Is your application serving on the port that you configured?  Kubernetes doesn't do port remapping, so if your application serves on 8080, the `containerPort` field needs to be 8080.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 If none of the above solves your problem, follow the instructions in [Debugging Service document](/docs/user-guide/debugging-services) to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are actually serving; you have DNS working, iptables rules installed, and kube-proxy does not seem to be misbehaving.

 You may also visit [troubleshooting document](/docs/troubleshooting/) for more information.

-{{% /capture %}}
+
@@ -2,20 +2,20 @@
 reviewers:
 - davidopp
 title: Troubleshoot Clusters
-content_template: templates/concept
+content_type: concept
 ---

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

 This doc is about cluster troubleshooting; we assume you have already ruled out your application as the root cause of the
 problem you are experiencing. See
 the [application troubleshooting guide](/docs/tasks/debug-application-cluster/debug-application) for tips on application debugging.
 You may also visit [troubleshooting document](/docs/troubleshooting/) for more information.

-{{% /capture %}}


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

 ## Listing your cluster

@@ -124,4 +124,4 @@ This is an incomplete list of things that could go wrong, and how to adjust your
  - Mitigates: Node shutdown
  - Mitigates: Kubelet software fault

-{{% /capture %}}
+
@@ -8,19 +8,20 @@ reviewers:
 - kow3ns
 - smarterclayton
 title: Debug Init Containers
-content_template: templates/task
+content_type: task
 ---

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

 This page shows how to investigate problems related to the execution of
 Init Containers. The example command lines below refer to the Pod as
  `<pod-name>` and the Init Containers as `<init-container-1>` and
  `<init-container-2>`.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

@@ -28,9 +29,9 @@ Init Containers. The example command lines below refer to the Pod as
  [Init Containers](/docs/concepts/abstractions/init-containers/).
 * You should have [Configured an Init Container](/docs/tasks/configure-pod-container/configure-pod-initialization/#creating-a-pod-that-has-an-init-container/).

-{{% /capture %}}

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

 ## Checking the status of Init Containers

@@ -113,9 +114,9 @@ Init Containers that run a shell script print
 commands as they're executed. For example, you can do this in Bash by running
 `set -x` at the beginning of the script.

-{{% /capture %}}

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

 ## Understanding Pod status

@@ -131,7 +132,7 @@ Status | Meaning
 `Pending` | The Pod has not yet begun executing Init Containers.
 `PodInitializing` or `Running` | The Pod has already finished executing Init Containers.

-{{% /capture %}}
+



@@ -2,25 +2,26 @@
 reviewers:
 - bprashanth
 title: Debug Pods and ReplicationControllers
-content_template: templates/task
+content_type: task
 ---

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

 This page shows how to debug Pods and ReplicationControllers.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

 * You should be familiar with the basics of
  [Pods](/docs/concepts/workloads/pods/pod/) and [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/).

-{{% /capture %}}

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

 ## Debugging Pods

@@ -106,4 +107,4 @@ or they can't. If they can't create pods, then please refer to the
 You can also use `kubectl describe rc ${CONTROLLER_NAME}` to inspect events
 related to the replication controller.

-{{% /capture %}}
+
@@ -3,16 +3,17 @@ reviewers:
 - verb
 - soltysh
 title: Debug Running Pods
-content_template: templates/task
+content_type: task
 ---

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

 This page explains how to debug Pods running (or crashing) on a Node.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * Your {{< glossary_tooltip text="Pod" term_id="pod" >}} should already be
  scheduled and running. If your Pod is not yet running, start with [Troubleshoot
@@ -21,9 +22,9 @@ This page explains how to debug Pods running (or crashing) on a Node.
  Pod is running and have shell access to run commands on that Node. You don't
  need that access to run the standard debug steps that use `kubectl`.

-{{% /capture %}}

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

 ## Examining pod logs {#examine-pod-logs}

@@ -187,4 +188,4 @@ given tools in the Kubernetes API. Therefore, if you find yourself needing to
 ssh into a machine, please file a feature request on GitHub describing your use
 case and why these tools are insufficient.

-{{% /capture %}}
+
@@ -2,21 +2,21 @@
 reviewers:
 - thockin
 - bowei
-content_template: templates/concept
+content_type: concept
 title: Debug Services
 ---

-{{% capture overview %}}
+<!-- overview -->
 An issue that comes up rather frequently for new installations of Kubernetes is
 that a Service is not working properly.  You've run your Pods through a
 Deployment (or other workload controller) and created a Service, but you
 get no response when you try to access it.  This document will hopefully help
 you to figure out what's going wrong.

-{{% /capture %}}


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

 ## Running commands in a Pod

@@ -728,10 +728,11 @@ Contact us on
 [Forum](https://discuss.kubernetes.io) or
 [GitHub](https://github.com/kubernetes/kubernetes).

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Visit [troubleshooting document](/docs/troubleshooting/) for more information.

-{{% /capture %}}
+
@@ -8,23 +8,24 @@ reviewers:
 - kow3ns
 - smarterclayton
 title: Debug a StatefulSet
-content_template: templates/task
+content_type: task
 ---

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

 This task shows you how to debug a StatefulSet.

-{{% /capture %}}

-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+

 * You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.
 * You should have a StatefulSet running that you want to investigate.

-{{% /capture %}}

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

 ## Debugging a StatefulSet

@@ -41,12 +42,13 @@ instructions on how to deal with them.
 You can debug individual Pods in a StatefulSet using the
 [Debugging Pods](/docs/tasks/debug-application-cluster/debug-pod-replication-controller/) guide.

-{{% /capture %}}

-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+

 Learn more about [debugging an init-container](/docs/tasks/debug-application-cluster/debug-init-containers/).

-{{% /capture %}}
+


--- a/Show More
+++ b/Show More