add en pages

content/en/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md

@@ -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 %}}
+