Reduce heading levels by 1.

2017-01-18 10:18:37 -08:00
parent 0f6b992771
commit 02d17ade5f
40 changed files with 178 additions and 187 deletions
@@ -15,7 +15,7 @@ Kubernetes cluster.

 {% capture steps %}

-### Adding a label to a node
+## Adding a label to a node

 1. List the nodes in your cluster:

@@ -49,7 +49,7 @@ Kubernetes cluster.
    In the preceding output, you can see that the `worker0` node has a
    `disktype=ssd` label.

-### Creating a pod that gets scheduled to your chosen node
+## Creating a pod that gets scheduled to your chosen node

 This pod configuration file describes a pod that has a node selector,
 `disktype: ssd`. This means that the pod will get scheduled on a node that has
@@ -15,7 +15,7 @@ PersistentVolume.

 {% capture steps %}

-### Why change reclaim policy of a PersistentVolume
+## Why change reclaim policy of a PersistentVolume

 `PersistentVolumes` can have various reclaim policies, including "Retain",
 "Recycle", and "Delete". For dynamically provisioned `PersistentVolumes`, 
@@ -27,7 +27,7 @@ policy. With the "Retain" policy, if a user deletes a `PeristentVolumeClaim`,
 the corresponding `PersistentVolume` is not be deleted. Instead, it is moved to the
 `Released` phase, where all of its data can be manually recovered.

-### Changing the reclaim policy of a PersistentVolume
+## Changing the reclaim policy of a PersistentVolume

 1. List the PersistentVolumes in your cluster:

@@ -70,7 +70,7 @@ the corresponding `PersistentVolume` is not be deleted. Instead, it is moved to
 * Learn more about [PersistentVolumes](/docs/user-guide/persistent-volumes/).
 * Learn more about [PersistentVolumeClaims](/docs/user-guide/persistent-volumes/#persistentvolumeclaims).

-#### Reference
+### Reference

 * [PersistentVolume](/docs/api-reference/v1/definitions/#_v1_persistentvolume)
 * [PersistentVolumeClaim](/docs/api-reference/v1/definitions/#_v1_persistentvolumeclaim)
@@ -19,7 +19,7 @@ Kubernetes cluster.

 {% capture steps %}

-### Determining whether DNS horizontal autoscaling is already enabled
+## Determining whether DNS horizontal autoscaling is already enabled

 List the Deployments in your cluster in the kube-system namespace:

@@ -36,7 +36,7 @@ If you see "kube-dns-autoscaler" in the output, DNS horizontal autoscaling is
 already enabled, and you can skip to
 [Tuning autoscaling parameters](#tuning-autoscaling-parameters).

-### Getting the name of your DNS Deployment or ReplicationController
+## Getting the name of your DNS Deployment or ReplicationController

 List the Deployments in your cluster in the kube-system namespace:

@@ -63,7 +63,7 @@ The output is similar to this:
    kube-dns-v20    1         1         1         ...
    ...

-### Determining your scale target
+## Determining your scale target

 If you have a DNS Deployment, your scale target is:

@@ -80,7 +80,7 @@ where <your-rc-name> is the name of your DNS ReplicationController. For example,
 if your DNS ReplicationController name is kube-dns-v20, your scale target is
 ReplicationController/kube-dns-v20.

-### Enabling DNS horizontal autoscaling
+## Enabling DNS horizontal autoscaling

 In this section, you create a Deployment. The Pods in the Deployment run a
 container based on the `cluster-proportional-autoscaler-amd64` image.
@@ -102,7 +102,7 @@ The output of a successful command is:

 DNS horizontal autoscaling is now enabled.

-### Tuning autoscaling parameters
+## Tuning autoscaling parameters

 Verify that the kube-dns-autoscaler ConfigMap exists:

@@ -139,12 +139,12 @@ cores, `nodesPerReplica` dominates.
 There are other supported scaling patterns. For details, see
 [cluster-proportional-autoscaler](https://github.com/kubernetes-incubator/cluster-proportional-autoscaler).

-### Disable DNS horizontal autoscaling
+## Disable DNS horizontal autoscaling

 There are a few options for turning DNS horizontal autoscaling. Which option to
 use depends on different conditions.

-#### Option 1: Scale down the kube-dns-autoscaler deployment to 0 replicas
+### Option 1: Scale down the kube-dns-autoscaler deployment to 0 replicas

 This option works for all situations. Enter this command:

@@ -165,7 +165,7 @@ The output displays 0 in the DESIRED and CURRENT columns:
    kube-dns-autoscaler   0         0         0            0           ...
    ...

-#### Option 2: Delete the kube-dns-autoscaler deployment
+### Option 2: Delete the kube-dns-autoscaler deployment

 This option works if kube-dns-autoscaler is under your own control, which means
 no one will re-create it:
@@ -176,7 +176,7 @@ The output is:

    deployment "kube-dns-autoscaler" deleted

-#### Option 3: Delete the kube-dns-autoscaler manifest file from the master node
+### Option 3: Delete the kube-dns-autoscaler manifest file from the master node

 This option works if kube-dns-autoscaler is under control of the
 [Addon Manager](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/README.md)'s
@@ -194,7 +194,7 @@ kube-dns-autoscaler Deployment.

 {% capture discussion %}

-### Understanding how DNS horizontal autoscaling works
+## Understanding how DNS horizontal autoscaling works

 * The cluster-proportional-autoscaler application is deployed separately from
 the DNS service.
@@ -215,7 +215,7 @@ the autoscaler Pod.
 * The autoscaler provides a controller interface to support two control
 patterns: *linear* and *ladder*.

-### Future enhancements
+## Future enhancements

 Control patterns, in addition to linear and ladder, that consider custom metrics
 are under consideration as a future development.
@@ -21,7 +21,7 @@ application-level disruption SLOs you want the system to enforce.

 {% capture steps %}

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

 You can use `kubectl drain` to safely evict all of your pods from a
 node before you perform maintenance on the node (e.g. kernel upgrade,
@@ -64,7 +64,7 @@ kubectl uncordon <node name>
 ```
 afterwards to tell Kubernetes that it can resume scheduling new pods onto the node.

-### Draining multiple nodes in parallel
+## Draining multiple nodes in parallel

 The `kubectl drain` command should only be issued to a single node at a
 time. However, you can run multiple `kubectl drain` commands for