From 199101048df6f84a80349464f3fb77a17fd799eb Mon Sep 17 00:00:00 2001 From: Devin Donnelly Date: Wed, 2 Nov 2016 16:27:27 -0700 Subject: [PATCH 01/44] Adds Concepts root page and starts to fill out the underlying section. --- docs/concepts/abstractions/pod.md | 3 ++ docs/concepts/index.md | 46 ++++++++++++++++++++++++++++++- 2 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 docs/concepts/abstractions/pod.md diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md new file mode 100644 index 0000000000..ec380ec43f --- /dev/null +++ b/docs/concepts/abstractions/pod.md @@ -0,0 +1,3 @@ +--- +--- + diff --git a/docs/concepts/index.md b/docs/concepts/index.md index db56a3d05b..3511f2354d 100644 --- a/docs/concepts/index.md +++ b/docs/concepts/index.md @@ -1,7 +1,51 @@ --- --- -The Concepts section of the Kubernetes documentation is a work in progress. +The Concepts section helps you learn about the parts of the Kubernetes system and the abstractions Kubernetes uses to represent your cluster, and helps you obtain a deeper understanding of how Kubernetes works. + +## Overview + +To work with Kubernetes, you use the **Kubernetes API abstractions** to describe your cluster's **desired state**: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. + +Once you've set your desired state, the **Kubernetes Control Plane** works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of processes running on your cluster: the Kubernetes Master, and kubelet and kube-proxy processes running on your cluster's individual nodes. + +## Kubernetes Abstractions + +Kubernetes contains a number of abstractions that represent your deployed containerized applications and workloads, along with their associated network and disk resources. These abstractions are made manifest as objects in the Kubernetes API. The basic Kubernetes abstractions include: + +* Pod +* Service +* Volume +* Namespace + +In addition, Kubernetes contains a number of higher-level abstractions that build upon the basic abstractions, and provide additional functionality and convenience features. They include: + +* ReplicaSet +* Deployment +* StatefulSet +* DaemonSet +* Job + +## Kubernetes Control Plane + +The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. When you use the Kubernetes API to create deployments, for example, the Kubernetes Control Plane carries out your instructions. + +### Kubernetes Master + +The Kubernetes master is responsible for maintaining the desired state for your cluster. The Kubernetes master(s) runs the following processes: + +* API Server +* Scheduler +* Etcd +* Controller Manager + +### Kubernetes Nodes + +The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. These nodes are controlled by the Kubernetes master. The following processes run on each node in a Kubernetes cluster: + +* Kubelet +* Docker-daemon +* kube-proxy #### Object Metadata From 6eea38eddb71bbab2dc9ffc121f0cd5e25575fc5 Mon Sep 17 00:00:00 2001 From: Devin Donnelly Date: Thu, 17 Nov 2016 16:10:17 -0800 Subject: [PATCH 02/44] First draft of Concepts landing page. Adds Kubernetes Objects overview. Adds first draft of Pod. --- docs/concepts/abstractions/overview.md | 58 +++++++++++++++++++++ docs/concepts/abstractions/pod.md | 71 ++++++++++++++++++++++++++ docs/concepts/index.md | 16 +++--- 3 files changed, 138 insertions(+), 7 deletions(-) create mode 100644 docs/concepts/abstractions/overview.md diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md new file mode 100644 index 0000000000..9b561d1b3e --- /dev/null +++ b/docs/concepts/abstractions/overview.md @@ -0,0 +1,58 @@ +--- +--- + +{% capture overview %} +This page explains how Kubernetes objects are represented in the Kubernetes API, and how you can express them in `.yaml` format. +{% endcapture %} + +{% capture body %} +### Understanding Kubernetes Objects + +*Kubernetes Objects* are persistent entities in the Kubernetes system. Kubenetes uses these entities to represent the state of your cluster. Specifically, they can describe: + +* What containerized applications are running (and on which nodes) +* The resources available to those applications +* The policies around how those applications behave, such as restart policies, upgrades, and fault-tolerance + +When you create a Kubernetes object, you create a "record of intent"--once you create the object, the Kubernetes system will constantly work to ensure that the entity exists. By creating an object, you're effectively telling the Kubernetes system what you want your cluster to be doing; this is your cluster's **desired state**. + +To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. + +#### Object Spec and Status + +Every Kubernetes object has two major nested object fields: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied by the Kubernetes system. At any given time, the [Kubernetes Control Plane](/docs/concepts/control-plane/overview/) actively maintains an object's actual state to match the desired state you supplied. + +For more information on the object spec and status, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status). + +#### Describing a Kubernetes Object + +When you create an object in Kubernetes, you need to describe it. Your description must provide some basic information about the object along with the object spec that represents your desired state. The Kubernetes API communicates this information by passing JSON; when you make Kubernetes API calls or use the `kubectl` command-line interface, **you can express that JSON using a `.yaml` file.** + +Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes [Deployment](/docs/concepts/abstractions/deployment/): + +{% include code.html language="yaml" file="nginx-deployment.yaml" ghlink="/docs/user-guide/nginx-deployment.yaml" %} + +One way to create a Deployment using a `.yaml` file like the one above is to use the []`kubectl create`]() command in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example: + +```shell +$ kubectl create -f docs/user-guide/nginx-deployment.yaml --record +deployment "nginx-deployment" created +``` + +#### Required Fields + +In the `.yaml` file for the Kubernetes object you want to create, you'll need to set values for the following fields: + +* `apiVersion` - Which version of the Kubernetes API you're using to create this object +* `kind` - What kind of object you want to create +* `metadata` - Data that helps uniquely identify the object, including a `name` string, UID, and optional `namespace` + +You'll also need to provide the object `spec` field. The precise format of the object `spec` is different for every Kubernetes object, and contains nested fields specific to that object. The [Kubernetes API reference](/docs/api/) can help you find the spec format for all of the objects you can create using Kubernetes. + +{% endcapture %} + +{% capture whatsnext %} +* Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/abstractions/pod/). +{% endcapture %} + +{% include templates/concept.md %} \ No newline at end of file diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md index ec380ec43f..4fd21471e9 100644 --- a/docs/concepts/abstractions/pod.md +++ b/docs/concepts/abstractions/pod.md @@ -1,3 +1,74 @@ --- --- +{% capture overview %} +This page provides an overview of `Pod`, the smallest deployable object in the Kubernetes object model. +{% endcapture %} + +* TOC +{:toc} + +{% capture body %} +### Understanding Pods + +A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster. + +A Pod encapsulates an application container (or, in some cases, multiple containers), storage resources, and options that govern how the container(s) should run. A Pod represents a unit of deployment: *a single workload in Kubernetes*, which might consist of either a single application or a small number of applications that are tightly coupled and that share resources. + +> [Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other container runtimes as well. + +Pods are employed a number of ways in a Kubernetes cluster, including: + +* **Pods that run a single application container**. The "one-application per Pod" model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single application, and Kubernetes manages the Pods rather than the containers directly. +* **Pods that run multiple application containers that need to work together**. Pods can support multiple application containers that are tightly coupled and need to share resources. You can think of these applications as forming a *single cohesive unit of service*. The Pod wraps them together with shared resources as a single managable entity. + +Pods typically *do not* model multiple instances of the same application container. Instead, you can have Kubernetes maintain separate Pods for each instance you want to run, usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information. + +#### How Pods Manage Containers + +Pods are designed to support multiple cooperating processes (as application containers) that form a cohesive unit of service. The containers in a Pod are automatically co-located and co-scheduled on the same phyiscal or virtual machine in the cluster. The containers can share resources and dependencies, communicate with one another, and coordinate when and how they are terminated. + +Pods provide two kinds of shared resources for their constituent containers: *networking* and *storage*. + +##### Networking + +Each Pod is assigned a unique IP address. Every the container in a pod shares the network namespace, including the IP address and network ports. Containers *inside a Pod* can communicate with one another using `localhost`. When containers in a Pod communicate with entities *outside the Pod*, they must coordinate how they use the shared network resources (such as ports). + +##### Storage + +A Pod can specify a set of shared storage *volumes*. All containers in the pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a pod to survive in case one of the containers within needs to be restarted. See [Volumes]() for more information on how Kubernetes implements shared storage in a Pod. + +### Working with Pods + +When a Pod gets created (directly or indirectly), it is scheduled to run on a [node]() in your cluster, and remains on that node until terminated or deleted. Should a node in the cluster fail, the Pods scheduled on that node are deleted after a timeout period. See [Termination](#pod-termination) for more details on how Pods terminate in Kubernetes. + +You'll rarely create or interact directly with individual Pods in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral entities (as opposed to a durable one). A Pod won't survive a scheduling failure, a node failure, or an eviction due to a lack of resources or node maintenance. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a higher-level abstraction called a *Controller*. + +#### Pods and Controllers + +A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope (for example, if a node fails, a Controller might schedule an identical replacement Pod on a different node). + +Some examples of Controllers that contain one or more pods include: + +* [Deployment]() +* [StatefulSet]() +* [DaemonSet]() + +In general, Controllers use a [Pod Template]() that you provide to create the Pods for which it is responsible. + +#### Pod Termination + +Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. After the grace period expires, Kubernetes issues a `KILL` signal to the relevant processes and the Pod is deleted from the Kubernetes Master. + +> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information. + +{% endcapture %} + + +{% if whatsnext %} + +### What's next + +{{ whatsnext }} + +{% endif %} \ No newline at end of file diff --git a/docs/concepts/index.md b/docs/concepts/index.md index 3511f2354d..a6b35bdfde 100644 --- a/docs/concepts/index.md +++ b/docs/concepts/index.md @@ -5,20 +5,22 @@ The Concepts section helps you learn about the parts of the Kubernetes system an ## Overview -To work with Kubernetes, you use the **Kubernetes API abstractions** to describe your cluster's **desired state**: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. +To work with Kubernetes, you use *Kubernetes API objects* to describe your cluster's *desired state*: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by creating objects using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. -Once you've set your desired state, the **Kubernetes Control Plane** works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of processes running on your cluster: the Kubernetes Master, and kubelet and kube-proxy processes running on your cluster's individual nodes. +Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of processes running on your cluster: the Kubernetes Master, and kubelet and kube-proxy processes running on your cluster's individual nodes. -## Kubernetes Abstractions +## Kubernetes Objects -Kubernetes contains a number of abstractions that represent your deployed containerized applications and workloads, along with their associated network and disk resources. These abstractions are made manifest as objects in the Kubernetes API. The basic Kubernetes abstractions include: +Kubernetes contains a number of abstractions that represent your the state of your system: deployed containerized applications and workloads, their associated network and disk resources, and other information about what your cluster is doing. These abstractions are represented by objects in the Kubernetes API; see the [Kubernetes Objects overview](/docs/concepts/abstractions/overview/) for more details. -* Pod +The basic Kubernetes objects include: + +* [Pod](/docs/concepts/abstractions/pod/) * Service * Volume * Namespace -In addition, Kubernetes contains a number of higher-level abstractions that build upon the basic abstractions, and provide additional functionality and convenience features. They include: +In addition, Kubernetes contains a number of higher-level abstractions that build upon the basic objects, and provide additional functionality and convenience features. They include: * ReplicaSet * Deployment @@ -28,7 +30,7 @@ In addition, Kubernetes contains a number of higher-level abstractions that buil ## Kubernetes Control Plane -The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. When you use the Kubernetes API to create deployments, for example, the Kubernetes Control Plane carries out your instructions. +The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. When you use the Kubernetes API to create a Deployment object, for example, the Kubernetes Control Plane carries out your instructions. ### Kubernetes Master From a21c80911e6a50e33f1add5fc1b7c832d4cb1ee5 Mon Sep 17 00:00:00 2001 From: Devin Donnelly Date: Thu, 17 Nov 2016 16:22:46 -0800 Subject: [PATCH 03/44] Attempted include file fix for sample Deployment .yaml file. --- docs/concepts/abstractions/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md index 9b561d1b3e..c4899afa44 100644 --- a/docs/concepts/abstractions/overview.md +++ b/docs/concepts/abstractions/overview.md @@ -30,7 +30,7 @@ When you create an object in Kubernetes, you need to describe it. Your descripti Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes [Deployment](/docs/concepts/abstractions/deployment/): -{% include code.html language="yaml" file="nginx-deployment.yaml" ghlink="/docs/user-guide/nginx-deployment.yaml" %} +{% include code.html language="yaml" file="/docs/user-guide/nginx-deployment.yaml" ghlink="/docs/user-guide/nginx-deployment.yaml" %} One way to create a Deployment using a `.yaml` file like the one above is to use the []`kubectl create`]() command in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example: From 30be38b63f5a249d654e8b132c8987bd4f4c6021 Mon Sep 17 00:00:00 2001 From: Devin Donnelly Date: Fri, 18 Nov 2016 16:37:23 -0800 Subject: [PATCH 04/44] Edited Concepts landing page, Objects overview, and Pod concept documentation to address feedback from pwittroc. --- docs/concepts/abstractions/overview.md | 17 ++++++++---- docs/concepts/abstractions/pod.md | 38 +++++++++++++++++++------- docs/concepts/index.md | 11 ++++++-- 3 files changed, 49 insertions(+), 17 deletions(-) diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md index c4899afa44..8407eecf43 100644 --- a/docs/concepts/abstractions/overview.md +++ b/docs/concepts/abstractions/overview.md @@ -14,19 +14,21 @@ This page explains how Kubernetes objects are represented in the Kubernetes API, * The resources available to those applications * The policies around how those applications behave, such as restart policies, upgrades, and fault-tolerance -When you create a Kubernetes object, you create a "record of intent"--once you create the object, the Kubernetes system will constantly work to ensure that the entity exists. By creating an object, you're effectively telling the Kubernetes system what you want your cluster to be doing; this is your cluster's **desired state**. +When you create a Kubernetes object, you create a "record of intent"--once you create the object, the Kubernetes system will constantly work to ensure that that object exists. By creating an object, you're effectively telling the Kubernetes system what you want your cluster's workload to look like; this is your cluster's **desired state**. -To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. +To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. Kubernetes currently provides a `golang` client library for this purpose, and other language libraries are being developed. #### Object Spec and Status -Every Kubernetes object has two major nested object fields: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied by the Kubernetes system. At any given time, the [Kubernetes Control Plane](/docs/concepts/control-plane/overview/) actively maintains an object's actual state to match the desired state you supplied. +Every Kubernetes object includes two nested object fields that govern the object's configuration: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied and updated by the Kubernetes system. At any given time, the [Kubernetes Control Plane](/docs/concepts/control-plane/overview/) actively manages an object's actual state to match the desired state you supplied. -For more information on the object spec and status, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status). +For example, a Kubernetes [Deployment]() is an object that can represent an application running on your cluster. When you create the Deployment, you might set the Deployment spec to specify that you want three replicas of the application to be running. The Kubernetes system reads the Deployment spec and starts three instances of your desired application--updating the status to match your spec. If any of those instances should fail (a status change), the Kubernetes system reacts to the difference between spec and status by making a correction--in this case, starting a replacement instance. + +For more information on the object spec, status, and metadata, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status). #### Describing a Kubernetes Object -When you create an object in Kubernetes, you need to describe it. Your description must provide some basic information about the object along with the object spec that represents your desired state. The Kubernetes API communicates this information by passing JSON; when you make Kubernetes API calls or use the `kubectl` command-line interface, **you can express that JSON using a `.yaml` file.** +When you create an object in Kubernetes, you must provide the object spec that describes your desired state for it, as well as some basic information about the object (such as a name). When you use the Kubernetes API to create the object (either directly or via `kubectl`), that API call sends the information to the Kubernetes Master as JSON. **You can express that JSON using a `.yaml` file.** Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes [Deployment](/docs/concepts/abstractions/deployment/): @@ -36,6 +38,11 @@ One way to create a Deployment using a `.yaml` file like the one above is to use ```shell $ kubectl create -f docs/user-guide/nginx-deployment.yaml --record +``` + +The output is similar to this: + +```shell deployment "nginx-deployment" created ``` diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md index 4fd21471e9..fb65c8b33c 100644 --- a/docs/concepts/abstractions/pod.md +++ b/docs/concepts/abstractions/pod.md @@ -13,20 +13,29 @@ This page provides an overview of `Pod`, the smallest deployable object in the K A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster. -A Pod encapsulates an application container (or, in some cases, multiple containers), storage resources, and options that govern how the container(s) should run. A Pod represents a unit of deployment: *a single workload in Kubernetes*, which might consist of either a single application or a small number of applications that are tightly coupled and that share resources. +A Pod encapsulates an application container (or, in some cases, multiple containers), storage resources, a unique network IP, and options that govern how the container(s) should run. A Pod represents a unit of deployment: *a single instance of an application in Kubernetes*, which might consist of either a single container or a small number of containers that are tightly coupled and that share resources. > [Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other container runtimes as well. Pods are employed a number of ways in a Kubernetes cluster, including: -* **Pods that run a single application container**. The "one-application per Pod" model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single application, and Kubernetes manages the Pods rather than the containers directly. -* **Pods that run multiple application containers that need to work together**. Pods can support multiple application containers that are tightly coupled and need to share resources. You can think of these applications as forming a *single cohesive unit of service*. The Pod wraps them together with shared resources as a single managable entity. +* **Pods that run a single container**. The "one-container-per-Pod" model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single container, and Kubernetes manages the Pods rather than the containers directly. +* **Pods that run multiple containers that need to work together**. A Pod might encapsulate an application that relies on multiple co-located containers that are tightly coupled and need to share resources. These co-located containers might form a single cohesive unit of service--one container serving files from a shared volume to the public, while a separate "sidecar" container refreshes or updates those files. The Pod wraps these containers and storage resources together as a single managable entity. -Pods typically *do not* model multiple instances of the same application container. Instead, you can have Kubernetes maintain separate Pods for each instance you want to run, usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information. +The [Kubernetes Blog](http://blog.kubernetes.io) has some additional information on Pod use cases. For more information, see: -#### How Pods Manage Containers +* [The Distributed System Toolkit: Patterns for Composite Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html) +* [Container Design Patterns](http://blog.kubernetes.io/2016/06/container-design-patterns.html) -Pods are designed to support multiple cooperating processes (as application containers) that form a cohesive unit of service. The containers in a Pod are automatically co-located and co-scheduled on the same phyiscal or virtual machine in the cluster. The containers can share resources and dependencies, communicate with one another, and coordinate when and how they are terminated. +Note that each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, such Pods are usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information. + +#### How Pods Manage Multiple Containers + +Pods are designed to support multiple cooperating processes (as containers) that form a cohesive unit of service. The containers in a Pod are automatically co-located and co-scheduled on the same phyiscal or virtual machine in the cluster. The containers can share resources and dependencies, communicate with one another, and coordinate when and how they are terminated. + +Note that grouping multiple co-located and co-managed containers in a single Pod is a relatively advanced use case. You should use this pattern only in specific instances in which your containers are tightly coupled. For example, you might have a container that acts as a web server for files in a shared volume, and a separate "sidecar" container that updates those files from a remote source, as in the following diagram: + +![pod diagram](/images/docs/pod.svg){: style="max-width: 50%" } Pods provide two kinds of shared resources for their constituent containers: *networking* and *storage*. @@ -40,13 +49,15 @@ A Pod can specify a set of shared storage *volumes*. All containers in the pod c ### Working with Pods -When a Pod gets created (directly or indirectly), it is scheduled to run on a [node]() in your cluster, and remains on that node until terminated or deleted. Should a node in the cluster fail, the Pods scheduled on that node are deleted after a timeout period. See [Termination](#pod-termination) for more details on how Pods terminate in Kubernetes. +You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a [node]() in your cluster. The Pod remains on that node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources. -You'll rarely create or interact directly with individual Pods in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral entities (as opposed to a durable one). A Pod won't survive a scheduling failure, a node failure, or an eviction due to a lack of resources or node maintenance. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a higher-level abstraction called a *Controller*. +> Note: Restarting a container in a Pod should not be confused with restarting the Pod. The Pod itself does not run, but is an environment the containers run in and persists until it is deleted. + +Pods do not, by themselves, self-heal. If a Pod is scheduled to a node that fails, or if the scheduling operation itself fails, the Pod is deleted; likewise, a Pod won't survive an eviction due to a lack of resources or node maintenance. Kubernetes uses a higher-level abstraction, called a *Controller*, that handles the work of managing the relatively disposable Pod instances. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a Controller. See [Pods and Controllers](#pods-and-controllers) for more information on how Kubernetes uses Controllers to implement Pod scaling and healing. #### Pods and Controllers -A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope (for example, if a node fails, a Controller might schedule an identical replacement Pod on a different node). +A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope. For example, if a node fails, the Controller might automatically replace the Pod by scheduling an identical replacement on a different node). Some examples of Controllers that contain one or more pods include: @@ -58,7 +69,14 @@ In general, Controllers use a [Pod Template]() that you provide to create the Po #### Pod Termination -Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. After the grace period expires, Kubernetes issues a `KILL` signal to the relevant processes and the Pod is deleted from the Kubernetes Master. +Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps: + +1. You send a command or API call to terminate the Pod. +1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period). +1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod. +1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down. +1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod. +1. Kubernetes removes the Pod from the API server on the Kubernetes Master. > **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information. diff --git a/docs/concepts/index.md b/docs/concepts/index.md index a6b35bdfde..ab5bd548a5 100644 --- a/docs/concepts/index.md +++ b/docs/concepts/index.md @@ -7,7 +7,12 @@ The Concepts section helps you learn about the parts of the Kubernetes system an To work with Kubernetes, you use *Kubernetes API objects* to describe your cluster's *desired state*: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by creating objects using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. -Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of processes running on your cluster: the Kubernetes Master, and kubelet and kube-proxy processes running on your cluster's individual nodes. +Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of a collection processes running on your cluster: + +* The **Kubernetes Master** is a collection of four processes that run on a single node in your cluster, which is designated as the master node. +* Each individual non-master node in your cluster runs two processes: + * **kubelet**, which communicates with the Kubernetes Master. + * **kube-proxy**, a network proxy which reflects Kubernetes networking services on each node. ## Kubernetes Objects @@ -30,7 +35,9 @@ In addition, Kubernetes contains a number of higher-level abstractions that buil ## Kubernetes Control Plane -The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. When you use the Kubernetes API to create a Deployment object, for example, the Kubernetes Control Plane carries out your instructions. +The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. The Control Plane maintains a record of all of the Kubernetes Objects in the system, and runs continuous control loops to manage those objects' state. At any given time, the Control Plane's control loops will attempt to match the actual state of all the objects in the system to the desired state that you provided when you created those objects. + +For example, When you use the Kubernetes API to create a Deployment object, for example, you provide a new desired state for the system. The Kubernetes Control Plane records that object creation, and carries out your instructions by starting the required applications and scheduling them to cluster nodes--thus making the cluster's actual state match the desired state. ### Kubernetes Master From a95cfcddf2c0217b9e8bc90737cca79263f2f371 Mon Sep 17 00:00:00 2001 From: tanshanshan Date: Tue, 3 Jan 2017 16:46:57 +0800 Subject: [PATCH 05/44] replace hack/build-go.sh with make --- docs/admin/multiple-schedulers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/multiple-schedulers.md b/docs/admin/multiple-schedulers.md index eb1c4c44f9..5548f32904 100644 --- a/docs/admin/multiple-schedulers.md +++ b/docs/admin/multiple-schedulers.md @@ -26,7 +26,7 @@ and build the source. ```shell git clone https://github.com/kubernetes/kubernetes.git cd kubernetes -hack/build-go.sh +make ``` Create a container image containing the kube-scheduler binary. Here is the `Dockerfile` From 9300e36e564c90f1110a321554251de4691f8f27 Mon Sep 17 00:00:00 2001 From: Aaron Signorelli Date: Wed, 4 Jan 2017 00:38:40 +0000 Subject: [PATCH 06/44] Fixing typo .PONY -> .PHONY --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 64ceef89a0..3657cb577a 100644 --- a/Makefile +++ b/Makefile @@ -1,4 +1,4 @@ -.PONY: all build build-preview help serve +.PHONY: all build build-preview help serve help: ## Show this help. @awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST) From b8b448fb63946bc8500cb5efa4250ad2a45cf3ef Mon Sep 17 00:00:00 2001 From: chentao1596 Date: Wed, 4 Jan 2017 09:16:51 +0800 Subject: [PATCH 07/44] change the flag which controlls the cbr0's create --- docs/admin/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/networking.md b/docs/admin/networking.md index e1de39fdbd..84e612bfdd 100644 --- a/docs/admin/networking.md +++ b/docs/admin/networking.md @@ -130,7 +130,7 @@ We start Docker with: DOCKER_OPTS="--bridge=cbr0 --iptables=false --ip-masq=false" ``` -This bridge is created by Kubelet (controlled by the `--configure-cbr0=true` +This bridge is created by Kubelet (controlled by the `--network-plugin=kubenet` flag) according to the `Node`'s `spec.podCIDR`. Docker will now allocate IPs from the `cbr-cidr` block. Containers can reach From 40c801bd111a5fe7bb0902881422b0c43cb7ec39 Mon Sep 17 00:00:00 2001 From: Minhan Xia Date: Wed, 4 Jan 2017 17:33:09 -0800 Subject: [PATCH 08/44] delete exec network plugin --- docs/admin/network-plugins.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index dd51a11b86..d5e05ac7b1 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -13,7 +13,6 @@ __Disclaimer__: Network plugins are in alpha. Its contents will change rapidly. Network plugins in Kubernetes come in a few flavors: -* Plain vanilla exec plugins - deprecated in favor of CNI plugins. * CNI plugins: adhere to the appc/CNI specification, designed for interoperability. * Kubenet plugin: implements basic `cbr0` using the `bridge` and `host-local` CNI plugins @@ -30,10 +29,6 @@ Besides providing the [`NetworkPlugin` interface](https://github.com/kubernetes/ By default if no kubelet network plugin is specified, the `noop` plugin is used, which sets `net/bridge/bridge-nf-call-iptables=1` to ensure simple configurations (like docker with a bridge) work correctly with the iptables proxy. -### Exec - -Place plugins in `network-plugin-dir/plugin-name/plugin-name`, i.e. if you have a bridge plugin and `network-plugin-dir` is `/usr/lib/kubernetes`, you'd place the bridge plugin executable at `/usr/lib/kubernetes/bridge/bridge`. See [this comment](https://github.com/kubernetes/kubernetes/tree/{{page.version}}/pkg/kubelet/network/exec/exec.go) for more details. - ### CNI The CNI plugin is selected by passing Kubelet the `--network-plugin=cni` command-line option. Kubelet reads a file from `--cni-conf-dir` (default `/etc/cni/net.d`) and uses the CNI configuration from that file to set up each pod's network. The CNI configuration file must match the [CNI specification](https://github.com/containernetworking/cni/blob/master/SPEC.md#network-configuration), and any required CNI plugins referenced by the configuration must be present in `--cni-bin-dir` (default `/opt/cni/bin`). @@ -73,7 +68,6 @@ This option is provided to the network-plugin; currently **only kubenet supports ## Usage Summary -* `--network-plugin=exec` specifies that we use the `exec` plugin, with executables located in `--network-plugin-dir`. * `--network-plugin=cni` specifies that we use the `cni` network plugin with actual CNI plugin binaries located in `--cni-bin-dir` (default `/opt/cni/bin`) and CNI plugin configuration located in `--cni-conf-dir` (default `/etc/cni/net.d`). * `--network-plugin=kubenet` specifies that we use the `kubenet` network plugin with CNI `bridge` and `host-local` plugins placed in `/opt/cni/bin` or `network-plugin-dir`. * `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin. From 068c797f47f346a578148964926bba32a884f4fa Mon Sep 17 00:00:00 2001 From: caiyixiang Date: Tue, 10 Jan 2017 09:20:38 +0800 Subject: [PATCH 09/44] Update ingress.md --- docs/user-guide/ingress.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index b9c371e2a1..788cabaa4b 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -69,7 +69,7 @@ spec: *POSTing this to the API server will have no effect if you have not configured an [Ingress controller](#ingress-controllers).* -__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields. For general information about working with config files, see [here](/docs/user-guide/simple-yaml), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources). +__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields. For general information about working with config files, see [here](docs/user-guide/deploying-applications), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources). __Lines 5-7__: Ingress [spec](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/api-conventions.md#spec-and-status) has all the information needed to configure a loadbalancer or proxy server. Most importantly, it contains a list of rules matched against all incoming requests. Currently the Ingress resource only supports http rules. @@ -107,7 +107,7 @@ Where `107.178.254.228` is the IP allocated by the Ingress controller to satisfy ### Simple fanout -As described previously, pods within kubernetes have IPs only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancer/s. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: +As described previously, pods within kubernetes have IPs only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancers. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: ```shell foo.bar.com -> 178.91.123.132 -> / foo s1:80 From 40356713c40a95c5abe728a83ecd794ae7bb0817 Mon Sep 17 00:00:00 2001 From: Patrick Clinger Date: Wed, 4 Jan 2017 14:56:49 -0800 Subject: [PATCH 10/44] Fix references to restartPolicy spec location This document currently indicates that restartPolicy is part of the v1.Container spec, however according to the definitions it is actually in the v1.PodSpec. References: http://kubernetes.io/docs/api-reference/v1/definitions/#_v1_pod http://kubernetes.io/docs/api-reference/v1/definitions/#_v1_container Changed references to be `.spec.template.spec.restartPolicy` --- docs/user-guide/jobs.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/user-guide/jobs.md b/docs/user-guide/jobs.md index d8476d73d5..cc2f9d38c3 100644 --- a/docs/user-guide/jobs.md +++ b/docs/user-guide/jobs.md @@ -172,20 +172,20 @@ parallelism, for a variety or reasons: A Container in a Pod may fail for a number of reasons, such as because the process in it exited with a non-zero exit code, or the Container was killed for exceeding a memory limit, etc. If this -happens, and the `.spec.template.containers[].restartPolicy = "OnFailure"`, then the Pod stays +happens, and the `.spec.template.spec.restartPolicy = "OnFailure"`, then the Pod stays on the node, but the Container is re-run. Therefore, your program needs to handle the case when it is -restarted locally, or else specify `.spec.template.containers[].restartPolicy = "Never"`. +restarted locally, or else specify `.spec.template.spec.restartPolicy = "Never"`. See [pods-states](/docs/user-guide/pod-states) for more information on `restartPolicy`. An entire Pod can also fail, for a number of reasons, such as when the pod is kicked off the node (node is upgraded, rebooted, deleted, etc.), or if a container of the Pod fails and the -`.spec.template.containers[].restartPolicy = "Never"`. When a Pod fails, then the Job controller +`.spec.template.spec.restartPolicy = "Never"`. When a Pod fails, then the Job controller starts a new Pod. Therefore, your program needs to handle the case when it is restarted in a new pod. In particular, it needs to handle temporary files, locks, incomplete output and the like caused by previous runs. Note that even if you specify `.spec.parallelism = 1` and `.spec.completions = 1` and -`.spec.template.containers[].restartPolicy = "Never"`, the same program may +`.spec.template.spec.restartPolicy = "Never"`, the same program may sometimes be started twice. If you do specify `.spec.parallelism` and `.spec.completions` both greater than 1, then there may be From 22fb75ff4d4a0f364cba7dd92a6c36f862e87e8f Mon Sep 17 00:00:00 2001 From: Ben Hall Date: Thu, 12 Jan 2017 09:04:54 +0000 Subject: [PATCH 11/44] Remove some padding around Katacoda to give it a little more space. --- .../kubernetes-basics/cluster-interactive.html | 2 +- .../kubernetes-basics/deploy-interactive.html | 2 +- .../kubernetes-basics/explore-interactive.html | 2 +- .../kubernetes-basics/expose-interactive.html | 2 +- .../tutorials/kubernetes-basics/public/css/styles.css | 11 ++++++++++- .../kubernetes-basics/scale-interactive.html | 2 +- .../kubernetes-basics/update-interactive.html | 2 +- 7 files changed, 16 insertions(+), 7 deletions(-) diff --git a/docs/tutorials/kubernetes-basics/cluster-interactive.html b/docs/tutorials/kubernetes-basics/cluster-interactive.html index da0df10297..c1125b90c0 100644 --- a/docs/tutorials/kubernetes-basics/cluster-interactive.html +++ b/docs/tutorials/kubernetes-basics/cluster-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Creating a Cluster
-
+
diff --git a/docs/tutorials/kubernetes-basics/deploy-interactive.html b/docs/tutorials/kubernetes-basics/deploy-interactive.html index 5fe4990723..42796283a0 100644 --- a/docs/tutorials/kubernetes-basics/deploy-interactive.html +++ b/docs/tutorials/kubernetes-basics/deploy-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Deploying an App
-
+

diff --git a/docs/tutorials/kubernetes-basics/explore-interactive.html b/docs/tutorials/kubernetes-basics/explore-interactive.html index ff007f80d1..6b284c3ad5 100644 --- a/docs/tutorials/kubernetes-basics/explore-interactive.html +++ b/docs/tutorials/kubernetes-basics/explore-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Exploring Your App
-
+

diff --git a/docs/tutorials/kubernetes-basics/expose-interactive.html b/docs/tutorials/kubernetes-basics/expose-interactive.html index 26b30492a6..00c7cb9e02 100644 --- a/docs/tutorials/kubernetes-basics/expose-interactive.html +++ b/docs/tutorials/kubernetes-basics/expose-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Exposing Your App
-
+
diff --git a/docs/tutorials/kubernetes-basics/public/css/styles.css b/docs/tutorials/kubernetes-basics/public/css/styles.css index 654544f1dd..33415378b9 100644 --- a/docs/tutorials/kubernetes-basics/public/css/styles.css +++ b/docs/tutorials/kubernetes-basics/public/css/styles.css @@ -9883,12 +9883,21 @@ p a:hover background: #f8f8f8; } +.content.katacoda-content { + padding: 0; + max-width: 100%; +} + +.content.katacoda-content .btn-success { + margin-bottom: 50px; +} + .katacoda { display: table; width: 100%; - margin: 50px 0; + margin: 0 0 50px 0; } @media screen and (max-width: 762px) { diff --git a/docs/tutorials/kubernetes-basics/scale-interactive.html b/docs/tutorials/kubernetes-basics/scale-interactive.html index dba3f3b1df..e4b1449aa3 100644 --- a/docs/tutorials/kubernetes-basics/scale-interactive.html +++ b/docs/tutorials/kubernetes-basics/scale-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Scaling Your App
-
+
diff --git a/docs/tutorials/kubernetes-basics/update-interactive.html b/docs/tutorials/kubernetes-basics/update-interactive.html index e011269f1d..5a3c1cb0b3 100644 --- a/docs/tutorials/kubernetes-basics/update-interactive.html +++ b/docs/tutorials/kubernetes-basics/update-interactive.html @@ -13,7 +13,7 @@ title: Interactive Tutorial - Updating Your App
-
+
From b9c0d80bbc94edf08dce29929b958c58243a3aa2 Mon Sep 17 00:00:00 2001 From: caiyixiang Date: Sat, 14 Jan 2017 15:07:09 +0800 Subject: [PATCH 12/44] Update ingress.md --- docs/user-guide/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index 788cabaa4b..f27788ccf9 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -107,7 +107,7 @@ Where `107.178.254.228` is the IP allocated by the Ingress controller to satisfy ### Simple fanout -As described previously, pods within kubernetes have IPs only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancers. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: +As described previously, pods within kubernetes have IPs only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancer. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: ```shell foo.bar.com -> 178.91.123.132 -> / foo s1:80 From 4bd2d4ce8ef266b2eebf6060e837785dd07e618a Mon Sep 17 00:00:00 2001 From: caiyixiang Date: Wed, 18 Jan 2017 08:33:28 +0800 Subject: [PATCH 13/44] Update ingress.md --- docs/user-guide/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index f27788ccf9..9768044bc9 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -69,7 +69,7 @@ spec: *POSTing this to the API server will have no effect if you have not configured an [Ingress controller](#ingress-controllers).* -__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields. For general information about working with config files, see [here](docs/user-guide/deploying-applications), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources). +__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields. For general information about working with config files, see [here](/docs/user-guide/deploying-applications), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources). __Lines 5-7__: Ingress [spec](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/api-conventions.md#spec-and-status) has all the information needed to configure a loadbalancer or proxy server. Most importantly, it contains a list of rules matched against all incoming requests. Currently the Ingress resource only supports http rules. From 4fb669be1176051ec83009e308f3703bc6b5e448 Mon Sep 17 00:00:00 2001 From: gregoplex Date: Tue, 17 Jan 2017 20:35:24 -0500 Subject: [PATCH 14/44] Fixed doc typo --- .../v1.5/documents/_generated_pod_v1_concept.md | 4 ++-- docs/api-reference/v1.5/index.html | 6 +++--- .../v1.5/documents/_generated_pod_v1_concept.md | 2 +- docs/resources-reference/v1.5/index.html | 4 ++-- .../kubectl/v1.5/documents/_generated_pod_v1_concept.md | 4 ++-- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/api-reference/v1.5/documents/_generated_pod_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_pod_v1_concept.md index c2ee5b3e4c..6d8c03649d 100644 --- a/docs/api-reference/v1.5/documents/_generated_pod_v1_concept.md +++ b/docs/api-reference/v1.5/documents/_generated_pod_v1_concept.md @@ -8,7 +8,7 @@ ```bdocs-tab:kubectl_yaml apiVersion: v1 -kind: Pob +kind: Pod metadata: name: pod-example spec: @@ -24,7 +24,7 @@ spec: ```bdocs-tab:curl_yaml apiVersion: v1 -kind: Pob +kind: Pod metadata: name: pod-example spec: diff --git a/docs/api-reference/v1.5/index.html b/docs/api-reference/v1.5/index.html index cc96bf697e..a665a89afe 100644 --- a/docs/api-reference/v1.5/index.html +++ b/docs/api-reference/v1.5/index.html @@ -7525,7 +7525,7 @@ $ kubectl get job example-job apiVersion: v1 -kind: Pob +kind: Pod metadata: name: pod-example spec: @@ -7539,7 +7539,7 @@ $ kubectl get job example-job apiVersion: v1 -kind: Pob +kind: Pod metadata: name: pod-example spec: @@ -51827,4 +51827,4 @@ Appears In Scale - \ No newline at end of file + diff --git a/docs/resources-reference/v1.5/documents/_generated_pod_v1_concept.md b/docs/resources-reference/v1.5/documents/_generated_pod_v1_concept.md index 6f6dd45764..ecba5a31be 100644 --- a/docs/resources-reference/v1.5/documents/_generated_pod_v1_concept.md +++ b/docs/resources-reference/v1.5/documents/_generated_pod_v1_concept.md @@ -8,7 +8,7 @@ ```bdocs-tab:example_yaml apiVersion: v1 -kind: Pob +kind: Pod metadata: name: pod-example spec: diff --git a/docs/resources-reference/v1.5/index.html b/docs/resources-reference/v1.5/index.html index 78713687ec..688ce5a06e 100644 --- a/docs/resources-reference/v1.5/index.html +++ b/docs/resources-reference/v1.5/index.html @@ -947,7 +947,7 @@ Appears In Job 

 apiVersion: v1
-kind: Pob
+kind: Pod
 metadata:
   name: pod-example
 spec:
@@ -10846,4 +10846,4 @@ Appears In Scale 
 
 
 
-
\ No newline at end of file
+
diff --git a/docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_concept.md b/docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_concept.md
index 0a7e20fdd3..603087e505 100644
--- a/docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_concept.md
+++ b/docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_concept.md
@@ -8,7 +8,7 @@
 ```bdocs-tab:kubectl_yaml
 
 apiVersion: v1
-kind: Pob
+kind: Pod
 metadata:
   name: pod-example
 spec:
@@ -24,7 +24,7 @@ spec:
 ```bdocs-tab:curl_yaml
 
 apiVersion: v1
-kind: Pob
+kind: Pod
 metadata:
   name: pod-example
 spec:

From f86d09dab3d0e46c27b2c2b7ddede3fb4713bcff Mon Sep 17 00:00:00 2001
From: Peter Lee 
Date: Wed, 18 Jan 2017 12:57:01 +0800
Subject: [PATCH 15/44] fix broken link

---
 docs/getting-started-guides/dcos.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started-guides/dcos.md b/docs/getting-started-guides/dcos.md
index d99f2d332e..5479ec10b9 100644
--- a/docs/getting-started-guides/dcos.md
+++ b/docs/getting-started-guides/dcos.md
@@ -32,7 +32,7 @@ Explore the following resources for more information about Kubernetes, Kubernete
 - [DCOS Documentation](https://docs.mesosphere.com/)
 - [Managing DCOS Services](https://docs.mesosphere.com/services/kubernetes/)
 - [Kubernetes Examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/)
-- [Kubernetes on Mesos Documentation](https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/README.md)
+- [Kubernetes on Mesos Documentation](https://github.com/kubernetes-incubator/kube-mesos-framework/blob/master/README.md)
 - [Kubernetes on Mesos Release Notes](https://github.com/mesosphere/kubernetes-mesos/releases)
 - [Kubernetes on DCOS Package Source](https://github.com/mesosphere/kubernetes-mesos)
 

From 0168fbc0299dfc2c9ba4eee1023154b6edf8ad6e Mon Sep 17 00:00:00 2001
From: khalpin11 
Date: Wed, 18 Jan 2017 09:32:37 -0700
Subject: [PATCH 16/44] Fix docs typo

"Action use IaaS providers reliable storage (e.g. GCE PD or AWS EBS volume) for VMs with apiserver+etcd" did not follow the same format as other actions in this section.
---
 docs/admin/cluster-troubleshooting.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/admin/cluster-troubleshooting.md b/docs/admin/cluster-troubleshooting.md
index ff8358a7a9..7e11eb12b0 100644
--- a/docs/admin/cluster-troubleshooting.md
+++ b/docs/admin/cluster-troubleshooting.md
@@ -89,7 +89,7 @@ Mitigations:
   - Mitigates: Apiserver VM shutdown or apiserver crashing
   - Mitigates: Supporting services VM shutdown or crashes
 
-- Action use IaaS providers reliable storage (e.g. GCE PD or AWS EBS volume) for VMs with apiserver+etcd
+- Action: Use IaaS providers reliable storage (e.g. GCE PD or AWS EBS volume) for VMs with apiserver+etcd
   - Mitigates: Apiserver backing storage lost
 
 - Action: Use (experimental) [high-availability](/docs/admin/high-availability) configuration
@@ -112,4 +112,4 @@ Mitigations:
   - Mitigates: Kubelet software fault
 
 - Action: [Multiple independent clusters](/docs/admin/multi-cluster) (and avoid making risky changes to all clusters at once)
-  - Mitigates: Everything listed above.
\ No newline at end of file
+  - Mitigates: Everything listed above.

From f09116b8e347cb566d253314ec65582b04855b17 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 13:30:16 -0800
Subject: [PATCH 17/44] Moved pod termination info to a temporary, unlinked
 file.

Added title to abstractions overview and pod overview.
---
 docs/concepts/abstractions/overview.md        |  1 +
 docs/concepts/abstractions/pod-termination.md | 15 +++++++++++++++
 docs/concepts/abstractions/pod.md             | 15 +--------------
 3 files changed, 17 insertions(+), 14 deletions(-)
 create mode 100644 docs/concepts/abstractions/pod-termination.md

diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index 8407eecf43..7665607858 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -1,4 +1,5 @@
 ---
+title: Kubernetes Objects
 ---
 
 {% capture overview %}
diff --git a/docs/concepts/abstractions/pod-termination.md b/docs/concepts/abstractions/pod-termination.md
new file mode 100644
index 0000000000..5276dae617
--- /dev/null
+++ b/docs/concepts/abstractions/pod-termination.md
@@ -0,0 +1,15 @@
+---
+---
+
+####  Pod Termination
+
+Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
+
+1. You send a command or API call to terminate the Pod.
+1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period).
+1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod.
+1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down.
+1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod.
+1. Kubernetes removes the Pod from the API server on the Kubernetes Master.
+
+> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
\ No newline at end of file
diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index fb65c8b33c..d41d2ad1ac 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -1,4 +1,5 @@
 ---
+title: Pods
 ---
 
 {% capture overview %}
@@ -9,7 +10,6 @@ This page provides an overview of `Pod`, the smallest deployable object in the K
 {:toc}
 
 {% capture body %}
-### Understanding Pods
 
 A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.
 
@@ -67,19 +67,6 @@ Some examples of Controllers that contain one or more pods include:
 
 In general, Controllers use a [Pod Template]() that you provide to create the Pods for which it is responsible.
 
-####  Pod Termination
-
-Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
-
-1. You send a command or API call to terminate the Pod.
-1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period).
-1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod.
-1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down.
-1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod.
-1. Kubernetes removes the Pod from the API server on the Kubernetes Master.
-
-> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
-
 {% endcapture %}
 
 

From 71d04d711491ec20a3bdf05cd8c0a1a29d40c598 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 13:45:21 -0800
Subject: [PATCH 18/44] Removed all blank links. Inserted links to StatefulSet
 content. Addressed remaining feedback.

---
 docs/concepts/abstractions/overview.md |  6 +++---
 docs/concepts/abstractions/pod.md      | 16 +++++++++-------
 docs/concepts/index.md                 | 20 +++++---------------
 3 files changed, 17 insertions(+), 25 deletions(-)

diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index 7665607858..2acadcafa5 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -21,9 +21,9 @@ To work with Kubernetes objects--whether to create, modify, or delete them--you'
 
 #### Object Spec and Status
 
-Every Kubernetes object includes two nested object fields that govern the object's configuration: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied and updated by the Kubernetes system. At any given time, the [Kubernetes Control Plane](/docs/concepts/control-plane/overview/) actively manages an object's actual state to match the desired state you supplied.
+Every Kubernetes object includes two nested object fields that govern the object's configuration: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied and updated by the Kubernetes system. At any given time, the Kubernetes Control Plane actively manages an object's actual state to match the desired state you supplied.
 
-For example, a Kubernetes [Deployment]() is an object that can represent an application running on your cluster. When you create the Deployment, you might set the Deployment spec to specify that you want three replicas of the application to be running. The Kubernetes system reads the Deployment spec and starts three instances of your desired application--updating the status to match your spec. If any of those instances should fail (a status change), the Kubernetes system reacts to the difference between spec and status by making a correction--in this case, starting a replacement instance.
+For example, a Kubernetes Deployment is an object that can represent an application running on your cluster. When you create the Deployment, you might set the Deployment spec to specify that you want three replicas of the application to be running. The Kubernetes system reads the Deployment spec and starts three instances of your desired application--updating the status to match your spec. If any of those instances should fail (a status change), the Kubernetes system reacts to the difference between spec and status by making a correction--in this case, starting a replacement instance.
 
 For more information on the object spec, status, and metadata, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status).
 
@@ -31,7 +31,7 @@ For more information on the object spec, status, and metadata, see the [Kubernet
 
 When you create an object in Kubernetes, you must provide the object spec that describes your desired state for it, as well as some basic information about the object (such as a name). When you use the Kubernetes API to create the object (either directly or via `kubectl`), that API call sends the information to the Kubernetes Master as JSON. **You can express that JSON using a `.yaml` file.**
 
-Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes [Deployment](/docs/concepts/abstractions/deployment/):
+Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes Deployment:
 
 {% include code.html language="yaml" file="/docs/user-guide/nginx-deployment.yaml" ghlink="/docs/user-guide/nginx-deployment.yaml" %}
 
diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index d41d2ad1ac..70c865b490 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -27,7 +27,9 @@ The [Kubernetes Blog](http://blog.kubernetes.io) has some additional information
 * [The Distributed System Toolkit: Patterns for Composite Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html)
 * [Container Design Patterns](http://blog.kubernetes.io/2016/06/container-design-patterns.html)
 
-Note that each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, such Pods are usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
+Each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, such Pods are usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
+
+> Note: Restarting a container in a Pod should not be confused with _restarting_ the Pod itself.  The Pod itself does not run, but is an environment the containers run in and persists until it is deleted.
 
 #### How Pods Manage Multiple Containers
 
@@ -45,11 +47,11 @@ Each Pod is assigned a unique IP address. Every the container in a pod shares th
 
 ##### Storage
 
-A Pod can specify a set of shared storage *volumes*. All containers in the pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a pod to survive in case one of the containers within needs to be restarted. See [Volumes]() for more information on how Kubernetes implements shared storage in a Pod.
+A Pod can specify a set of shared storage *volumes*. All containers in the pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.
 
 ### Working with Pods
 
-You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a [node]() in your cluster. The Pod remains on that node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources.
+You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a node in your your cluster. The Pod remains on that node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources.
 
 > Note: Restarting a container in a Pod should not be confused with restarting the Pod. The Pod itself does not run, but is an environment the containers run in and persists until it is deleted.
 
@@ -61,11 +63,11 @@ A Controller can create and manage multiple Pods for you, handling replication a
 
 Some examples of Controllers that contain one or more pods include:
 
-* [Deployment]()
-* [StatefulSet]()
-* [DaemonSet]()
+* Deployment
+* [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/)
+* DaemonSet
 
-In general, Controllers use a [Pod Template]() that you provide to create the Pods for which it is responsible.
+In general, Controllers use a Pod Template that you provide to create the Pods for which it is responsible.
 
 {% endcapture %}
 
diff --git a/docs/concepts/index.md b/docs/concepts/index.md
index 1afc20d43b..9ae7b9134b 100644
--- a/docs/concepts/index.md
+++ b/docs/concepts/index.md
@@ -26,11 +26,11 @@ The basic Kubernetes objects include:
 * Volume
 * Namespace
 
-In addition, Kubernetes contains a number of higher-level abstractions that build upon the basic objects, and provide additional functionality and convenience features. They include:
+In addition, Kubernetes contains a number of higher-level abstractions called Controllers. Controllers build upon the basic objects, and provide additional functionality and convenience features. They include:
 
 * ReplicaSet
 * Deployment
-* StatefulSet
+* [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/))
 * DaemonSet
 * Job
 
@@ -42,29 +42,19 @@ For example, When you use the Kubernetes API to create a Deployment object, for
 
 ### Kubernetes Master
 
-The Kubernetes master is responsible for maintaining the desired state for your cluster. The Kubernetes master(s) runs the following processes:
+The Kubernetes master is responsible for maintaining the desired state for your cluster. When you interact with Kubernetes, such as by using the `kubectl` command-line interface, you're communicating with your cluster's Kubernetes master.
 
-* API Server
-* Scheduler
-* Etcd
-* Controller Manager
+> The "master" refers to a collection of processes managing the cluster state.  Typically these processes are all run on a single node in the cluster, and this node is also referred to as the master. The master can also be replicated for availability and redundnacy.
 
 ### Kubernetes Nodes
 
-The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. These nodes are controlled by the Kubernetes master. The following processes run on each node in a Kubernetes cluster:
-
-* Kubelet
-* Docker-daemon
-* kube-proxy
+The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. The Kubernetes master controls each node; you'll rarely interact with nodes directly.
 
 #### Object Metadata
 
 
 * [Annotations](/docs/concepts/object-metadata/annotations/)
 
-#### Controllers
-* [StatefulSets](/docs/concepts/abstractions/controllers/statefulsets/)
-
 
 ### What's next
 

From 86d6b19a17cacbfaed786a17fab584ac3248475e Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 13:55:20 -0800
Subject: [PATCH 19/44] Added TOC entries and skip-titles entries for Concepts
 files.

---
 _data/concepts.yml   | 12 +++++++++---
 skip_title_check.txt |  1 +
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/_data/concepts.yml b/_data/concepts.yml
index a9a7c3eb29..69c3bed524 100644
--- a/_data/concepts.yml
+++ b/_data/concepts.yml
@@ -2,9 +2,15 @@ bigheader: "Concepts"
 abstract: "Detailed explanations of Kubernetes system concepts and abstractions."
 toc:
 - docs/concepts/index.md
+section:
+- title: Kubernetes Objects
+  section:
+  - docs/concepts/abstractions/overview.md
+  - docs/concepts/pod.md
+  - title: Controllers
+    section:
+    - docs/concepts/abstractions/controllers/statefulsets.md
+
 - title: Object Metadata
   section:
   - docs/concepts/object-metadata/annotations.md
-- title: Controllers
-  section:
-  - docs/concepts/abstractions/controllers/statefulsets.md
diff --git a/skip_title_check.txt b/skip_title_check.txt
index 3c62da283d..90ac6482c5 100644
--- a/skip_title_check.txt
+++ b/skip_title_check.txt
@@ -9,3 +9,4 @@ docs/api-reference/v1/definitions.md
 docs/api-reference/v1/operations.md
 docs/user-guide/pods/_viewing-a-pod.md
 docs/user-guide/simple-yaml.md
+docs/concepts/abstractions/pod-termination.md
\ No newline at end of file

From cd49c123cdbd5df2c443e1c1b547cc37a511b30a Mon Sep 17 00:00:00 2001
From: Peter Lee 
Date: Wed, 18 Jan 2017 11:37:46 +0800
Subject: [PATCH 20/44] fix broken links

fix some broken links in /docs/getting-started-guides/mesos/
---
 docs/getting-started-guides/mesos/index.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/getting-started-guides/mesos/index.md b/docs/getting-started-guides/mesos/index.md
index 499ff0ba51..b30482a9a1 100644
--- a/docs/getting-started-guides/mesos/index.md
+++ b/docs/getting-started-guides/mesos/index.md
@@ -11,7 +11,7 @@ title: Kubernetes on Mesos
 
 
 
-Mesos allows dynamic sharing of cluster resources between Kubernetes and other first-class Mesos frameworks such as [Hadoop][1], [Spark][2], and [Chronos][3].
+Mesos allows dynamic sharing of cluster resources between Kubernetes and other first-class Mesos frameworks such as [HDFS][1], [Spark][2], and [Chronos][3].
 Mesos also ensures applications from different frameworks running on your cluster are isolated and that resources are allocated fairly among them.
 
 Mesos clusters can be deployed on nearly every IaaS cloud provider infrastructure or in your own physical datacenter. Kubernetes on Mesos runs on-top of that and therefore allows you to easily move Kubernetes workloads from one of these environments to the other.
@@ -325,16 +325,16 @@ Future work will add instructions to this guide to enable support for Kubernetes
 
 **NOTE:** Please be aware that there are [known issues with the current Kubernetes-Mesos implementation][7].
 
-[1]: http://mesosphere.com/docs/tutorials/run-hadoop-on-mesos-using-installer
-[2]: http://mesosphere.com/docs/tutorials/run-spark-on-mesos
-[3]: http://mesosphere.com/docs/tutorials/run-chronos-on-mesos
+[1]: https://docs.mesosphere.com/latest/usage/service-guides/hdfs/
+[2]: https://docs.mesosphere.com/latest/usage/service-guides/spark/
+[3]: https://docs.mesosphere.com/latest/usage/service-guides/chronos/
 [4]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md
-[5]: http://open.mesosphere.com/getting-started/cloud/google/mesosphere/
+[5]: https://dcos.io/docs/latest/administration/installing/cloud/gce/
 [6]: http://mesos.apache.org/
-[7]: https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/docs/issues.md
+[7]: https://github.com/kubernetes-incubator/kube-mesos-framework/blob/master/docs/issues.md
 [8]: https://github.com/mesosphere/kubernetes-mesos/issues
 [9]: https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples
 [10]: http://open.mesosphere.com/getting-started/cloud/google/mesosphere/#vpn-setup
 [11]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/skydns-rc.yaml.in
 [12]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/skydns-svc.yaml.in
-[13]: https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/README.md
+[13]: https://github.com/kubernetes-incubator/kube-mesos-framework/blob/master/README.md

From 58dc06f510114432ec3bedf397b61240f838c4b6 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:09:52 -0800
Subject: [PATCH 21/44] Fixed bug in TOC file; added pod-termination to
 skip_toc_check.

---
 _data/concepts.yml | 2 +-
 skip_toc_check.txt | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/_data/concepts.yml b/_data/concepts.yml
index 69c3bed524..a91c1b86d6 100644
--- a/_data/concepts.yml
+++ b/_data/concepts.yml
@@ -6,7 +6,7 @@ section:
 - title: Kubernetes Objects
   section:
   - docs/concepts/abstractions/overview.md
-  - docs/concepts/pod.md
+  - docs/concepts/abstractions/pod.md
   - title: Controllers
     section:
     - docs/concepts/abstractions/controllers/statefulsets.md
diff --git a/skip_toc_check.txt b/skip_toc_check.txt
index 00d5a5bdec..255bb26d10 100644
--- a/skip_toc_check.txt
+++ b/skip_toc_check.txt
@@ -8,3 +8,4 @@ docs/user-guide/walkthrough/k8s201.md
 docs/user-guide/logging-demo/README.md
 docs/user-guide/downward-api/README.md
 docs/user-guide/configmap/README.md
+docs/concepts/abstractions/pod-termination.md
\ No newline at end of file

From 2a5394ae7e13fd7add246613fd337e3922a9feb7 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:15:31 -0800
Subject: [PATCH 22/44] Added sample .yaml file to concepts directory.

---
 docs/concepts/abstractions/nginx-deployment.yaml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 docs/concepts/abstractions/nginx-deployment.yaml

diff --git a/docs/concepts/abstractions/nginx-deployment.yaml b/docs/concepts/abstractions/nginx-deployment.yaml
new file mode 100644
index 0000000000..7a0dd431ef
--- /dev/null
+++ b/docs/concepts/abstractions/nginx-deployment.yaml
@@ -0,0 +1,16 @@
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: nginx-deployment
+spec:
+  replicas: 3
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.7.9
+        ports:
+        - containerPort: 80

From 65de831b9c7fa0de67a4fab70692bfa548d32d24 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:16:33 -0800
Subject: [PATCH 23/44] Fixed bug in line to include sample deployment yaml.

---
 docs/concepts/abstractions/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index 2acadcafa5..74d223361d 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -33,7 +33,7 @@ When you create an object in Kubernetes, you must provide the object spec that d
 
 Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes Deployment:
 
-{% include code.html language="yaml" file="/docs/user-guide/nginx-deployment.yaml" ghlink="/docs/user-guide/nginx-deployment.yaml" %}
+{% include code.html language="yaml" file="nginx-deployment.yaml" ghlink="/docs/concepts/abstractions/nginx-deployment.yaml" %}
 
 One way to create a Deployment using a `.yaml` file like the one above is to use the []`kubectl create`]() command in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example:
 

From 34d349d7b870d261357f3b87eb557c0e2e772688 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:23:41 -0800
Subject: [PATCH 24/44] More bug fixes for TOC, titling, and formatting.

---
 _data/concepts.yml     | 12 ++++++------
 docs/concepts/index.md |  2 +-
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/_data/concepts.yml b/_data/concepts.yml
index a91c1b86d6..bd1b5d7f7e 100644
--- a/_data/concepts.yml
+++ b/_data/concepts.yml
@@ -2,14 +2,14 @@ bigheader: "Concepts"
 abstract: "Detailed explanations of Kubernetes system concepts and abstractions."
 toc:
 - docs/concepts/index.md
-section:
-- title: Kubernetes Objects
   section:
-  - docs/concepts/abstractions/overview.md
-  - docs/concepts/abstractions/pod.md
-  - title: Controllers
+  - title: Kubernetes Objects
     section:
-    - docs/concepts/abstractions/controllers/statefulsets.md
+    - docs/concepts/abstractions/overview.md
+    - docs/concepts/abstractions/pod.md
+    - title: Controllers
+      section:
+      - docs/concepts/abstractions/controllers/statefulsets.md
 
 - title: Object Metadata
   section:
diff --git a/docs/concepts/index.md b/docs/concepts/index.md
index 9ae7b9134b..bbe2c9844c 100644
--- a/docs/concepts/index.md
+++ b/docs/concepts/index.md
@@ -30,7 +30,7 @@ In addition, Kubernetes contains a number of higher-level abstractions called Co
 
 * ReplicaSet
 * Deployment
-* [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/))
+* [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/)
 * DaemonSet
 * Job
 

From e84e00467012af3072d472bd640fbf5b1a62454a Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:25:41 -0800
Subject: [PATCH 25/44] TOC fix.

---
 _data/concepts.yml | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/_data/concepts.yml b/_data/concepts.yml
index bd1b5d7f7e..41aefaaedf 100644
--- a/_data/concepts.yml
+++ b/_data/concepts.yml
@@ -3,13 +3,11 @@ abstract: "Detailed explanations of Kubernetes system concepts and abstractions.
 toc:
 - docs/concepts/index.md
   section:
-  - title: Kubernetes Objects
+  - docs/concepts/abstractions/overview.md
+  - docs/concepts/abstractions/pod.md
+  - title: Controllers
     section:
-    - docs/concepts/abstractions/overview.md
-    - docs/concepts/abstractions/pod.md
-    - title: Controllers
-      section:
-      - docs/concepts/abstractions/controllers/statefulsets.md
+    - docs/concepts/abstractions/controllers/statefulsets.md
 
 - title: Object Metadata
   section:

From 16917fc25868031cd8a4a828eff33f9800dea9d6 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:27:43 -0800
Subject: [PATCH 26/44] TOC fix, redux.

---
 _data/concepts.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/_data/concepts.yml b/_data/concepts.yml
index 41aefaaedf..4102b5f142 100644
--- a/_data/concepts.yml
+++ b/_data/concepts.yml
@@ -2,6 +2,8 @@ bigheader: "Concepts"
 abstract: "Detailed explanations of Kubernetes system concepts and abstractions."
 toc:
 - docs/concepts/index.md
+
+- title: Kubernetes Objects
   section:
   - docs/concepts/abstractions/overview.md
   - docs/concepts/abstractions/pod.md

From 7d7074801bec0db56158d67adc63577cd7289914 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:34:27 -0800
Subject: [PATCH 27/44] Attempted fix of Pod page template.

---
 docs/concepts/abstractions/pod.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index 70c865b490..022e51ceaf 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -10,6 +10,7 @@ This page provides an overview of `Pod`, the smallest deployable object in the K
 {:toc}
 
 {% capture body %}
+### Understanding Pods
 
 A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.
 
@@ -71,11 +72,10 @@ In general, Controllers use a Pod Template that you provide to create the Pods f
 
 {% endcapture %}
 
+{% capture whatsnext %}
+* Learn more about Pod behavior:
+  * Pod Termination
+  * Other Pod Topics
+{% endcapture %}
 
-{% if whatsnext %}
-
-### What's next
-
-{{ whatsnext }}
-
-{% endif %}
\ No newline at end of file
+{% include templates/concept.md %}
\ No newline at end of file

From 90aab18a2a75d162fb7a4279abb774a437d0a553 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 14:43:18 -0800
Subject: [PATCH 28/44] Formatting fixes for Pod.

---
 docs/concepts/abstractions/pod.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index 022e51ceaf..ebef20584d 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -6,7 +6,6 @@ title: Pods
 This page provides an overview of `Pod`, the smallest deployable object in the Kubernetes object model.
 {% endcapture %}
 
-* TOC
 {:toc}
 
 {% capture body %}
@@ -58,7 +57,7 @@ You'll rarely create individual Pods directly in Kubernetes--even singleton Pods
 
 Pods do not, by themselves, self-heal. If a Pod is scheduled to a node that fails, or if the scheduling operation itself fails, the Pod is deleted; likewise, a Pod won't survive an eviction due to a lack of resources or node maintenance. Kubernetes uses a higher-level abstraction, called a *Controller*, that handles the work of managing the relatively disposable Pod instances. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a Controller. See [Pods and Controllers](#pods-and-controllers) for more information on how Kubernetes uses Controllers to implement Pod scaling and healing.
 
-####  Pods and Controllers
+#### Pods and Controllers
 
 A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope. For example, if a node fails, the Controller might automatically replace the Pod by scheduling an identical replacement on a different node). 
 

From 1d289b91934ac82460ecfbe44ecc9b4e57d86083 Mon Sep 17 00:00:00 2001
From: Devin Donnelly 
Date: Wed, 18 Jan 2017 15:21:02 -0800
Subject: [PATCH 29/44] Fixed wording in response to feedback from pwittrock.

---
 docs/concepts/abstractions/overview.md | 10 +++++-----
 docs/concepts/abstractions/pod.md      | 16 +++++++---------
 docs/concepts/index.md                 |  4 ++--
 3 files changed, 14 insertions(+), 16 deletions(-)

diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index 74d223361d..ffed154293 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -15,23 +15,23 @@ This page explains how Kubernetes objects are represented in the Kubernetes API,
 * The resources available to those applications
 * The policies around how those applications behave, such as restart policies, upgrades, and fault-tolerance
 
-When you create a Kubernetes object, you create a "record of intent"--once you create the object, the Kubernetes system will constantly work to ensure that that object exists. By creating an object, you're effectively telling the Kubernetes system what you want your cluster's workload to look like; this is your cluster's **desired state**.
+A Kubernetes object is a "record of intent"--once you create the object, the Kubernetes system will constantly work to ensure that that object exists. By creating an object, you're effectively telling the Kubernetes system what you want your cluster's workload to look like; this is your cluster's **desired state**.
 
-To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. Kubernetes currently provides a `golang` client library for this purpose, and other language libraries are being developed.
+To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. Kubernetes currently provides a `golang` [client library](https://github.com/kubernetes/client-go) for this purpose, and other language libraries (such as [Python](https://github.com/kubernetes-incubator/client-python)) are being developed.
 
 #### Object Spec and Status
 
 Every Kubernetes object includes two nested object fields that govern the object's configuration: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied and updated by the Kubernetes system. At any given time, the Kubernetes Control Plane actively manages an object's actual state to match the desired state you supplied.
 
-For example, a Kubernetes Deployment is an object that can represent an application running on your cluster. When you create the Deployment, you might set the Deployment spec to specify that you want three replicas of the application to be running. The Kubernetes system reads the Deployment spec and starts three instances of your desired application--updating the status to match your spec. If any of those instances should fail (a status change), the Kubernetes system reacts to the difference between spec and status by making a correction--in this case, starting a replacement instance.
+For example, a Kubernetes Deployment is an object that can represent an application running on your cluster. When you create the Deployment, you might set the Deployment spec to specify that you want three replicas of the application to be running. The Kubernetes system reads the Deployment spec and starts three instances of your desired application--updating the status to match your spec. If any of those instances should fail (a status change), the Kubernetes system responds to the difference between spec and status by making a correction--in this case, starting a replacement instance.
 
 For more information on the object spec, status, and metadata, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status).
 
 #### Describing a Kubernetes Object
 
-When you create an object in Kubernetes, you must provide the object spec that describes your desired state for it, as well as some basic information about the object (such as a name). When you use the Kubernetes API to create the object (either directly or via `kubectl`), that API call sends the information to the Kubernetes Master as JSON. **You can express that JSON using a `.yaml` file.**
+When you create an object in Kubernetes, you must provide the object spec that describes its desired state, as well as some basic information about the object (such as a name). When you use the Kubernetes API to create the object (either directly or via `kubectl`), that API request must include that information as JSON in the request body. **Most often, you provide the information to `kubectl` in a .yaml file.** `kubectl` converts the information to JSON when making the API request.
 
-Here's an example `.yaml` file that shows an example of the required fields and object spec for a Kubernetes Deployment:
+Here's an example `.yaml` file that shows the required fields and object spec for a Kubernetes Deployment:
 
 {% include code.html language="yaml" file="nginx-deployment.yaml" ghlink="/docs/concepts/abstractions/nginx-deployment.yaml" %}
 
diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index ebef20584d..82d6407a8e 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -20,16 +20,14 @@ A Pod encapsulates an application container (or, in some cases, multiple contain
 Pods are employed a number of ways in a Kubernetes cluster, including:
 
 * **Pods that run a single container**. The "one-container-per-Pod" model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single container, and Kubernetes manages the Pods rather than the containers directly.
-* **Pods that run multiple containers that need to work together**. A Pod might encapsulate an application that relies on multiple co-located containers that are tightly coupled and need to share resources. These co-located containers might form a single cohesive unit of service--one container serving files from a shared volume to the public, while a separate "sidecar" container refreshes or updates those files. The Pod wraps these containers and storage resources together as a single managable entity.
+* **Pods that run multiple containers that need to work together**. A Pod might encapsulate an application composed multiple co-located containers that are tightly coupled and need to share resources. These co-located containers might form a single cohesive unit of service--one container serving files from a shared volume to the public, while a separate "sidecar" container refreshes or updates those files. The Pod wraps these containers and storage resources together as a single managable entity.
 
 The [Kubernetes Blog](http://blog.kubernetes.io) has some additional information on Pod use cases. For more information, see:
 
 * [The Distributed System Toolkit: Patterns for Composite Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html)
 * [Container Design Patterns](http://blog.kubernetes.io/2016/06/container-design-patterns.html)
 
-Each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, such Pods are usually managed by a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
-
-> Note: Restarting a container in a Pod should not be confused with _restarting_ the Pod itself.  The Pod itself does not run, but is an environment the containers run in and persists until it is deleted.
+Each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, this is generally referred to as _replication_. Replicated Pods are usually created and managed as a group by an abstraction called a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
 
 #### How Pods Manage Multiple Containers
 
@@ -43,23 +41,23 @@ Pods provide two kinds of shared resources for their constituent containers: *ne
 
 ##### Networking
 
-Each Pod is assigned a unique IP address. Every the container in a pod shares the network namespace, including the IP address and network ports. Containers *inside a Pod* can communicate with one another using `localhost`. When containers in a Pod communicate with entities *outside the Pod*, they must coordinate how they use the shared network resources (such as ports).
+Each Pod is assigned a unique IP address. Every the container in a Pod shares the network namespace, including the IP address and network ports. Containers *inside a Pod* can communicate with one another using `localhost`. When containers in a Pod communicate with entities *outside the Pod*, they must coordinate how they use the shared network resources (such as ports).
 
 ##### Storage
 
-A Pod can specify a set of shared storage *volumes*. All containers in the pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.
+A Pod can specify a set of shared storage *volumes*. All containers in the Pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a Pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.
 
 ### Working with Pods
 
-You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a node in your your cluster. The Pod remains on that node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources.
+You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a Node in your your cluster. The Pod remains on that Node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources, or the Node fails.
 
 > Note: Restarting a container in a Pod should not be confused with restarting the Pod. The Pod itself does not run, but is an environment the containers run in and persists until it is deleted.
 
-Pods do not, by themselves, self-heal. If a Pod is scheduled to a node that fails, or if the scheduling operation itself fails, the Pod is deleted; likewise, a Pod won't survive an eviction due to a lack of resources or node maintenance. Kubernetes uses a higher-level abstraction, called a *Controller*, that handles the work of managing the relatively disposable Pod instances. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a Controller. See [Pods and Controllers](#pods-and-controllers) for more information on how Kubernetes uses Controllers to implement Pod scaling and healing.
+Pods do not, by themselves, self-heal. If a Pod is scheduled to a Node that fails, or if the scheduling operation itself fails, the Pod is deleted; likewise, a Pod won't survive an eviction due to a lack of resources or Node maintenance. Kubernetes uses a higher-level abstraction, called a *Controller*, that handles the work of managing the relatively disposable Pod instances. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a Controller. See [Pods and Controllers](#pods-and-controllers) for more information on how Kubernetes uses Controllers to implement Pod scaling and healing.
 
 #### Pods and Controllers
 
-A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope. For example, if a node fails, the Controller might automatically replace the Pod by scheduling an identical replacement on a different node). 
+A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope. For example, if a Node fails, the Controller might automatically replace the Pod by scheduling an identical replacement on a different Node). 
 
 Some examples of Controllers that contain one or more pods include:
 
diff --git a/docs/concepts/index.md b/docs/concepts/index.md
index bbe2c9844c..3f131c6358 100644
--- a/docs/concepts/index.md
+++ b/docs/concepts/index.md
@@ -36,9 +36,9 @@ In addition, Kubernetes contains a number of higher-level abstractions called Co
 
 ## Kubernetes Control Plane
 
-The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. The Control Plane maintains a record of all of the Kubernetes Objects in the system, and runs continuous control loops to manage those objects' state. At any given time, the Control Plane's control loops will attempt to match the actual state of all the objects in the system to the desired state that you provided when you created those objects.
+The various parts of the Kubernetes Control Plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster. The Control Plane maintains a record of all of the Kubernetes Objects in the system, and runs continuous control loops to manage those objects' state. At any given time, the Control Plane's control loops will respond to changes in the cluster and work to make the actual state of all the objects in the system to the desired state that you provided.
 
-For example, When you use the Kubernetes API to create a Deployment object, for example, you provide a new desired state for the system. The Kubernetes Control Plane records that object creation, and carries out your instructions by starting the required applications and scheduling them to cluster nodes--thus making the cluster's actual state match the desired state.
+For example, when you use the Kubernetes API to create a Deployment object, you provide a new desired state for the system. The Kubernetes Control Plane records that object creation, and carries out your instructions by starting the required applications and scheduling them to cluster nodes--thus making the cluster's actual state match the desired state.
 
 ### Kubernetes Master
 

From ee02a66f1257b499c823306434d3a3848b112083 Mon Sep 17 00:00:00 2001
From: steveperry-53 
Date: Wed, 18 Jan 2017 12:55:46 -0800
Subject: [PATCH 30/44] Remove 3 User Guide topics, redirect to Tasks.

---
 _data/guides.yml                          |   3 -
 docs/tasks/index.md                       |   6 +
 docs/user-guide/configuring-containers.md | 162 ----------------------
 docs/user-guide/pods/single-container.md  |  94 -------------
 docs/user-guide/simple-nginx.md           |  61 --------
 5 files changed, 6 insertions(+), 320 deletions(-)
 delete mode 100644 docs/user-guide/configuring-containers.md
 delete mode 100644 docs/user-guide/pods/single-container.md
 delete mode 100644 docs/user-guide/simple-nginx.md

diff --git a/_data/guides.yml b/_data/guides.yml
index c1bdd99a4e..fdade5b1ec 100644
--- a/_data/guides.yml
+++ b/_data/guides.yml
@@ -65,11 +65,8 @@ toc:
 
 - title: Containers and Pods
   section:
-  - docs/user-guide/simple-nginx.md
-  - docs/user-guide/pods/single-container.md
   - docs/user-guide/pods/multi-container.md
   - docs/user-guide/pods/init-container.md
-  - docs/user-guide/configuring-containers.md
   - docs/user-guide/pod-templates.md
   - docs/user-guide/containers.md
   - docs/user-guide/environment-guide/index.md
diff --git a/docs/tasks/index.md b/docs/tasks/index.md
index 544036b749..c16a22af7f 100644
--- a/docs/tasks/index.md
+++ b/docs/tasks/index.md
@@ -3,6 +3,12 @@ title: Tasks
 redirect_from:
 - "/docs/user-guide/production-pods/"
 - "/docs/user-guide/production-pods.html"
+- "/docs/user-guide/simple-nginx/"
+- "/docs/user-guide/simple-nginx.html"
+- "/docs/user-guide/pods/single-container/"
+- "/docs/user-guide/pods/single-container.html"
+- "/docs/user-guide/configuring-containers/"
+- "/docs/user-guide/configuring-containers.html"
 ---
 
 This section of the Kubernetes documentation contains pages that
diff --git a/docs/user-guide/configuring-containers.md b/docs/user-guide/configuring-containers.md
deleted file mode 100644
index 51ac150f07..0000000000
--- a/docs/user-guide/configuring-containers.md
+++ /dev/null
@@ -1,162 +0,0 @@
----
-assignees:
-- caesarxuchao
-- thockin
-title: Configuring Containers
----
-
-* TOC
-{:toc}
-
-## Configuration in Kubernetes
-
-In addition to the imperative-style commands, such as `kubectl run` and `kubectl expose`, described [elsewhere](/docs/user-guide/quick-start), Kubernetes supports declarative configuration. Oftentimes, configuration files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, which is especially important for more complex configurations, producing a more robust, reliable and archival system.
-
-In the declarative style, all configuration is stored in YAML or JSON configuration files using Kubernetes's API resource schemas as the configuration schemas. `kubectl` can create, update, delete, and get API resources. The `apiVersion` (currently `v1`?), resource `kind`, and resource `name` are used by `kubectl` to construct the appropriate API path to invoke for the specified operation.
-
-## Launching a container using a configuration file
-
-Kubernetes executes containers in [*Pods*](/docs/user-guide/pods). A pod containing a simple Hello World container can be specified in YAML as follows:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: hello-world
-spec:  # specification of the pod's contents
-  restartPolicy: Never
-  containers:
-  - name: hello
-    image: "ubuntu:14.04"
-    command: ["/bin/echo", "hello", "world"]
-```
-
-The value of `metadata.name`, `hello-world`, will be the name of the pod resource created, and must be unique within the cluster, whereas `containers[0].name` is just a nickname for the container within that pod. `image` is the name of the Docker image, which Kubernetes expects to be able to pull from a registry, the [Docker Hub](https://registry.hub.docker.com/) by default.
-
-`restartPolicy: Never` indicates that we just want to run the container once and then terminate the pod.
-
-The [`command`](/docs/user-guide/containers/#containers-and-commands) overrides the Docker container's `Entrypoint`. Command arguments (corresponding to Docker's `Cmd`) may be specified using `args`, as follows:
-
-```yaml
-    command: ["/bin/echo"]
-    args: ["hello","world"]
-```
-
-This pod can be created using the `create` command:
-
-```shell
-$ kubectl create -f ./hello-world.yaml
-pods/hello-world
-```
-
-`kubectl` prints the resource type and name of the resource created when successful.
-
-## Validating configuration
-
-We enable validation by default in `kubectl` since v1.1.
-
-Let's say you specified `entrypoint` instead of `command`. You'd see output as follows:
-
-```shell
-error validating "./hello-world.yaml": error validating data: found invalid field Entrypoint for v1.Container; if you choose to ignore these errors, turn validation off with --validate=false
-```
-
-Using `kubectl create --validate=false` to turn validation off, it creates the resource anyway, unless a required field is absent or a field value is invalid. Unknown API fields are ignored, so be careful. This pod was created, but with no `command`, which is an optional field, since the image may specify an `Entrypoint`.
-View the [Pod API
-object](/docs/api-reference/v1/definitions/#_v1_pod)
-to see the list of valid fields.
-
-## Environment variables and variable expansion
-
-Kubernetes [does not automatically run commands in a shell](https://github.com/kubernetes/kubernetes/wiki/User-FAQ#use-of-environment-variables-on-the-command-line) (not all images contain shells). If you would like to run your command in a shell, such as to expand environment variables (specified using `env`), you could do the following:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: hello-world
-spec:  # specification of the pod's contents
-  restartPolicy: Never
-  containers:
-  - name: hello
-    image: "ubuntu:14.04"
-    env:
-    - name: MESSAGE
-      value: "hello world"
-    command: ["/bin/sh","-c"]
-    args: ["/bin/echo \"${MESSAGE}\""]
-```
-
-However, a shell isn't necessary just to expand environment variables. Kubernetes will do it for you if you use [`$(ENVVAR)` syntax](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/expansion.md):
-
-```yaml
-    command: ["/bin/echo"]
-    args: ["$(MESSAGE)"]
-```
-
-## Viewing pod status
-
-You can see the pod you created (actually all of your cluster's pods) using the `get` command.
-
-If you're quick, it will look as follows:
-
-```shell
-$ kubectl get pods
-NAME          READY     STATUS    RESTARTS   AGE
-hello-world   0/1       Pending   0          0s
-```
-
-Initially, a newly created pod is unscheduled -- no node has been selected to run it. Scheduling happens after creation, but is fast, so you normally shouldn't see pods in an unscheduled state unless there's a problem.
-
-After the pod has been scheduled, the image may need to be pulled to the node on which it was scheduled, if it hadn't been pulled already. After a few seconds, you should see the container running:
-
-```shell
-$ kubectl get pods
-NAME          READY     STATUS    RESTARTS   AGE
-hello-world   1/1       Running   0          5s
-```
-
-The `READY` column shows how many containers in the pod are running.
-
-Almost immediately after it starts running, this command will terminate. `kubectl` shows that the container is no longer running and displays the exit status:
-
-```shell
-$ kubectl get pods --show-all
-NAME          READY     STATUS       RESTARTS   AGE
-hello-world   0/1       ExitCode:0   0          15s
-```
-
-## Viewing pod output
-
-You probably want to see the output of the command you ran. As with [`docker logs`](https://docs.docker.com/engine/reference/commandline/logs/), `kubectl logs` will show you the output:
-
-```shell
-$ kubectl logs hello-world
-hello world
-```
-
-## Deleting pods
-
-When you're done looking at the output, you should delete the pod:
-
-```shell
-$ kubectl delete pod hello-world
-pods/hello-world
-```
-
-As with `create`, `kubectl` prints the resource type and name of the resource deleted when successful.
-
-You can also use the resource/name format to specify the pod:
-
-```shell
-$ kubectl delete pods/hello-world
-pods/hello-world
-```
-
-Terminated pods aren't currently automatically deleted, so that you can observe their final status, so be sure to clean up your dead pods.
-
-On the other hand, containers and their logs are eventually deleted automatically in order to free up disk space on the nodes.
-
-## What's next?
-
-[Learn about deploying continuously running applications.](/docs/user-guide/deploying-applications)
diff --git a/docs/user-guide/pods/single-container.md b/docs/user-guide/pods/single-container.md
deleted file mode 100644
index 4fef42a2f9..0000000000
--- a/docs/user-guide/pods/single-container.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-assignees:
-- janetkuo
-title: Creating Single-Container Pods
----
-
-* TOC
-{:toc}
-
-A pod is a group of containers that are scheduled
-onto the same host. Pods serve as units of scheduling, deployment, and
-horizontal scaling/replication. Pods share fate, and share some resources, such
-as storage volumes and IP addresses.
-
-## Creating a pod
-
-Single-container pods can be created with the `run` command. The
-pod's properties are specified with flags on the command line.
-
-The `run` command creates a Deployment to monitor the pod(s).
-The Deployment watches for failed pods and will start up new pods as required
-to maintain the specified number.
-
-Note: If you don't want a Deployment to monitor your pod (e.g. your pod
-is writing non-persistent data which won't survive a restart, or your pod is
-intended to be very short-lived), you can
-[create a pod directly with the `create` command](/docs/user-guide/pods/multi-container/).
-
-To create a pod using the `run` command:
-
-```shell
-$ kubectl run NAME
-    --image=image
-    [--port=port]
-    [--replicas=replicas]
-    [--labels=key=value,key=value,...]
-```
-
-Where:
-
-* `kubectl run` creates a Deployment named "nginx" on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/kubectl_run/) for more details. 
-* `NAME` (required) is the name of the container to create. This value is also
-  applied as the name of the Deployment, and as the prefix of the
-  pod name. For example:
-  
-  ```shell 
-  $ kubectl run example --image=nginx
-  deployment "example" created
-
-  $ kubectl get pods -l run=example
-  NAME                       READY     STATUS    RESTARTS   AGE
-  example-1934187764-scau1   1/1       Running   0          13s
-  ```
-* `--image=IMAGE` (required) is the Docker container image to use for this
-   container.
-* `--port=PORT` is the port to expose on the container.
-* `--replicas=NUM` is the number of replicated pods to create. If not specified,
-  one pod will be created.
-* `--labels=key=value` specifies one or more labels to attach to the pod. In
-  addition to any labels specified here, `run` attaches a label of
-  the format `run=NAME`. This is used by the Deployment
-  to target the pods created by the command.
-  
-![image](/images/docs/pods/single-container_1.svg)  
-
-There are additional flags that can be specified. For a complete list, run:
-
-    $ kubectl run --help
-
-## Viewing a pod
-
-{% include_relative _viewing-a-pod.md %}
-
-## Deleting a pod
-
-If your pod was created using the `run` command, Kubernetes creates a
-[Deployment](/docs/user-guide/deployments/)
-to manage the pod. Pods managed by a Deployment are rescheduled if
-they go away, including being deleted by `kubectl delete pod`. To permanently
-delete the pod, delete its Deployment.
-
-First, find the Deployment's name:
-
-```shell
-$ kubectl get deployment 
-NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-example   1         1         1            1           1m
-```
-
-Then, `delete` the Deployment:
-
-```shell
-$ kubectl delete deployment DEPLOYMENT_NAME
-```
diff --git a/docs/user-guide/simple-nginx.md b/docs/user-guide/simple-nginx.md
deleted file mode 100644
index 83011310a5..0000000000
--- a/docs/user-guide/simple-nginx.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-assignees:
-- mikedanese
-title: Running Your First Containers
----
-
-Ok, you've run one of the [getting started guides](/docs/getting-started-guides/) and you have
-successfully turned up a Kubernetes cluster.  Now what?  This guide will help you get oriented
-to Kubernetes and running your first containers on the cluster.
-
-### Running a container (simple version)
-
-From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides.
-
-The [`kubectl run`](/docs/user-guide/kubectl/kubectl_run) line below will create a [`Deployment`](/docs/user-guide/deployments) named `my-nginx`, and 
-two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/docs/user-guide/pods) listening on port 80. The `Deployment` will ensure that there are 
-always exactly two pods running as specified in its spec. 
-
-```shell
-kubectl run my-nginx --image=nginx --replicas=2 --port=80
-```
-
-Once the pods are created, you can list them to see what is up and running:
-
-```shell
-kubectl get pods
-```
-
-You can also see the Deployment that was created:
-
-```shell
-kubectl get deployments
-```
-
-To stop the two replicated containers, delete the Deployment:
-
-```shell
-kubectl delete deployment my-nginx
-```
-
-### Exposing your pods to the internet.
-
-On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](/docs/user-guide/services/#external-services) for the pods,
-to do this run:
-
-```shell
-kubectl expose deployment my-nginx --port=80 --type=LoadBalancer
-```
-
-This should print the service that has been created, and map an external IP address to the service. Where to find this external IP address will depend on the environment you run in.  For instance, for Google Compute Engine the external IP address is listed as part of the newly created service and can be retrieved by running
-
-```shell
-kubectl get services
-```
-
-In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a firewall to allow traffic on port 80.
-
-### Next: Configuration files
-
-Most people will eventually want to use declarative configuration files for creating/modifying their applications.  A [simplified introduction](/docs/user-guide/deploying-applications/)
-is given in a different document.

From 9797dee77c9b37868dc4885a0b5522b7ede3ce27 Mon Sep 17 00:00:00 2001
From: Jared 
Date: Wed, 18 Jan 2017 16:38:37 -0800
Subject: [PATCH 31/44] Fixed dead link

Fixed dead link to drivers
---
 docs/getting-started-guides/minikube.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md
index 7e47aeadd6..d033f3c48e 100644
--- a/docs/getting-started-guides/minikube.md
+++ b/docs/getting-started-guides/minikube.md
@@ -57,8 +57,8 @@ the following drivers:
 
 * virtualbox
 * vmwarefusion
-* kvm ([driver installation](./DRIVERS.md#kvm-driver))
-* xhyve ([driver installation](./DRIVERS.md#xhyve-driver))
+* kvm ([driver installation](https://github.com/kubernetes/minikube/blob/master/DRIVERS.md#kvm-driver))
+* xhyve ([driver installation](https://github.com/kubernetes/minikube/blob/master/DRIVERS.md#xhyve-driver))
 
 Note that the IP below is dynamic and can change. It can be retrieved with `minikube ip`.
 

From 0f6b9927719322bc20c55132d9b2bd163780d37f Mon Sep 17 00:00:00 2001
From: Jared 
Date: Wed, 18 Jan 2017 16:50:49 -0800
Subject: [PATCH 32/44] fixed all relative links

Addresses issue: https://github.com/kubernetes/kubernetes.github.io/issues/1944
---
 docs/getting-started-guides/minikube.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md
index d033f3c48e..a6fc28bfb0 100644
--- a/docs/getting-started-guides/minikube.md
+++ b/docs/getting-started-guides/minikube.md
@@ -27,7 +27,7 @@ Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a
 ### Requirements
 
 * OS X
-    * [xhyve driver](./DRIVERS.md#xhyve-driver), [VirtualBox](https://www.virtualbox.org/wiki/Downloads) or [VMware Fusion](https://www.vmware.com/products/fusion) installation
+    * [xhyve driver](https://github.com/kubernetes/minikube/blob/master/DRIVERS.md#xhyve-driver), [VirtualBox](https://www.virtualbox.org/wiki/Downloads) or [VMware Fusion](https://www.vmware.com/products/fusion) installation
 * Linux
     * [VirtualBox](https://www.virtualbox.org/wiki/Downloads) or [KVM](http://www.linux-kvm.org/) installation,
 * VT-x/AMD-v virtualization must be enabled in BIOS
@@ -111,7 +111,7 @@ This will use an alternative minikube ISO image containing both rkt, and Docker,
 
 ### Driver plugins
 
-See [DRIVERS](./DRIVERS.md) for details on supported drivers and how to install
+See [DRIVERS](https://github.com/kubernetes/minikube/blob/master/DRIVERS.md) for details on supported drivers and how to install
 plugins, if required.
 
 ### Reusing the Docker daemon
@@ -150,7 +150,7 @@ Remember to turn off the imagePullPolicy:Always, as otherwise Kubernetes won't u
 
 ### Starting a Cluster
 
-The [minikube start](./docs/minikube_start.md) command can be used to start your cluster.
+The [minikube start](https://github.com/kubernetes/minikube/blob/master/docs/minikube_start.md) command can be used to start your cluster.
 This command creates and configures a virtual machine that runs a single-node Kubernetes cluster.
 This command also configures your [kubectl](http://kubernetes.io/docs/user-guide/kubectl-overview/) installation to communicate with this cluster.
 
@@ -194,12 +194,12 @@ This feature also supports nested structs. To change the `LeaderElection.LeaderE
 To set the `AuthorizationMode` on the `apiserver` to `RBAC`, you can use: `--extra-config=apiserver.AuthorizationMode=RBAC`. 
 
 ### Stopping a Cluster
-The [minikube stop](./docs/minikube_stop.md) command can be used to stop your cluster.
+The [minikube stop](https://github.com/kubernetes/minikube/blob/master/docs/minikube_stop.md) command can be used to stop your cluster.
 This command shuts down the minikube virtual machine, but preserves all cluster state and data.
 Starting the cluster again will restore it to it's previous state.
 
 ### Deleting a Cluster
-The [minikube delete](./docs/minikube_delete.md) command can be used to delete your cluster.
+The [minikube delete](https://github.com/kubernetes/minikube/blob/master/docs/minikube_delete.md) command can be used to delete your cluster.
 This command shuts down and deletes the minikube virtual machine. No data or state is preserved.
 
 ## Interacting With your Cluster
@@ -288,7 +288,7 @@ In order to have minikube properly start/restart custom addons, place the addon(
 
 ## Documentation
 
-For a list of minikube's available commands see the [full CLI docs](./docs/minikube.md).
+For a list of minikube's available commands see the [full CLI docs](https://github.com/kubernetes/minikube/blob/master/docs/minikube.md).
 
 ## Using Minikube with an HTTP Proxy
 

From 02d17ade5fd1205151d0c01e1c40e0e156388892 Mon Sep 17 00:00:00 2001
From: steveperry-53 
Date: Wed, 18 Jan 2017 10:18:37 -0800
Subject: [PATCH 33/44] Reduce heading levels by 1.

---
 _includes/templates/concept.md                |  2 +-
 _includes/templates/task.md                   |  4 +--
 _includes/templates/tutorial.md               |  8 ++---
 .../abstractions/controllers/statefulsets.md  | 16 +++++-----
 docs/concepts/abstractions/overview.md        | 10 +++----
 docs/concepts/abstractions/pod.md             | 14 ++++-----
 docs/concepts/object-metadata/annotations.md  |  2 +-
 ...load-balance-access-application-cluster.md | 13 ++------
 ...port-forward-access-application-cluster.md |  6 ++--
 .../http-proxy-access-api.md                  |  4 +--
 .../administer-cluster/assign-pods-nodes.md   |  4 +--
 .../change-pv-reclaim-policy.md               |  6 ++--
 .../dns-horizontal-autoscaling.md             | 22 +++++++-------
 .../administer-cluster/safely-drain-node.md   |  4 +--
 .../assign-cpu-ram-container.md               |  6 ++--
 .../attach-handler-lifecycle-event.md         |  6 ++--
 .../communicate-containers-same-pod.md        |  4 +--
 .../configure-liveness-readiness-probes.md    | 12 ++++----
 .../configure-pod-initialization.md           |  2 +-
 .../configure-volume-storage.md               |  2 +-
 .../define-command-argument-container.md      |  6 ++--
 .../define-environment-variable-container.md  |  2 +-
 .../distribute-credentials-secure.md          | 10 +++----
 .../pull-image-private-registry.md            |  8 ++---
 .../determine-reason-pod-failure.md           |  4 +--
 .../debugging-a-statefulset.md                |  4 +--
 docs/tasks/manage-stateful-set/delete-pods.md |  6 ++--
 .../deleting-a-statefulset.md                 |  8 ++---
 .../manage-stateful-set/scale-stateful-set.md | 10 +++----
 .../upgrade-pet-set-to-stateful-set.md        | 18 +++++------
 .../troubleshoot/debug-init-containers.md     |  8 ++---
 docs/tutorials/services/source-ip.md          | 10 +++----
 .../basic-stateful-set.md                     | 28 ++++++++---------
 .../run-replicated-stateful-application.md    | 28 ++++++++---------
 .../run-stateful-application.md               | 10 +++----
 .../stateful-application/zookeeper.md         | 30 +++++++++----------
 .../expose-external-ip-address-service.md     |  4 +--
 .../expose-external-ip-address.md             |  2 +-
 .../stateless-application/hello-minikube.md   | 14 ++++-----
 .../run-stateless-application-deployment.md   |  8 ++---
 40 files changed, 178 insertions(+), 187 deletions(-)

diff --git a/_includes/templates/concept.md b/_includes/templates/concept.md
index dc6efdad13..65edc7f808 100644
--- a/_includes/templates/concept.md
+++ b/_includes/templates/concept.md
@@ -24,7 +24,7 @@
 
 {% if whatsnext %}
 
-### What's next
+## What's next
 
 {{ whatsnext }}
 
diff --git a/_includes/templates/task.md b/_includes/templates/task.md
index d74ff3b97a..e76cb7b117 100644
--- a/_includes/templates/task.md
+++ b/_includes/templates/task.md
@@ -15,7 +15,7 @@
 
 {% if prerequisites %}
 
-### Before you begin
+## Before you begin
 
 {{ prerequisites }}
 
@@ -48,7 +48,7 @@
 
 {% if whatsnext %}
 
-### What's next
+## What's next
 
 {{ whatsnext }}
 
diff --git a/_includes/templates/tutorial.md b/_includes/templates/tutorial.md
index 9c2d680643..b4c1faa0f1 100644
--- a/_includes/templates/tutorial.md
+++ b/_includes/templates/tutorial.md
@@ -15,7 +15,7 @@
 
 {% if objectives %}
 
-### Objectives
+## Objectives
 
 {{ objectives }}
 
@@ -28,7 +28,7 @@
 
 {% if prerequisites %}
 
-### Before you begin
+## Before you begin
 
 {{ prerequisites }}
 
@@ -52,7 +52,7 @@
 
 {% if cleanup %}
 
-### Cleaning up
+## Cleaning up
 
 {{ cleanup }}
 
@@ -61,7 +61,7 @@
 
 {% if whatsnext %}
 
-### What's next
+## What's next
 
 {{ whatsnext }}
 
diff --git a/docs/concepts/abstractions/controllers/statefulsets.md b/docs/concepts/abstractions/controllers/statefulsets.md
index 996a63fe8d..fb48e63ae0 100644
--- a/docs/concepts/abstractions/controllers/statefulsets.md
+++ b/docs/concepts/abstractions/controllers/statefulsets.md
@@ -22,7 +22,7 @@ guarantees about the ordering of deployment and scaling.
 
 {% capture body %}
 
-### Using StatefulSets
+## Using StatefulSets
 
 StatefulSets are valuable for applications that require one or more of the 
 following.
@@ -39,7 +39,7 @@ provides a set of stateless replicas. Controllers such as
 [Deployment](/docs/user-guide/deployments/) or 
 [ReplicaSet](/docs/user-guide/replicasets/) may be better suited to your stateless needs.
 
-### Limitations
+## Limitations
 * StatefulSet is a beta resource, not available in any Kubernetes release prior to 1.5.
 * As with all alpha/beta resources, you can disable StatefulSet through the `--runtime-config` option passed to the apiserver.
 * The storage for a given Pod must either be provisioned by a [PersistentVolume Provisioner](http://releases.k8s.io/{{page.githubbranch}}/examples/experimental/persistent-volume-provisioning/README.md) based on the requested `storage class`, or pre-provisioned by an admin.
@@ -47,7 +47,7 @@ provides a set of stateless replicas. Controllers such as
 * StatefulSets currently require a [Headless Service](/docs/user-guide/services/#headless-services) to be responsible for the network identity of the Pods. You are responsible for creating this Service.
 * Updating an existing StatefulSet is currently a manual process.
 
-### Components
+## Components
 The example below demonstrates the components of a StatefulSet. 
 
 * A Headless Service, named nginx, is used to control the network domain. 
@@ -103,17 +103,17 @@ spec:
           storage: 1Gi
 ```
 
-### Pod Identity
+## Pod Identity
 StatefulSet Pods have a unique identity that is comprised of an ordinal, a 
 stable network identity, and stable storage. The identity sticks to the Pod, 
 regardless of which node it's (re)scheduled on.
 
-__Ordinal Index__
+### Ordinal Index
 
 For a StatefulSet with N replicas, each Pod in the StatefulSet will be 
 assigned an integer ordinal, in the range [0,N), that is unique over the Set. 
 
-__Stable Network ID__
+### Stable Network ID
 
 Each Pod in a StatefulSet derives its hostname from the name of the StatefulSet 
 and the ordinal of the Pod. The pattern for the constructed hostname 
@@ -139,7 +139,7 @@ Cluster Domain | Service (ns/name) | StatefulSet (ns/name)  | StatefulSet Domain
 Note that Cluster Domain will be set to `cluster.local` unless 
 [otherwise configured](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md#how-do-i-configure-it).
 
-__Stable Storage__
+### Stable Storage
 
 Kubernetes creates one [PersistentVolume](/docs/user-guide/volumes/) for each 
 VolumeClaimTemplate. In the nginx example above, each Pod will receive a single PersistentVolume 
@@ -149,7 +149,7 @@ PersistentVolume Claims. Note that, the PersistentVolumes associated with the
 Pods' PersistentVolume Claims are not deleted when the Pods, or StatefulSet are deleted. 
 This must be done manually.
 
-### Deployment and Scaling Guarantee
+## Deployment and Scaling Guarantee
 
 * For a StatefulSet with N replicas, when Pods are being deployed, they are created sequentially, in order from {0..N-1}. 
 * When Pods are being deleted, they are terminated in reverse order, from {N-1..0}.
diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index ffed154293..dc2e8cf7ab 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -7,7 +7,7 @@ This page explains how Kubernetes objects are represented in the Kubernetes API,
 {% endcapture %}
 
 {% capture body %}
-### Understanding Kubernetes Objects
+## Understanding Kubernetes Objects
 
 *Kubernetes Objects* are persistent entities in the Kubernetes system. Kubenetes uses these entities to represent the state of your cluster. Specifically, they can describe:
 
@@ -19,7 +19,7 @@ A Kubernetes object is a "record of intent"--once you create the object, the Kub
 
 To work with Kubernetes objects--whether to create, modify, or delete them--you'll need to use the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md). When you use the `kubectl` comamnd-line interface, for example, the CLI makes the necessary Kubernetes API calls for you; you can also use the Kubernetes API directly in your own programs. Kubernetes currently provides a `golang` [client library](https://github.com/kubernetes/client-go) for this purpose, and other language libraries (such as [Python](https://github.com/kubernetes-incubator/client-python)) are being developed.
 
-#### Object Spec and Status
+### Object Spec and Status
 
 Every Kubernetes object includes two nested object fields that govern the object's configuration: the object *spec* and the object *status*. The *spec*, which you must provide, describes your *desired state* for the object--the characteristics that you want the object to have. The *status* describes the *actual state* for the object, and is supplied and updated by the Kubernetes system. At any given time, the Kubernetes Control Plane actively manages an object's actual state to match the desired state you supplied.
 
@@ -27,7 +27,7 @@ For example, a Kubernetes Deployment is an object that can represent an applicat
 
 For more information on the object spec, status, and metadata, see the [Kubernetes API Conventions](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md#spec-and-status).
 
-#### Describing a Kubernetes Object
+### Describing a Kubernetes Object
 
 When you create an object in Kubernetes, you must provide the object spec that describes its desired state, as well as some basic information about the object (such as a name). When you use the Kubernetes API to create the object (either directly or via `kubectl`), that API request must include that information as JSON in the request body. **Most often, you provide the information to `kubectl` in a .yaml file.** `kubectl` converts the information to JSON when making the API request.
 
@@ -47,7 +47,7 @@ The output is similar to this:
 deployment "nginx-deployment" created
 ```
 
-#### Required Fields
+### Required Fields
 
 In the `.yaml` file for the Kubernetes object you want to create, you'll need to set values for the following fields:
 
@@ -63,4 +63,4 @@ You'll also need to provide the object `spec` field. The precise format of the o
 * Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/abstractions/pod/).
 {% endcapture %}
 
-{% include templates/concept.md %}
\ No newline at end of file
+{% include templates/concept.md %}
diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index 82d6407a8e..33637168db 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -9,7 +9,7 @@ This page provides an overview of `Pod`, the smallest deployable object in the K
 {:toc}
 
 {% capture body %}
-### Understanding Pods
+## Understanding Pods
 
 A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.
 
@@ -29,7 +29,7 @@ The [Kubernetes Blog](http://blog.kubernetes.io) has some additional information
 
 Each Pod is meant to run a single instance of a given application. If you want to scale your application horizontally (e.g., run muliple instances), you should use multiple Pods, one for each instance. In Kubernetes, this is generally referred to as _replication_. Replicated Pods are usually created and managed as a group by an abstraction called a Controller. See [Pods and Controllers](#pods-and-controllers) for more information.
 
-#### How Pods Manage Multiple Containers
+### How Pods Manage Multiple Containers
 
 Pods are designed to support multiple cooperating processes (as containers) that form a cohesive unit of service. The containers in a Pod are automatically co-located and co-scheduled on the same phyiscal or virtual machine in the cluster. The containers can share resources and dependencies, communicate with one another, and coordinate when and how they are terminated.
 
@@ -39,15 +39,15 @@ Note that grouping multiple co-located and co-managed containers in a single Pod
 
 Pods provide two kinds of shared resources for their constituent containers: *networking* and *storage*.
 
-##### Networking
+#### Networking
 
 Each Pod is assigned a unique IP address. Every the container in a Pod shares the network namespace, including the IP address and network ports. Containers *inside a Pod* can communicate with one another using `localhost`. When containers in a Pod communicate with entities *outside the Pod*, they must coordinate how they use the shared network resources (such as ports).
 
-##### Storage
+#### Storage
 
 A Pod can specify a set of shared storage *volumes*. All containers in the Pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a Pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.
 
-### Working with Pods
+## Working with Pods
 
 You'll rarely create individual Pods directly in Kubernetes--even singleton Pods. This is because Pods are designed as relatively ephemeral, disposable entities. When a Pod gets created (directly by you, or indirectly by a Controller), it is scheduled to run on a Node in your your cluster. The Pod remains on that Node until the process is terminated, the pod object is deleted, or the pod is *evicted* for lack of resources, or the Node fails.
 
@@ -55,7 +55,7 @@ You'll rarely create individual Pods directly in Kubernetes--even singleton Pods
 
 Pods do not, by themselves, self-heal. If a Pod is scheduled to a Node that fails, or if the scheduling operation itself fails, the Pod is deleted; likewise, a Pod won't survive an eviction due to a lack of resources or Node maintenance. Kubernetes uses a higher-level abstraction, called a *Controller*, that handles the work of managing the relatively disposable Pod instances. Thus, while it is possible to use Pod directly, it's far more common in Kubernetes to manage your pods using a Controller. See [Pods and Controllers](#pods-and-controllers) for more information on how Kubernetes uses Controllers to implement Pod scaling and healing.
 
-#### Pods and Controllers
+### Pods and Controllers
 
 A Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope. For example, if a Node fails, the Controller might automatically replace the Pod by scheduling an identical replacement on a different Node). 
 
@@ -75,4 +75,4 @@ In general, Controllers use a Pod Template that you provide to create the Pods f
   * Other Pod Topics
 {% endcapture %}
 
-{% include templates/concept.md %}
\ No newline at end of file
+{% include templates/concept.md %}
diff --git a/docs/concepts/object-metadata/annotations.md b/docs/concepts/object-metadata/annotations.md
index fbf73f48fd..00840db613 100644
--- a/docs/concepts/object-metadata/annotations.md
+++ b/docs/concepts/object-metadata/annotations.md
@@ -8,7 +8,7 @@ to objects. Clients such as tools and libraries can retrieve this metadata.
 {% endcapture %}
 
 {% capture body %}
-### Attaching metadata to objects
+## Attaching metadata to objects
 
 You can use either labels or annotations to attach metadata to Kubernetes
 objects. Labels can be used to select objects and to find
diff --git a/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md b/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md
index c42d97e3e9..f6cb1251fe 100644
--- a/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md
+++ b/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md
@@ -28,7 +28,7 @@ load-balanced access to an application running in a cluster.
 
 {% capture lessoncontent %}
 
-### Creating a Service for an application running in two pods
+## Creating a Service for an application running in two pods
 
 1. Run a Hello World application in your cluster:
 
@@ -98,7 +98,7 @@ load-balanced access to an application running in a cluster.
     where `` us the IP address of your Minikube node,
     and `` is the NodePort value for your service.
 
-### Using a service configuration file
+## Using a service configuration file
 
 As an alternative to using `kubectl expose`, you can use a
 [service configuration file](/docs/user-guide/services/operations)
@@ -108,15 +108,6 @@ to create a Service.
 {% endcapture %}
 
 
-{% capture cleanup %}
-
-If you want to stop the Hello World application, enter these commands:
-
-    TODO
-
-{% endcapture %}
-
-
 {% capture whatsnext %}
 
 Learn more about
diff --git a/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md b/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
index 4b0acb8f88..f3fe10161e 100644
--- a/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
+++ b/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
@@ -22,7 +22,7 @@ for database debugging.
 
 {% capture steps %}
 
-### Creating a pod to run a Redis server
+## Creating a pod to run a Redis server
 
 1. Create a pod:
 
@@ -51,7 +51,7 @@ for database debugging.
 
         6379
 
-### Forward a local port to a port on the pod
+## Forward a local port to a port on the pod
 
 1. Forward port 6379 on the local workstation to port 6379 of redis-master pod:
 
@@ -77,7 +77,7 @@ for database debugging.
 
 {% capture discussion %}
 
-### Discussion
+## Discussion
 
 Connections made to local port 6379 are forwarded to port 6379 of the pod that
 is running the Redis server. With this connection in place you can use your
diff --git a/docs/tasks/access-kubernetes-api/http-proxy-access-api.md b/docs/tasks/access-kubernetes-api/http-proxy-access-api.md
index 9dee7c9c4d..92baf97aa9 100644
--- a/docs/tasks/access-kubernetes-api/http-proxy-access-api.md
+++ b/docs/tasks/access-kubernetes-api/http-proxy-access-api.md
@@ -19,13 +19,13 @@ This page shows how to use an HTTP proxy to access the Kubernetes API.
 
 {% capture steps %}
 
-### Using kubectl to start a proxy server
+## Using kubectl to start a proxy server
 
 This command starts a proxy to the Kubernetes API server:
 
     kubectl proxy --port=8080
 
-### Exploring the Kubernetes API
+## Exploring the Kubernetes API
 
 When the proxy server is running, you can explore the API using `curl`, `wget`,
 or a browser.
diff --git a/docs/tasks/administer-cluster/assign-pods-nodes.md b/docs/tasks/administer-cluster/assign-pods-nodes.md
index 03dc0c021c..43db077f76 100644
--- a/docs/tasks/administer-cluster/assign-pods-nodes.md
+++ b/docs/tasks/administer-cluster/assign-pods-nodes.md
@@ -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
diff --git a/docs/tasks/administer-cluster/change-pv-reclaim-policy.md b/docs/tasks/administer-cluster/change-pv-reclaim-policy.md
index 0e70c0c709..08a18f8f08 100644
--- a/docs/tasks/administer-cluster/change-pv-reclaim-policy.md
+++ b/docs/tasks/administer-cluster/change-pv-reclaim-policy.md
@@ -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)
diff --git a/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md b/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md
index fa8202865d..069409058a 100644
--- a/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md
+++ b/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md
@@ -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  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.
diff --git a/docs/tasks/administer-cluster/safely-drain-node.md b/docs/tasks/administer-cluster/safely-drain-node.md
index 902d9b1db3..d69bcb2363 100644
--- a/docs/tasks/administer-cluster/safely-drain-node.md
+++ b/docs/tasks/administer-cluster/safely-drain-node.md
@@ -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 
 ```
 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
diff --git a/docs/tasks/configure-pod-container/assign-cpu-ram-container.md b/docs/tasks/configure-pod-container/assign-cpu-ram-container.md
index 8722499c34..24cca3eca5 100644
--- a/docs/tasks/configure-pod-container/assign-cpu-ram-container.md
+++ b/docs/tasks/configure-pod-container/assign-cpu-ram-container.md
@@ -19,7 +19,7 @@ in a Kubernetes Pod.
 
 {% capture steps %}
 
-### Assigning CPU and RAM resources to a container
+## Assigning CPU and RAM resources to a container
 
 When you create a Pod, you can request CPU and RAM resources for the containers
 that run in the Pod. You can also set limits for CPU and RAM resources. To
@@ -64,7 +64,7 @@ for the `Pod`:
               cpu:    250m
               memory:   64Mi
 
-### Understanding CPU and RAM units
+## Understanding CPU and RAM units
 
 The CPU resource is measured in *cpu*s. Fractional values are allowed. You can
 use the suffix *m* to mean mili. For example 100m cpu is 100 milicpu, and is
@@ -89,7 +89,7 @@ If you specify a request, a Pod is guaranteed to be able to use that much
 of the resource. See
 [Resource QoS](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/resource-qos.md) for the difference between resource limits and requests.
 
-### If you don't specify limits or requests
+## If you don't specify limits or requests
 
 If you don't specify a RAM limit, Kubernetes places no upper bound on the
 amount of RAM a Container can use. A Container could use all the RAM
diff --git a/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md b/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
index 715ea3effb..a46f910714 100644
--- a/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
+++ b/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
@@ -21,7 +21,7 @@ Container is terminated.
 
 {% capture steps %}
 
-### Defining postStart and preStop handlers
+## Defining postStart and preStop handlers
 
 In this exercise, you create a Pod that has one Container. The Container has handlers
 for the postStart and preStop events.
@@ -60,7 +60,7 @@ The output shows the text written by the postStart handler:
 
 {% capture discussion %}
 
-### Discussion
+## Discussion
 
 Kubernetes sends the postStart event immediately after the Container is created.
 There is no guarantee, however, that the postStart handler is called before
@@ -83,7 +83,7 @@ unless the Pod's grace period expires. For more details, see
 * Learn more about the [lifecycle of a Pod](https://kubernetes.io/docs/user-guide/pod-states/).
 
 
-#### Reference
+### Reference
  
 * [Lifecycle](https://kubernetes.io/docs/resources-reference/1_5/#lifecycle-v1)
 * [Container](https://kubernetes.io/docs/resources-reference/1_5/#container-v1)
diff --git a/docs/tasks/configure-pod-container/communicate-containers-same-pod.md b/docs/tasks/configure-pod-container/communicate-containers-same-pod.md
index 0f934dc085..815ee8dc19 100644
--- a/docs/tasks/configure-pod-container/communicate-containers-same-pod.md
+++ b/docs/tasks/configure-pod-container/communicate-containers-same-pod.md
@@ -19,7 +19,7 @@ in the same Pod.
 
 {% capture steps %}
 
-###  Creating a Pod that runs two Containers
+##  Creating a Pod that runs two Containers
 
 In this exercise, you create a Pod that runs two Containers. The two containers
 share a Volume that they can use to communicate. Here is the configuration file
@@ -111,7 +111,7 @@ The output shows that nginx serves a web page written by the debian container:
 
 {% capture discussion %}
 
-### Discussion
+## Discussion
 
 The primary reason that Pods can have multiple containers is to support
 helper applications that assist a primary application. Typical examples of
diff --git a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
index 3b7f7462ef..8c877ac16c 100644
--- a/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
+++ b/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
@@ -30,7 +30,7 @@ When a Pod is not ready, it is removed from Service load balancers.
 
 {% capture steps %}
 
-### Defining a liveness command
+## Defining a liveness command
 
 Many applications running for long periods of time eventually transition to
 broken states, and cannot recover except by being restarted. Kubernetes provides
@@ -117,7 +117,7 @@ NAME            READY     STATUS    RESTARTS   AGE
 liveness-exec   1/1       Running   1          1m
 ```
 
-### Defining a liveness HTTP request
+## Defining a liveness HTTP request
 
 Another kind of liveness probe uses an HTTP GET request. Here is the configuration
 file for a Pod that runs a container based on the `gcr.io/google_containers/liveness`
@@ -173,7 +173,7 @@ the Container has been restarted:
 kubectl describe pod liveness-http
 ```
 
-### Using a named port
+## Using a named port
 
 You can use a named
 [ContainerPort](/docs/api-reference/v1/definitions/#_v1_containerport)
@@ -191,7 +191,7 @@ livenessProbe:
   port: liveness-port
 ```
 
-### Defining readiness probes
+## Defining readiness probes
 
 Sometimes, applications are temporarily unable to serve traffic.
 For example, an application might need to load large data or configuration
@@ -219,7 +219,7 @@ readinessProbe:
 
 {% capture discussion %}
 
-### Discussion
+## Discussion
 
 {% comment %}
 Eventually, some of this Discussion section could be moved to a concept topic.
@@ -260,7 +260,7 @@ In addition to command probes and HTTP probes, Kubenetes supports
 * Learn more about
 [Health Checking section](/docs/user-guide/walkthrough/k8s201/#health-checking).
 
-#### Reference
+### Reference
 
 * [Pod](http://kubernetes.io/docs/api-reference/v1/definitions#_v1_pod)
 * [Container](/docs/api-reference/v1/definitions/#_v1_container)
diff --git a/docs/tasks/configure-pod-container/configure-pod-initialization.md b/docs/tasks/configure-pod-container/configure-pod-initialization.md
index add65b09ee..7aa2bff40a 100644
--- a/docs/tasks/configure-pod-container/configure-pod-initialization.md
+++ b/docs/tasks/configure-pod-container/configure-pod-initialization.md
@@ -16,7 +16,7 @@ application Container runs.
 
 {% capture steps %}
 
-### Creating a Pod that has an init Container
+## Creating a Pod that has an init Container
 
 In this exercise you create a Pod that has one application Container and one
 init Container. The init Container runs to completion before the application
diff --git a/docs/tasks/configure-pod-container/configure-volume-storage.md b/docs/tasks/configure-pod-container/configure-volume-storage.md
index 6919a91fb0..92756615a8 100644
--- a/docs/tasks/configure-pod-container/configure-volume-storage.md
+++ b/docs/tasks/configure-pod-container/configure-volume-storage.md
@@ -23,7 +23,7 @@ key-value cache and store.
 
 {% capture steps %}
 
-### Configuring a volume for a Pod
+## Configuring a volume for a Pod
 
 In this exercise, you create a Pod that runs one Container. This Pod has a
 Volume of type
diff --git a/docs/tasks/configure-pod-container/define-command-argument-container.md b/docs/tasks/configure-pod-container/define-command-argument-container.md
index 4fd988744d..df4350aa1a 100644
--- a/docs/tasks/configure-pod-container/define-command-argument-container.md
+++ b/docs/tasks/configure-pod-container/define-command-argument-container.md
@@ -19,7 +19,7 @@ in a Kubernetes Pod.
 
 {% capture steps %}
 
-### Defining a command and arguments when you create a Pod
+## Defining a command and arguments when you create a Pod
 
 When you create a Pod, you can define a command and arguments for the
 containers that run in the Pod. To define a command, include the `command`
@@ -60,7 +60,7 @@ from the Pod:
         command-demo
         tcp://10.3.240.1:443
 
-### Using environment variables to define arguments
+## Using environment variables to define arguments
 
 In the preceding example, you defined the arguments directly by
 providing strings. As an alternative to providing strings directly,
@@ -81,7 +81,7 @@ and
 NOTE: The environment variable appears in parentheses, `"$(VAR)"`. This is
 required for the variable to be expanded in the `command` or `args` field.
 
-### Running a command in a shell
+## Running a command in a shell
 
 In some cases, you need your command to run in a shell. For example, your
 command might consist of several commands piped together, or it might be a shell
diff --git a/docs/tasks/configure-pod-container/define-environment-variable-container.md b/docs/tasks/configure-pod-container/define-environment-variable-container.md
index f24f1bcc8a..7faba40522 100644
--- a/docs/tasks/configure-pod-container/define-environment-variable-container.md
+++ b/docs/tasks/configure-pod-container/define-environment-variable-container.md
@@ -19,7 +19,7 @@ in a Kubernetes Pod.
 
 {% capture steps %}
 
-### Defining an environment variable for a container
+## Defining an environment variable for a container
 
 When you create a Pod, you can set environment variables for the containers
 that run in the Pod. To set environment variables, include the `env` field in
diff --git a/docs/tasks/configure-pod-container/distribute-credentials-secure.md b/docs/tasks/configure-pod-container/distribute-credentials-secure.md
index 48272a7cba..69d5d37890 100644
--- a/docs/tasks/configure-pod-container/distribute-credentials-secure.md
+++ b/docs/tasks/configure-pod-container/distribute-credentials-secure.md
@@ -15,7 +15,7 @@ encryption keys, into Pods.
 
 {% capture steps %}
 
-### Converting your secret data to a base-64 representation
+## Converting your secret data to a base-64 representation
 
 Suppose you want to have two pieces of secret data: a username `my-app` and a password
 `39528$vdg7Jb`. First, use [Base64 encoding](https://www.base64encode.org/) to
@@ -28,7 +28,7 @@ example:
 The output shows that the base-64 representation of your username is `bXktYXBwCg==`,
 and the base-64 representation of your password is `Mzk1MjgkdmRnN0piCg==`.
 
-### Creating a Secret
+## Creating a Secret
 
 Here is a configuration file you can use to create a Secret that holds your
 username and password:
@@ -72,7 +72,7 @@ username and password:
         password:   13 bytes
         username:   7 bytes
 
-### Creating a Pod that has access to the secret data through a Volume
+## Creating a Pod that has access to the secret data through a Volume
 
 Here is a configuration file you can use to create a Pod:
 
@@ -119,7 +119,7 @@ is exposed:
         my-app
         39528$vdg7Jb
 
-### Creating a Pod that has access to the secret data through environment variables
+## Creating a Pod that has access to the secret data through environment variables
 
 Here is a configuration file you can use to create a Pod:
 
@@ -160,7 +160,7 @@ Here is a configuration file you can use to create a Pod:
 * Learn more about [Secrets](/docs/user-guide/secrets/).
 * Learn about [Volumes](/docs/user-guide/volumes/).
 
-#### Reference
+### Reference
 
 * [Secret](docs/api-reference/v1/definitions/#_v1_secret)
 * [Volume](docs/api-reference/v1/definitions/#_v1_volume)
diff --git a/docs/tasks/configure-pod-container/pull-image-private-registry.md b/docs/tasks/configure-pod-container/pull-image-private-registry.md
index 5560dd9a30..e9b640873a 100644
--- a/docs/tasks/configure-pod-container/pull-image-private-registry.md
+++ b/docs/tasks/configure-pod-container/pull-image-private-registry.md
@@ -20,7 +20,7 @@ private Docker registry or repository.
 
 {% capture steps %}
 
-### Logging in to Docker
+## Logging in to Docker
 
     docker login
 
@@ -43,7 +43,7 @@ The output contains a section similar to this:
         }
     }
 
-### Creating a Secret that holds your authorization token
+## Creating a Secret that holds your authorization token
 
 Create a Secret named `regsecret`:
 
@@ -55,7 +55,7 @@ where:
 * `` is your Docker password.
 * `` is your Docker email.
 
-### Understanding your Secret
+## Understanding your Secret
 
 To understand what's in the Secret you just created, start by viewing the
 Secret in YAML format:
@@ -92,7 +92,7 @@ The output is similar to this:
 Notice that the secret data contains the authorization token from your
 `config.json` file.
 
-### Creating a Pod that uses your Secret
+## Creating a Pod that uses your Secret
 
 Here is a configuration file for a Pod that needs access to your secret data:
 
diff --git a/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md b/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
index 3f1c5fbc89..3a0e79898a 100644
--- a/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
+++ b/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
@@ -27,7 +27,7 @@ the general
 
 {% capture steps %}
 
-### Writing and reading a termination message
+## Writing and reading a termination message
 
 In this exercise, you create a Pod that runs one container.
 The configuration file specifies a command that runs when
@@ -75,7 +75,7 @@ only the termination message:
 {% raw %}    kubectl get pod termination-demo -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"{% endraw %}
 ```
 
-### Setting the termination log file
+## Setting the termination log file
 
 By default Kubernetes retrieves termination messages from
 `/dev/termination-log`. To change this to a different file,
diff --git a/docs/tasks/manage-stateful-set/debugging-a-statefulset.md b/docs/tasks/manage-stateful-set/debugging-a-statefulset.md
index 2266d7a323..f66a8a1c53 100644
--- a/docs/tasks/manage-stateful-set/debugging-a-statefulset.md
+++ b/docs/tasks/manage-stateful-set/debugging-a-statefulset.md
@@ -26,7 +26,7 @@ This task shows you how to debug a StatefulSet.
 
 {% capture steps %}
 
-### Debugging a StatefulSet
+## Debugging a StatefulSet
 
 In order to list all the pods which belong to a StatefulSet, which have a label `app=myapp` set on them, you can use the following: 
 
@@ -44,7 +44,7 @@ kubectl annotate pods  pod.alpha.kubernetes.io/initialized="false" --o
 
 When the annotation is set to `"false"`, the StatefulSet will not respond to its Pods becoming unhealthy or unavailable. It will not create replacement Pods till the annotation is removed or set to `"true"` on each StatefulSet Pod. 
 
-#### Step-wise Initialization
+### Step-wise Initialization
 
 You can also use the same annotation to debug race conditions during bootstrapping of the StatefulSet by setting the `pod.alpha.kubernetes.io/initialized` annotation to `"false"` in the `.spec.template.metadata.annotations` field of the StatefulSet prior to creating it. 
 
diff --git a/docs/tasks/manage-stateful-set/delete-pods.md b/docs/tasks/manage-stateful-set/delete-pods.md
index 4b31def936..d1b66ce881 100644
--- a/docs/tasks/manage-stateful-set/delete-pods.md
+++ b/docs/tasks/manage-stateful-set/delete-pods.md
@@ -21,13 +21,13 @@ This page shows how to delete Pods which are part of a stateful set, and explain
 {% capture steps %}
 
 
-### StatefulSet considerations
+## StatefulSet considerations
 
 In normal operation of a StatefulSet, there is **never** a need to force delete a StatefulSet Pod. The StatefulSet controller is responsible for creating, scaling and deleting members of the StatefulSet. It tries to ensure that the specified number of Pods from ordinal 0 through N-1 are alive and ready. StatefulSet ensures that, at any time, there is at most one Pod with a given identity running in a cluster. This is referred to as *at most one* semantics provided by a StatefulSet.
 
 Manual force deletion should be undertaken with caution, as it has the potential to violate the at most one semantics inherent to StatefulSet. StatefulSets may be used to run distributed and clustered applications which have a need for a stable network identity and stable storage. These applications often have configuration which relies on an ensemble of a fixed number of members with fixed identities. Having multiple members with the same identity can be disastrous and may lead to data loss (e.g. split brain scenario in quorum-based systems). 
 
-### Deleting Pods
+## Deleting Pods
 
 You can perform a graceful pod deletion with the following command:
 
@@ -46,7 +46,7 @@ The recommended best practice is to use the first or second approach. If a Node
 
 Normally, the system completes the deletion once the Pod is no longer running on a Node, or the Node is deleted by an administrator. You may override this by force deleting the Pod.
 
-#### Force Deletion
+### Force Deletion
 
 Force deletions **do not** wait for confirmation from the kubelet that the Pod has been terminated. Irrespective of whether a force deletion is successful in killing a Pod, it will immediately free up the name from the apiserver. This would let the StatefulSet controller create a replacement Pod with that same identity; this can lead to the duplication of a still-running Pod, and if said Pod can still communicate with the other members of the StatefulSet, will violate the at most one semantics that StatefulSet is designed to guarantee.
 
diff --git a/docs/tasks/manage-stateful-set/deleting-a-statefulset.md b/docs/tasks/manage-stateful-set/deleting-a-statefulset.md
index 5ea82aef04..76cc87dcf0 100644
--- a/docs/tasks/manage-stateful-set/deleting-a-statefulset.md
+++ b/docs/tasks/manage-stateful-set/deleting-a-statefulset.md
@@ -22,7 +22,7 @@ This task shows you how to delete a StatefulSet.
 
 {% capture steps %}
 
-### Deleting a StatefulSet
+## Deleting a StatefulSet
 
 You can delete a StatefulSet in the same way you delete other resources in Kubernetes: use the `kubectl delete` command, and specify the StatefulSet either by file or by name.
 
@@ -52,13 +52,13 @@ By passing `--cascade=false` to `kubectl delete`, the Pods managed by the Statef
 kubectl delete pods -l app=myapp
 ```
 
-#### Persistent Volumes
+### Persistent Volumes
 
 Deleting the Pods in a StatefulSet will not delete the associated volumes. This is to ensure that you have the chance to copy data off the volume before deleting it. Deleting the PVC after the pods have left the [terminating state](/docs/user-guide/pods/index#termination-of-pods) might trigger deletion of the backing Persistent Volumes depending on the storage class and reclaim policy. You should never assume ability to access a volume after claim deletion.
 
 **Note: Use caution when deleting a PVC, as it may lead to data loss.**
 
-#### Complete deletion of a StatefulSet
+### Complete deletion of a StatefulSet
 
 To simply delete everything in a StatefulSet, including the associated pods, you can run a series of commands similar to the following:
 
@@ -72,7 +72,7 @@ kubectl delete pvc -l app=myapp
 
 In the example above, the Pods have the label `app=myapp`; substitute your own label as appropriate.
 
-#### Force deletion of StatefulSet pods
+### Force deletion of StatefulSet pods
 
 If you find that some pods in your StatefulSet are stuck in the 'Terminating' or 'Unknown' states for an extended period of time, you may need to manually intervene to forcefully delete the pods from the apiserver. This is a potentially dangerous task. Refer to [Deleting StatefulSet Pods](/docs/tasks/manage-stateful-set/delete-pods/) for details.
 
diff --git a/docs/tasks/manage-stateful-set/scale-stateful-set.md b/docs/tasks/manage-stateful-set/scale-stateful-set.md
index d00fbc055b..eda728efdd 100644
--- a/docs/tasks/manage-stateful-set/scale-stateful-set.md
+++ b/docs/tasks/manage-stateful-set/scale-stateful-set.md
@@ -25,13 +25,13 @@ This page shows how to scale a StatefulSet.
 
 {% capture steps %}
 
-### Use `kubectl` to scale StatefulSets
+## Use `kubectl` to scale StatefulSets
 
 Make sure you have `kubectl` upgraded to Kubernetes version 1.5 or later before
 continuing. If you're unsure, run `kubectl version` and check `Client Version`
 for which kubectl you're using.
 
-#### `kubectl scale`
+### `kubectl scale`
 
 First, find the StatefulSet you want to scale. Remember, you need to first understand if you can scale it or not. 
 
@@ -45,7 +45,7 @@ Change the number of replicas of your StatefulSet:
 kubectl scale statefulsets  --replicas=
 ```
 
-#### Alternative: `kubectl apply` / `kubectl edit` / `kubectl patch`
+### Alternative: `kubectl apply` / `kubectl edit` / `kubectl patch`
 
 Alternatively, you can do [in-place updates](/docs/user-guide/managing-deployments/#in-place-updates-of-resources) on your StatefulSets. 
 
@@ -68,9 +68,9 @@ Or use `kubectl patch`:
 kubectl patch statefulsets  -p '{"spec":{"replicas":}}'
 ```
 
-### Troubleshooting
+## Troubleshooting
 
-#### Scaling down doesn't not work right
+### Scaling down doesn't not work right
 
 You cannot scale down a StatefulSet when any of the stateful Pods it manages is unhealthy. Scaling down only takes place
 after those stateful Pods become running and ready. 
diff --git a/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.md b/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.md
index 592d07f833..57852bd1cc 100644
--- a/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.md
+++ b/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.md
@@ -23,7 +23,7 @@ This page shows how to upgrade from PetSets (Kubernetes version 1.3 or 1.4) to *
 
 {% capture steps %}
 
-### Differences between alpha PetSets and beta StatefulSets
+## Differences between alpha PetSets and beta StatefulSets
 
 PetSet was introduced as an alpha resource in Kubernetes release 1.3, and was renamed to StatefulSet as a beta resource in 1.5. 
 Here are some notable changes:
@@ -33,13 +33,13 @@ Here are some notable changes:
 * **Flipped debug annotation behavior**: The default value of the debug annotation (`pod.alpha.kubernetes.io/initialized`) is now `true`. The absence of this annotation will pause PetSet operations, but will NOT pause StatefulSet operations. In most cases, you no longer need this annotation in your StatefulSet manifests. 
 
 
-### Upgrading from PetSets to StatefulSets
+## Upgrading from PetSets to StatefulSets
 
 Note that these steps need to be done in the specified order. You **should
 NOT upgrade your Kubernetes master, nodes, or `kubectl` to Kubernetes version
 1.5 or later**, until told to do so.
 
-#### Find all PetSets and their manifests 
+### Find all PetSets and their manifests 
 
 First, find all existing PetSets in your cluster:
 
@@ -60,7 +60,7 @@ Here's an example command for you to save all existing PetSets as one file.
 kubectl get petsets --all-namespaces -o yaml > all-petsets.yaml
 ```
 
-#### Prepare StatefulSet manifests 
+### Prepare StatefulSet manifests 
 
 Now, for every PetSet manifest you have, prepare a corresponding StatefulSet manifest: 
 
@@ -71,7 +71,7 @@ Now, for every PetSet manifest you have, prepare a corresponding StatefulSet man
 It's recommended that you keep both PetSet manifests and StatefulSet manifests, so that you can safely roll back and recreate your PetSets, 
 if you decide not to upgrade your cluster. 
 
-#### Delete all PetSets without cascading
+### Delete all PetSets without cascading
 
 If you find existing PetSets in your cluster in the previous step, you need to delete all PetSets *without cascading*. You can do this from `kubectl` with `--cascade=false`. 
 Note that if the flag isn't set, **cascading deletion will be performed by default**, and all Pods managed by your PetSets will be gone. 
@@ -103,18 +103,18 @@ kubectl get petsets --all-namespaces
 At this moment, you've deleted all PetSets in your cluster, but not their Pods, Persistent Volumes, or Persistent Volume Claims. 
 However, since the Pods are not managed by PetSets anymore, they will be vulnerable to node failures until you finish the master upgrade and recreate StatefulSets.
 
-#### Upgrade your master to Kubernetes version 1.5 or later
+### Upgrade your master to Kubernetes version 1.5 or later
 
 Now, you can [upgrade your Kubernetes master](/docs/admin/cluster-management/#upgrading-a-cluster) to Kubernetes version 1.5 or later.
 Note that **you should NOT upgrade Nodes at this time**, because the Pods
 (that were once managed by PetSets) are now vulnerable to node failures. 
 
-#### Upgrade kubectl to Kubernetes version 1.5 or later
+### Upgrade kubectl to Kubernetes version 1.5 or later
 
 Upgrade `kubectl` to Kubernetes version 1.5 or later, following [the steps for installing and setting up 
 kubectl](/docs/user-guide/prereqs/).
 
-#### Create StatefulSets
+### Create StatefulSets
 
 Make sure you have both master and `kubectl` upgraded to Kubernetes version 1.5
 or later before continuing:
@@ -147,7 +147,7 @@ newly-upgraded cluster:
 kubectl get statefulsets --all-namespaces
 ```
 
-#### Upgrade nodes to Kubernetes version 1.5 or later (optional)
+### Upgrade nodes to Kubernetes version 1.5 or later (optional)
 
 You can now [upgrade Kubernetes nodes](/docs/admin/cluster-management/#upgrading-a-cluster)
 to Kubernetes version 1.5 or later. This step is optional, but needs to be done after all StatefulSets
diff --git a/docs/tasks/troubleshoot/debug-init-containers.md b/docs/tasks/troubleshoot/debug-init-containers.md
index 1739c03f5a..3c362c5072 100644
--- a/docs/tasks/troubleshoot/debug-init-containers.md
+++ b/docs/tasks/troubleshoot/debug-init-containers.md
@@ -30,7 +30,7 @@ Init Containers.
 
 {% capture steps %}
 
-### Checking the status of Init Containers
+## Checking the status of Init Containers
 
 The Pod status will give you an overview of Init Container execution:
 
@@ -49,7 +49,7 @@ NAME         READY     STATUS     RESTARTS   AGE
 See [Understanding Pod status](#understanding-pod-status) for more examples of
 status values and their meanings.
 
-### Getting details about Init Containers
+## Getting details about Init Containers
 
 You can see detailed information about Init Container execution by running:
 
@@ -98,7 +98,7 @@ kubectl get pod  --template '{{index .metadata.annotations "pod.beta.k
 
 This will return the same information as above, but in raw JSON format.
 
-### Accessing logs from Init Containers
+## Accessing logs from Init Containers
 
 You can access logs for an Init Container by passing its Container name along
 with the Pod name:
@@ -115,7 +115,7 @@ commands as they're executed. For example, you can do this in Bash by running
 
 {% capture discussion %}
 
-### Understanding Pod status
+## Understanding Pod status
 
 A Pod status beginning with `Init:` summarizes the status of Init Container
 execution. The table below describes some example status values that you might
diff --git a/docs/tutorials/services/source-ip.md b/docs/tutorials/services/source-ip.md
index 6efdb42870..56daa8b345 100644
--- a/docs/tutorials/services/source-ip.md
+++ b/docs/tutorials/services/source-ip.md
@@ -15,7 +15,7 @@ of Services, and how you can toggle this behavior according to your needs.
 
 {% include task-tutorial-prereqs.md %}
 
-### Terminology
+## Terminology
 
 This document makes use of the following terms:
 
@@ -26,7 +26,7 @@ This document makes use of the following terms:
 * [Kube-proxy](/docs/user-guide/services/#virtual-ips-and-service-proxies): a network daemon that orchestrates Service VIP management on every node
 
 
-### Prerequisites
+## Prerequisites
 
 You must have a working Kubernetes 1.5 cluster to run the examples in this
 document. The examples use a small nginx webserver that echoes back the source
@@ -50,7 +50,7 @@ deployment "source-ip-app" created
 
 {% capture lessoncontent %}
 
-### Source IP for Services with Type=ClusterIP
+## Source IP for Services with Type=ClusterIP
 
 Packets sent to ClusterIP from within the cluster are never source NAT'd if
 you're running kube-proxy in [iptables mode](/docs/user-guide/services/#proxy-mode-iptables),
@@ -107,7 +107,7 @@ command=GET
 ...
 ```
 
-### Source IP for Services with Type=NodePort
+## Source IP for Services with Type=NodePort
 
 As of Kubernetes 1.5, packets sent to Services with [Type=NodePort](/docs/user-guide/services/#type-nodeport)
 are source NAT'd by default. You can test this by creating a `NodePort` Service:
@@ -204,7 +204,7 @@ Visually:
 
 
 
-### Source IP for Services with Type=LoadBalancer
+## Source IP for Services with Type=LoadBalancer
 
 As of Kubernetes 1.5, packets sent to Services with [Type=LoadBalancer](/docs/user-guide/services/#type-loadbalancer) are
 source NAT'd by default, because all schedulable Kubernetes nodes in the
diff --git a/docs/tutorials/stateful-application/basic-stateful-set.md b/docs/tutorials/stateful-application/basic-stateful-set.md
index 179dd94f71..25621354af 100644
--- a/docs/tutorials/stateful-application/basic-stateful-set.md
+++ b/docs/tutorials/stateful-application/basic-stateful-set.md
@@ -51,7 +51,7 @@ After this tutorial, you will be familiar with the following.
 {% endcapture %}
 
 {% capture lessoncontent %}
-### Creating a StatefulSet 
+## Creating a StatefulSet 
 
 Begin by creating a StatefulSet using the example below. It is similar to the 
 example presented in the
@@ -95,7 +95,7 @@ NAME      DESIRED   CURRENT   AGE
 web       2         1         20s
 ```
 
-#### Ordered Pod Creation
+### Ordered Pod Creation
 
 For a StatefulSet with N replicas, when Pods are being deployed, they are 
 created sequentially, in order from {0..N-1}. Examine the output of the 
@@ -120,11 +120,11 @@ Notice that the `web-0` Pod is launched and set to Pending prior to
 launching `web-1`. In fact, `web-1` is not launched until `web-0` is 
 [Running and Ready](/docs/user-guide/pod-states). 
 
-### Pods in a StatefulSet
+## Pods in a StatefulSet
 Unlike Pods in other controllers, the Pods in a StatefulSet have a unique 
 ordinal index and a stable network identity.
 
-#### Examining the Pod's Ordinal Index
+### Examining the Pod's Ordinal Index
 
 Get the StatefulSet's Pods.
 
@@ -143,7 +143,7 @@ Set controller. The Pods' names take the form
 `-`. Since the `web` StatefulSet has two 
 replicas, it creates two Pods, `web-0` and `web-1`.
 
-#### Using Stable Network Identities
+### Using Stable Network Identities
 Each Pod has a stable hostname based on its ordinal index. Use
 [`kubectl exec`](/docs/user-guide/kubectl/kubectl_exec/) to execute the 
 `hostname` command in each Pod. 
@@ -253,7 +253,7 @@ liveness and readiness, you can use the SRV records of the Pods (
 application will be able to discover the Pods' addresses when they transition 
 to Running and Ready.
 
-#### Writing to Stable Storage
+### Writing to Stable Storage
 
 Get the PersistentVolumeClaims for `web-0` and `web-1`.
 
@@ -326,14 +326,14 @@ Volume Claims are remounted to their `volumeMount`s. No matter what node `web-0`
 and `web-1` are scheduled on, their PersistentVolumes will be mounted to the 
 appropriate mount points.
 
-### Scaling a StatefulSet
+## Scaling a StatefulSet
 Scaling a StatefulSet refers to increasing or decreasing the number of replicas. 
 This is accomplished by updating the `replicas` field. You can use either
 [`kubectl scale`](/docs/user-guide/kubectl/kubectl_scale/) or
 [`kubectl patch`](/docs/user-guide/kubectl/kubectl_patch/) to scale a Stateful 
 Set.
 
-#### Scaling Up
+### Scaling Up
 
 In one terminal window, watch the Pods in the StatefulSet.
 
@@ -378,7 +378,7 @@ created each Pod sequentially with respect to its ordinal index, and it
 waited for each Pod's predecessor to be Running and Ready before launching the 
 subsequent Pod.
 
-#### Scaling Down
+### Scaling Down
 
 In one terminal, watch the StatefulSet's Pods.
 
@@ -412,7 +412,7 @@ web-3     1/1       Terminating   0         42s
 web-3     1/1       Terminating   0         42s
 ```
 
-#### Ordered Pod Termination
+### Ordered Pod Termination
 
 The controller deleted one Pod at a time, with respect to its ordinal index, 
 in reverse order, and it waited for each to be completely shutdown before 
@@ -438,7 +438,7 @@ the StatefulSet's Pods are deleted. This is still true when Pod deletion is
 caused by scaling the StatefulSet down. This feature can be used to facilitate 
 upgrading the container images of Pods in a StatefulSet.
 
-### Updating Containers
+## Updating Containers
 As demonstrated in the [Scaling a StatefulSet](#scaling-a-statefulset) section,
 the `replicas` field of a StatefulSet is mutable. The only other field of a 
 StatefulSet that can be updated is the `spec.template.containers` field. 
@@ -530,14 +530,14 @@ gcr.io/google_containers/nginx-slim:0.7
 
 All the Pods in the StatefulSet are now running a new container image.
 
-### Deleting StatefulSets
+## Deleting StatefulSets
 
 StatefulSet supports both Non-Cascading and Cascading deletion. In a 
 Non-Cascading Delete, the StatefulSet's Pods are not deleted when the Stateful
 Set is deleted. In a Cascading Delete, both the StatefulSet and its Pods are 
 deleted.
 
-#### Non-Cascading Delete
+### Non-Cascading Delete
 
 In one terminal window, watch the Pods in the StatefulSet.
 
@@ -643,7 +643,7 @@ because the StatefulSet never deletes the PersistentVolumes associated with a
 Pod. When you recreated the StatefulSet and it relaunched `web-0`, its original 
 PersistentVolume was remounted.
 
-#### Cascading Delete
+### Cascading Delete
 
 In one terminal window, watch the Pods in the StatefulSet.
 
diff --git a/docs/tutorials/stateful-application/run-replicated-stateful-application.md b/docs/tutorials/stateful-application/run-replicated-stateful-application.md
index 30d22e1cce..cdc373b00d 100644
--- a/docs/tutorials/stateful-application/run-replicated-stateful-application.md
+++ b/docs/tutorials/stateful-application/run-replicated-stateful-application.md
@@ -49,12 +49,12 @@ on general patterns for running stateful applications in Kubernetes.
 
 {% capture lessoncontent %}
 
-### Deploying MySQL
+## Deploying MySQL
 
 The example MySQL deployment consists of a ConfigMap, two Services,
 and a StatefulSet.
 
-#### ConfigMap
+### ConfigMap
 
 Create the ConfigMap from the following YAML configuration file:
 
@@ -74,7 +74,7 @@ portions to apply to different Pods.
 Each Pod decides which portion to look at as it's initializing,
 based on information provided by the StatefulSet controller.
 
-#### Services
+### Services
 
 Create the Services from the following YAML configuration file:
 
@@ -100,7 +100,7 @@ Because there is only one MySQL master, clients should connect directly to the
 MySQL master Pod (through its DNS entry within the Headless Service) to execute
 writes.
 
-#### StatefulSet
+### StatefulSet
 
 Finally, create the StatefulSet from the following YAML configuration file:
 
@@ -133,7 +133,7 @@ This manifest uses a variety of techniques for managing stateful Pods as part of
 a StatefulSet. The next section highlights some of these techniques to explain
 what happens as the StatefulSet creates Pods.
 
-### Understanding stateful Pod initialization
+## Understanding stateful Pod initialization
 
 The StatefulSet controller starts Pods one at a time, in order by their
 ordinal index.
@@ -146,7 +146,7 @@ In this case, that results in Pods named `mysql-0`, `mysql-1`, and `mysql-2`.
 The Pod template in the above StatefulSet manifest takes advantage of these
 properties to perform orderly startup of MySQL replication.
 
-#### Generating configuration
+### Generating configuration
 
 Before starting any of the containers in the Pod spec, the Pod first runs any
 [Init Containers](/docs/user-guide/production-pods/#handling-initialization)
@@ -175,7 +175,7 @@ Combined with the StatefulSet controller's
 this ensures the MySQL master is Ready before creating slaves, so they can begin
 replicating.
 
-#### Cloning existing data
+### Cloning existing data
 
 In general, when a new Pod joins the set as a slave, it must assume the MySQL
 master might already have data on it. It also must assume that the replication
@@ -196,7 +196,7 @@ from the Pod whose ordinal index is one lower.
 This works because the StatefulSet controller always ensures Pod `N` is
 Ready before starting Pod `N+1`.
 
-#### Starting replication
+### Starting replication
 
 After the Init Containers complete successfully, the regular containers run.
 The MySQL Pods consist of a `mysql` container that runs the actual `mysqld`
@@ -220,7 +220,7 @@ connections from other Pods requesting a data clone.
 This server remains up indefinitely in case the StatefulSet scales up, or in
 case the next Pod loses its PersistentVolumeClaim and needs to redo the clone.
 
-### Sending client traffic
+## Sending client traffic
 
 You can send test queries to the MySQL master (hostname `mysql-0.mysql`)
 by running a temporary container with the `mysql:5.7` image and running the
@@ -287,13 +287,13 @@ endpoint might be selected upon each connection attempt:
 You can press **Ctrl+C** when you want to stop the loop, but it's useful to keep
 it running in another window so you can see the effects of the following steps.
 
-### Simulating Pod and Node downtime
+## Simulating Pod and Node downtime
 
 To demonstrate the increased availability of reading from the pool of slaves
 instead of a single server, keep the `SELECT @@server_id` loop from above
 running while you force a Pod out of the Ready state.
 
-#### Break the Readiness Probe
+### Break the Readiness Probe
 
 The [readiness probe](/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks)
 for the `mysql` container runs the command `mysql -h 127.0.0.1 -e 'SELECT 1'`
@@ -333,7 +333,7 @@ after a few seconds:
 kubectl exec mysql-2 -c mysql -- mv /usr/bin/mysql.off /usr/bin/mysql
 ```
 
-#### Delete Pods
+### Delete Pods
 
 The StatefulSet also recreates Pods if they're deleted, similar to what a
 ReplicaSet does for stateless Pods.
@@ -348,7 +348,7 @@ PersistentVolumeClaim.
 You should see server ID `102` disappear from the loop output for a while
 and then return on its own.
 
-#### Drain a Node
+### Drain a Node
 
 If your Kubernetes cluster has multiple Nodes, you can simulate Node downtime
 (such as when Nodes are upgraded) by issuing a
@@ -407,7 +407,7 @@ Now uncordon the Node to return it to a normal state:
 kubectl uncordon 
 ```
 
-### Scaling the number of slaves
+## Scaling the number of slaves
 
 With MySQL replication, you can scale your read query capacity by adding slaves.
 With StatefulSet, you can do this with a single command:
diff --git a/docs/tutorials/stateful-application/run-stateful-application.md b/docs/tutorials/stateful-application/run-stateful-application.md
index 928aaecacd..dc7655831f 100644
--- a/docs/tutorials/stateful-application/run-stateful-application.md
+++ b/docs/tutorials/stateful-application/run-stateful-application.md
@@ -37,7 +37,7 @@ application is MySQL.
 
 {% capture lessoncontent %}
 
-### Set up a disk in your environment
+## Set up a disk in your environment
 
 You can use any type of persistent volume for your stateful app. See
 [Types of Persistent Volumes](/docs/user-guide/persistent-volumes/#types-of-persistent-volumes)
@@ -66,7 +66,7 @@ kubectl create -f http://k8s.io/docs/tutorials/stateful-application/gce-volume.y
 ```
 
 
-### Deploy MySQL
+## Deploy MySQL
 
 You can run a stateful application by creating a Kubernetes Deployment
 and connecting it to an existing PersistentVolume using a
@@ -146,7 +146,7 @@ for a secure solution.
         Access Modes:	RWO
         No events.
 
-### Accessing the MySQL instance
+## Accessing the MySQL instance
 
 The preceding YAML file creates a service that
 allows other Pods in the cluster to access the database. The Service option
@@ -171,7 +171,7 @@ If you don't see a command prompt, try pressing enter.
 mysql> 
 ```
 
-### Updating
+## Updating
 
 The image or any other part of the Deployment can be updated as usual
 with the `kubectl apply` command. Here are some precautions that are
@@ -187,7 +187,7 @@ specific to stateful apps:
   one Pod running at a time. The `Recreate` strategy will stop the
   first pod before creating a new one with the updated configuration.
 
-### Deleting a deployment
+## Deleting a deployment
 
 Delete the deployed objects by name:
 
diff --git a/docs/tutorials/stateful-application/zookeeper.md b/docs/tutorials/stateful-application/zookeeper.md
index 1b550fe718..836192de9f 100644
--- a/docs/tutorials/stateful-application/zookeeper.md
+++ b/docs/tutorials/stateful-application/zookeeper.md
@@ -58,7 +58,7 @@ After this tutorial, you will know the following.
 
 {% capture lessoncontent %}
 
-#### ZooKeeper Basics
+### ZooKeeper Basics
 
 [Apache ZooKeeper](https://zookeeper.apache.org/doc/current/) is a 
 distributed, open-source coordination service for distributed applications.
@@ -86,7 +86,7 @@ snapshot their in memory state to storage media. These snapshots can be loaded
 directly into memory, and all WAL entries that preceded the snapshot may be 
 safely discarded.
 
-### Creating a ZooKeeper Ensemble
+## Creating a ZooKeeper Ensemble
 
 The manifest below contains a 
 [Headless Service](/docs/user-guide/services/#headless-services), 
@@ -145,7 +145,7 @@ zk-2      1/1       Running   0         40s
 The StatefulSet controller creates three Pods, and each Pod has a container with 
 a [ZooKeeper 3.4.9](http://www-us.apache.org/dist/zookeeper/zookeeper-3.4.9/) server.
 
-#### Facilitating Leader Election
+### Facilitating Leader Election
 
 As there is no terminating algorithm for electing a leader in an anonymous 
 network, Zab requires explicit membership configuration in order to perform 
@@ -242,7 +242,7 @@ server.2=zk-1.zk-headless.default.svc.cluster.local:2888:3888
 server.3=zk-2.zk-headless.default.svc.cluster.local:2888:3888
 ```
 
-#### Achieving Consensus
+### Achieving Consensus
 
 Consensus protocols require that the identifiers of each participant be 
 unique. No two participants in the Zab protocol should claim the same unique 
@@ -301,7 +301,7 @@ and at least two of the Pods are Running and Ready), or they will fail to do so
 (if either of the aforementioned conditions are not met). No state will arise 
 where one server acknowledges a write on behalf of another.
 
-#### Sanity Testing the Ensemble
+### Sanity Testing the Ensemble
 
 The most basic sanity test is to write some data to one ZooKeeper server and 
 to read the data from another. 
@@ -348,7 +348,7 @@ dataLength = 5
 numChildren = 0
 ```
 
-#### Providing Durable Storage
+### Providing Durable Storage
 
 As mentioned in the [ZooKeeper Basics](#zookeeper-basics) section,
 ZooKeeper commits all entries to a durable WAL, and periodically writes snapshots 
@@ -507,7 +507,7 @@ same PersistentVolume mounted to the ZooKeeper server's data directory.
 Even when the Pods are rescheduled, all of the writes made to the ZooKeeper 
 servers' WALs, and all of their snapshots, remain durable.
 
-### Ensuring Consistent Configuration
+## Ensuring Consistent Configuration
 
 As noted in the [Facilitating Leader Election](#facilitating-leader-election) and
 [Achieving Consensus](#achieving-consensus) sections, the servers in a 
@@ -651,7 +651,7 @@ ZK_DATA_LOG_DIR=/var/lib/zookeeper/log
 ZK_LOG_DIR=/var/log/zookeeper
 ```
 
-#### Configuring Logging
+### Configuring Logging
 
 One of the files generated by the `zkConfigGen.sh` script controls ZooKeeper's logging. 
 ZooKeeper uses [Log4j](http://logging.apache.org/log4j/2.x/), and, by default, 
@@ -721,7 +721,7 @@ For cluster level log shipping and aggregation, you should consider deploying a
 [sidecar](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html) 
 container to rotate and ship your logs.
 
-#### Configuring a Non-Privileged User
+### Configuring a Non-Privileged User
 
 The best practices with respect to allowing an application to run as a privileged 
 user inside of a container are a matter of debate. If your organization requires 
@@ -773,7 +773,7 @@ and the ZooKeeper process is able to successfully read and write its data.
 drwxr-sr-x 3 zookeeper zookeeper 4096 Dec  5 20:45 /var/lib/zookeeper/data
 ```
 
-### Managing the ZooKeeper Process
+## Managing the ZooKeeper Process
 
 The [ZooKeeper documentation](https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_supervision) 
 documentation indicates that "You will want to have a supervisory process that 
@@ -783,7 +783,7 @@ common pattern. When deploying an application in Kubernetes, rather than using
 an external utility as a supervisory process, you should use Kubernetes as the 
 watchdog for your application.
 
-#### Handling Process Failure 
+### Handling Process Failure 
 
 
 [Restart Policies](/docs/user-guide/pod-states/#restartpolicy) control how 
@@ -846,7 +846,7 @@ child process. This ensures that Kubernetes will restart the application's
 container when the process implementing the application's business logic fails. 
 
 
-#### Testing for Liveness
+### Testing for Liveness
 
 
 Configuring your application to restart failed processes is not sufficient to 
@@ -918,7 +918,7 @@ zk-0      1/1       Running   1         1h
 ```
 
 
-#### Testing for Readiness
+### Testing for Readiness
 
 
 Readiness is not the same as liveness. If a process is alive, it is scheduled 
@@ -951,7 +951,7 @@ to specify both. This ensures that only healthy servers in the ZooKeeper
 ensemble receive network traffic.
 
 
-### Tolerating Node Failure
+## Tolerating Node Failure
 
 ZooKeeper needs a quorum of servers in order to successfully commit mutations 
 to data. For a three server ensemble, two servers must be healthy in order for 
@@ -1013,7 +1013,7 @@ Service in the domain defined by the `topologyKey`. The `topologyKey`
 different rules, labels, and selectors, you can extend this technique to spread 
 your ensemble across physical, network, and power failure domains.
 
-### Surviving Maintenance
+## Surviving Maintenance
 
 **In this section you will cordon and drain nodes. If you are using this tutorial
 on a shared cluster, be sure that this will not adversely affect other tenants.**
diff --git a/docs/tutorials/stateless-application/expose-external-ip-address-service.md b/docs/tutorials/stateless-application/expose-external-ip-address-service.md
index 23bffda9df..f4a63b1e31 100644
--- a/docs/tutorials/stateless-application/expose-external-ip-address-service.md
+++ b/docs/tutorials/stateless-application/expose-external-ip-address-service.md
@@ -29,7 +29,7 @@ provides load balancing for an application that has two running instances.
 
 {% capture lessoncontent %}
 
-### Creating a service for an application running in two pods
+## Creating a service for an application running in two pods
 
 1. Run a Hello World application in your cluster:
 
@@ -111,7 +111,7 @@ provides load balancing for an application that has two running instances.
 
         Hello Kubernetes!
 
-### Using a service configuration file
+## Using a service configuration file
 
 As an alternative to using `kubectl expose`, you can use a
 [service configuration file](/docs/user-guide/services/operations)
diff --git a/docs/tutorials/stateless-application/expose-external-ip-address.md b/docs/tutorials/stateless-application/expose-external-ip-address.md
index f21abf7e61..665a06a2b0 100644
--- a/docs/tutorials/stateless-application/expose-external-ip-address.md
+++ b/docs/tutorials/stateless-application/expose-external-ip-address.md
@@ -36,7 +36,7 @@ external IP address.
 
 {% capture lessoncontent %}
 
-### Creating a service for an application running in five pods
+## Creating a service for an application running in five pods
 
 1. Run a Hello World application in your cluster:
 
diff --git a/docs/tutorials/stateless-application/hello-minikube.md b/docs/tutorials/stateless-application/hello-minikube.md
index 4f75960b4e..9e6a93e5c3 100644
--- a/docs/tutorials/stateless-application/hello-minikube.md
+++ b/docs/tutorials/stateless-application/hello-minikube.md
@@ -38,7 +38,7 @@ driver.
 
 {% capture lessoncontent %}
 
-### Create a Minikube cluster
+## Create a Minikube cluster
 
 This tutorial uses [Minikube](https://github.com/kubernetes/minikube) to
 create a local cluster. This tutorial also assumes you are using
@@ -94,7 +94,7 @@ Verify that `kubectl` is configured to communicate with your cluster:
 kubectl cluster-info
 ```
 
-### Create your Node.js application
+## Create your Node.js application
 
 The next step is to write the application. Save this code in a folder named `hellonode`
 with the filename `server.js`:
@@ -113,7 +113,7 @@ Stop the running Node.js server by pressing **Ctrl-C**.
 
 The next step is to package your application in a Docker container.
 
-### Create a Docker container image
+## Create a Docker container image
 
 Create a file, also in the `hellonode` folder, named `Dockerfile`. A Dockerfile describes
 the image that you want to build. You can build a Docker container image by extending an
@@ -145,7 +145,7 @@ docker build -t hello-node:v1 .
 
 Now the Minikube VM can run the image you built.
 
-### Create a Deployment
+## Create a Deployment
 
 A Kubernetes [*Pod*](/docs/user-guide/pods/) is a group of one or more Containers,
 tied together for the purposes of administration and networking. The Pod in this
@@ -206,7 +206,7 @@ kubectl config view
 For more information about `kubectl`commands, see the
 [kubectl overview](/docs/user-guide/kubectl-overview/).
 
-### Create a Service
+## Create a Service
 
 By default, the Pod is only accessible by its internal IP address within the
 Kubernetes cluster. To make the `hello-node` Container accessible from outside the
@@ -254,7 +254,7 @@ you should now be able to see some logs:
 kubectl logs 
 ```
 
-### Update your app
+## Update your app
 
 Edit your `server.js` file to return a new message:
 
@@ -281,7 +281,7 @@ Run your app again to view the new message:
 minikube service hello-node
 ```
 
-### Clean up
+## Clean up
 
 Now you can clean up the resources you created in your cluster:
 
diff --git a/docs/tutorials/stateless-application/run-stateless-application-deployment.md b/docs/tutorials/stateless-application/run-stateless-application-deployment.md
index 06ccc74579..8e3d725752 100644
--- a/docs/tutorials/stateless-application/run-stateless-application-deployment.md
+++ b/docs/tutorials/stateless-application/run-stateless-application-deployment.md
@@ -27,7 +27,7 @@ This page shows how to run an application using a Kubernetes Deployment object.
 
 {% capture lessoncontent %}
 
-### Creating and exploring an nginx deployment
+## Creating and exploring an nginx deployment
 
 You can run an application by creating a Kubernetes Deployment object, and you
 can describe a Deployment in a YAML file. For example, this YAML file describes
@@ -72,7 +72,7 @@ a Deployment that runs the nginx:1.7.9 Docker image:
 
     where `` is the name of one of your pods.
 
-### Updating the deployment
+## Updating the deployment
 
 You can update the deployment by applying a new YAML file. This YAML file
 specifies that the deployment should be updated to use nginx 1.8.
@@ -87,7 +87,7 @@ specifies that the deployment should be updated to use nginx 1.8.
 
         kubectl get pods -l app=nginx
 
-### Scaling the application by increasing the replica count
+## Scaling the application by increasing the replica count
 
 You can increase the number of pods in your Deployment by applying a new YAML
 file. This YAML file sets `replicas` to 4, which specifies that the Deployment
@@ -111,7 +111,7 @@ should have four pods:
         nginx-deployment-148880595-fxcez   1/1       Running   0          2m
         nginx-deployment-148880595-rwovn   1/1       Running   0          2m
 
-### Deleting a deployment
+## Deleting a deployment
 
 Delete the deployment by name:
 

From 01d3ade5397e7b6695236804d53ed395a46ecaab Mon Sep 17 00:00:00 2001
From: steveperry-53 
Date: Thu, 19 Jan 2017 14:37:45 -0800
Subject: [PATCH 34/44] Update headings and guidance about headings.

---
 _data/support.yml                             | 23 +++++------
 docs/contribute/create-pull-request.md        | 10 ++---
 docs/contribute/page-templates.md             | 33 ++++++++++-----
 docs/contribute/review-issues.md              | 34 ++++++++--------
 .../contribute/stage-documentation-changes.md |  8 ++--
 docs/contribute/style-guide.md                | 40 +++++++++----------
 docs/contribute/write-new-topic.md            | 18 ++++-----
 7 files changed, 89 insertions(+), 77 deletions(-)

diff --git a/_data/support.yml b/_data/support.yml
index c25faa70f8..a6b13e9d09 100644
--- a/_data/support.yml
+++ b/_data/support.yml
@@ -3,17 +3,6 @@ abstract: "Troubleshooting resources, frequently asked questions, and community
 toc:
 - docs/troubleshooting.md
 
-- title: Contributing to the Kubernetes Docs
-  section:
-  - editdocs.md
-  - docs/contribute/create-pull-request.md
-  - docs/contribute/write-new-topic.md
-  - docs/contribute/stage-documentation-changes.md
-  - docs/contribute/page-templates.md
-  - docs/contribute/review-issues.md
-  - docs/contribute/style-guide.md
-
-
 - title: Troubleshooting
   section:
   - docs/user-guide/debugging-pods-and-replication-controllers.md
@@ -31,6 +20,16 @@ toc:
   - title: Services FAQ
     path: https://github.com/kubernetes/kubernetes/wiki/Services-FAQ/
 
+- title: Contributing to the Kubernetes Docs
+  section:
+  - editdocs.md
+  - docs/contribute/create-pull-request.md
+  - docs/contribute/write-new-topic.md
+  - docs/contribute/stage-documentation-changes.md
+  - docs/contribute/page-templates.md
+  - docs/contribute/review-issues.md
+  - docs/contribute/style-guide.md
+
 - title: Other Resources
   section:
   - title: Kubernetes Issue Tracker on GitHub
@@ -40,6 +39,6 @@ toc:
     path: https://github.com/kubernetes/kubernetes/releases/
   - title: Release Roadmap
     path: https://github.com/kubernetes/kubernetes/milestones/
-  
+
 - title: Deprecation Policy
   path: /docs/deprecation-policy.md
diff --git a/docs/contribute/create-pull-request.md b/docs/contribute/create-pull-request.md
index 4637c0b066..7ed2b2b953 100644
--- a/docs/contribute/create-pull-request.md
+++ b/docs/contribute/create-pull-request.md
@@ -23,7 +23,7 @@ Documentation will be published under the [CC BY SA 4.0](https://github.com/kube
 
 {% capture steps %}
 
-### Creating a fork of the Kubernetes documentation repository
+## Creating a fork of the Kubernetes documentation repository
 
 1. Go to the
 [kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"}
@@ -33,18 +33,18 @@ repository.
 Kubernetes documentation repository in your GitHub account. The copy
 is called a *fork*.
 
-### Making your changes
+## Making your changes
 
 1. In your GitHub account, in your fork of the Kubernetes docs, create
 a new branch to use for your contribution.
 
-1. In your new branch, make your changes and commit them. If you want to 
+1. In your new branch, make your changes and commit them. If you want to
 [write a new topic](/docs/contribute/write-new-topic/),
 choose the
 [page type](/docs/contribute/page-templates/)
 that is the best fit for your content.
 
-### Submitting a pull request to the master branch (Current Release)
+## Submitting a pull request to the master branch (Current Release)
 
 If you want your change to be published in the released version Kubernetes docs,
 create a pull request against the master branch of the Kubernetes
@@ -62,7 +62,7 @@ site where you can verify that your changes have rendered correctly.
 If needed, revise your pull request by committing changes to your
 new branch in your fork.
 
-### Submitting a pull request to the <vnext> branch (Upcoming Release)
+## Submitting a pull request to the <vnext> branch (Upcoming Release)
 
 If your documentation change should not be released until the next release of
 the Kubernetes product, create a pull request against the <vnext> branch
diff --git a/docs/contribute/page-templates.md b/docs/contribute/page-templates.md
index 93fa03a6bb..0dfb600896 100644
--- a/docs/contribute/page-templates.md
+++ b/docs/contribute/page-templates.md
@@ -18,7 +18,7 @@ title: Using Page Templates
 
 
The page templates are in the _includes/templates directory of the kubernetes.github.io repository.
 
-
Task template

+
Task template

 
 
A task page shows how to do a single thing, typically by giving a short
 sequence of steps. Task pages have minimal explanation, but often provide links
@@ -36,10 +36,15 @@ variables, and then include templates/task.md:

     
  • whatsnext - optional
    • 
 
 
+
    In the steps section, use ## to start with a level-two heading. For subheadings,
+use ### and #### as needed. Similarly, if you choose to have a discussion section,
+start the section with a level-two heading.
    
+
 
    Here's an example of a Markdown file that uses the task template:
    
 
 {% raw %}
 
    ---
+title: Configuring This Thing
 ---
 
 {% capture overview %}
@@ -52,14 +57,14 @@ This page shows how to ...
 {% endcapture %}
 
 {% capture steps %}
-### Doing ...
+## Doing ...
 
 1. Do this.
 1. Do this next. Possibly read this [related explanation](...).
 {% endcapture %}
 
 {% capture discussion %}
-### Understanding ...
+## Understanding ...
 
 Here's an interesting thing to know about the steps you just did.
 {% endcapture %}
@@ -77,7 +82,7 @@ Here's an interesting thing to know about the steps you just did.
 
 
    Using an HTTP Proxy to Access the Kubernetes API
    
 
-
    Tutorial template
    
+
    Tutorial template
    
 
 
    A tutorial page shows how to accomplish a goal that is larger than a single
 task. Typically a tutorial page has several sections, each of which has a
@@ -99,10 +104,14 @@ variables, and then include templates/tutorial.md:
    
     
  • whatsnext - optional
    • 
 
 
+
    In the lessoncontent section, use ## to start with a level-two heading. For subheadings,
+use ### and #### as needed.
+
 
    Here's an example of a Markdown file that uses the tutorial template:
    
 
 {% raw %}
 
    ---
+title: Running a Thing
 ---
 
 {% capture overview %}
@@ -121,17 +130,17 @@ This page shows how to ...
 {% endcapture %}
 
 {% capture lessoncontent %}
-### Building ...
+## Building ...
 
 1. Do this.
 1. Do this next. Possibly read this [related explanation](...).
 
-### Running ...
+## Running ...
 
 1. Do this.
 1. Do this next.
 
-### Understanding the code
+## Understanding the code
 Here's something interesting about the code you ran in the preceding steps.
 {% endcapture %}
 
@@ -153,7 +162,7 @@ Here's something interesting about the code you ran in the preceding steps.
 
 
    Running a Stateless Application Using a Deployment
    
 
-
    Concept template
    
+
    Concept template
    
 
 
    A concept page explains some aspect of Kubernetes. For example, a concept
 page might describe the Kubernetes Deployment object and explain the role it
@@ -171,10 +180,14 @@ variables, and then include templates/concept.md:
    
     
  • whatsnext - optional
    • 
 
 
+
    In the body section, use ## to start with a level-two heading. For subheadings,
+use ### and #### as needed.
+
 
    Here's an example of a page that uses the concept template:
    
 
 {% raw %}
 
    ---
+title: Understanding this Thing
 ---
 
 {% capture overview %}
@@ -182,11 +195,11 @@ This page explains ...
 {% endcapture %}
 
 {% capture body %}
-### Understanding ...
+## Understanding ...
 
 Kubernetes provides ...
 
-### Using ...
+## Using ...
 
 To use ...
 {% endcapture %}
diff --git a/docs/contribute/review-issues.md b/docs/contribute/review-issues.md
index 8b16d450c6..e9c13988b5 100644
--- a/docs/contribute/review-issues.md
+++ b/docs/contribute/review-issues.md
@@ -9,50 +9,50 @@ This page explains how you should review and prioritize documentation issues mad
 
 {% capture body %}
 
-### Categorizing issues
-Issues should be sorted into different buckets of work using the following labels and definitions. If an issue doesn't have enough information to identify a problem that can be researched, reviewed, or worked on (i.e. the issue doesn't fit into any of the categories below) you should close the issue with a comment explaining why it is being closed.  
+## Categorizing issues
+Issues should be sorted into different buckets of work using the following labels and definitions. If an issue doesn't have enough information to identify a problem that can be researched, reviewed, or worked on (i.e. the issue doesn't fit into any of the categories below) you should close the issue with a comment explaining why it is being closed.
 
 
-#### Actionable 
+### Actionable
 * Issues that can be worked on with current information (or may need a comment to explain what needs to be done to make it more clear)
-* Allows contributors to have easy to find issues to work on 
+* Allows contributors to have easy to find issues to work on
 
 
-#### Needs Tech Review 
+### Needs Tech Review
 * Issues that need more information in order to be worked on (the proposed solution needs to be proven, a subject matter expert needs to be involved, work needs to be done to understand the problem/resolution and if the issue is still relevant)
-* Promotes transparency about level of work needed for the issue and that issue is in progress 
+* Promotes transparency about level of work needed for the issue and that issue is in progress
 
-#### Needs Docs Review
+### Needs Docs Review
 * Issues that are suggestions for better processes or site improvements that require community agreement to be implemented
 * Topics can be brought to SIG meetings as agenda items
 
 
-### Prioritizing Issues
-The following labels and definitions should be used to prioritize issues. If you change the priority of an issues, please comment on the issue with your reasoning for the change.   
+## Prioritizing Issues
+The following labels and definitions should be used to prioritize issues. If you change the priority of an issues, please comment on the issue with your reasoning for the change.
 
-#### P1
+### P1
 * Major content errors affecting more than 1 page
 * Broken code sample on a heavily trafficked page
 * Errors on a “getting started” page
 * Well known or highly publicized customer pain points
 * Automation issues
 
-#### P2
+### P2
 * Default for all new issues
 * Broken code for sample that is not heavily used
 * Minor content issues in a heavily trafficked page
-* Major content issues on a lower-trafficked page 
+* Major content issues on a lower-trafficked page
 
-#### P3
+### P3
 * Typos and broken anchor links
 
-### Handling special issue types
+## Handling special issue types
 
-#### Duplicate issues
+### Duplicate issues
 If a single problem has one or more issues open for it, the problem should be consolodated into a single issue. You should decide which issue to keep open (or open a new issue), port over all relevant information, link related issues, and close all the other issues that describe the same problem. Only having a single issue to work on will help reduce confusion and avoid duplicating work on the same problem.
 
-#### Dead link issues
-Depending on where the dead link is reported, different actions are required to resolve the issue. Dead links in the API and Kubectl docs are automation issues and should be assigned a P1 until the problem can be fully understood. All other dead links are issues that need to be manually fixed and can be assigned a P3. 
+### Dead link issues
+Depending on where the dead link is reported, different actions are required to resolve the issue. Dead links in the API and Kubectl docs are automation issues and should be assigned a P1 until the problem can be fully understood. All other dead links are issues that need to be manually fixed and can be assigned a P3.
 
 {% endcapture %}
 
diff --git a/docs/contribute/stage-documentation-changes.md b/docs/contribute/stage-documentation-changes.md
index 50e22a1b8b..452c38170c 100644
--- a/docs/contribute/stage-documentation-changes.md
+++ b/docs/contribute/stage-documentation-changes.md
@@ -14,7 +14,7 @@ Create a fork of the Kubernetes documentation repository as described in
 
 {% capture steps %}
 
-### Staging from your GitHub account
+## Staging from your GitHub account
 
 GitHub provides staging of content in your master branch. Note that you
 might not want to merge your changes into your master branch. If that is
@@ -32,7 +32,7 @@ the master branch.
 
         https://.github.io
 
-### Staging a pull request
+## Staging a pull request
 
 When you create a pull request, either against the master or <vnext>
 branch, your changes are staged in a custom subdomain on Netlify so that
@@ -47,7 +47,7 @@ Wait for the **deploy/netlify** check to complete. To the right of
 **deploy/netlify**, click **Details**. This opens a staging site where you
 can see your changes.
 
-### Staging locally using Docker
+## Staging locally using Docker
 
 You can use the k8sdocs Docker image to run a local staging server. If you're
 interested, you can view the
@@ -66,7 +66,7 @@ web server:
 1. View your staged content at
 [http://localhost:4000](http://localhost:4000){: target="_blank"}.
 
-### Staging locally without Docker
+## Staging locally without Docker
 
 1. [Install Ruby 2.2 or later](https://www.ruby-lang.org){: target="_blank"}.
 
diff --git a/docs/contribute/style-guide.md b/docs/contribute/style-guide.md
index 47d3cd75c0..6bb1aa5837 100644
--- a/docs/contribute/style-guide.md
+++ b/docs/contribute/style-guide.md
@@ -15,9 +15,9 @@ docs, follow the instructions on
 
 {% capture body %}
 
-### Documentation formatting standards
+## Documentation formatting standards
 
-#### Use Camel Case for API objects
+### Use Camel Case for API objects
 
 When you refer to an API object, use the same uppercase and lowercase letters
 that are used in the actual object name. Typically, the names of API
@@ -39,7 +39,7 @@ leads to an awkward construction.
   The two ContainerStateTerminated objects ...The two ContainerStateTerminateds ...
 
 
-#### Use angle brackets for placeholders
+### Use angle brackets for placeholders
 
 Use angle brackets for placeholders. Tell the reader what a placeholder
 represents.
@@ -50,7 +50,7 @@ represents.
 
     where `` is the name of one of your pods.
 
-#### Use bold for user interface elements
+### Use bold for user interface elements
 
 
@@ -58,7 +58,7 @@ represents.
   
    
   
    DoDon't
    Select Other.Select 'Other'.
    
 
    
 
-#### Use italics to define or introduce new terms
+### Use italics to define or introduce new terms
 
 
@@ -66,7 +66,7 @@ represents.
   
    
   
    DoDon't
    These components form the control plane.These components form the control plane.
    
 
    
 
-#### Use code style for filenames, directories, and paths
+### Use code style for filenames, directories, and paths
 
 
@@ -75,9 +75,9 @@ represents.
   
    
   
    DoDon't
    Open the /_data/concepts.yaml file.Open the /_data/concepts.yaml file.
    
 
    
 
-### Code snippet formatting
+## Code snippet formatting
 
-#### Use code style for inline code and commands
+### Use code style for inline code and commands
 
 For inline code in an HTML document, use the `` tag. In a Markdown
 document, use the backtick (`).
@@ -88,14 +88,14 @@ document, use the backtick (`).
   The kubectl run command creates a Deployment.The "kubectl run" command creates a Deployment.
 
 
-#### Don't include the command prompt
+### Don't include the command prompt
 
 
    
   
    DoDon't
    
   
    kubectl get pods$ kubectl get pods
    
 
    
 
-#### Separate commands from output
+### Separate commands from output
 
 Verify that the pod is running on your chosen node:
 
@@ -117,11 +117,11 @@ A list of Kubernetes-specific terms and words to be used consistently across the
 {% endcomment %}
 
 
-### Content best practices
+## Content best practices
 
 This section contains suggested best practices for clear, concise, and consistent content.
 
-#### Use present tense
+### Use present tense
 
 
@@ -131,7 +131,7 @@ This section contains suggested best practices for clear, concise, and consisten
 Exception: Use future or past tense if it is required to convey the correct
 meaning.
 
-#### Use active voice
+### Use active voice
 
 
    
   
    DoDon't
    
@@ -141,7 +141,7 @@ meaning.
 
 Exception: Use passive voice if active voice leads to an awkward construction.
 
-#### Use simple and direct language
+### Use simple and direct language
 
 Use simple and direct language. Avoid using unnecessary phrases, such as saying "please."
 
@@ -153,7 +153,7 @@ Use simple and direct language. Avoid using unnecessary phrases, such as saying
 
 
    
   
    DoDon't
    
 
-#### Address the reader as "you"
+### Address the reader as "you"
 
 
@@ -161,9 +161,9 @@ Use simple and direct language. Avoid using unnecessary phrases, such as saying
     
    
   
    DoDon't
    In the preceding output, you can see...In the preceding output, we can see ...
    
 
    
 
-### Patterns to avoid
+## Patterns to avoid
 
-#### Avoid using "we"
+### Avoid using "we"
 
 Using "we" in a sentence can be confusing, because the reader might not know
 whether they're part of the "we" you're describing.
@@ -175,7 +175,7 @@ whether they're part of the "we" you're describing.
   This page teaches you how to use pods.In this page, we are going to learn about pods.
 
 
-#### Avoid jargon and idioms
+### Avoid jargon and idioms
 
 Some readers speak English as a second language. Avoid jargon and idioms to help make their understanding easier.
 
@@ -185,13 +185,13 @@ Some readers speak English as a second language. Avoid jargon and idioms to help
     Create a new cluster.Turn up a new cluster.
 
 
-#### Avoid statements about the future
+### Avoid statements about the future
 
 Avoid making promises or giving hints about the future. If you need to talk about
 an alpha feature, put the text under a heading that identifies it as alpha
 information.
 
-#### Avoid statements that will soon be out of date
+### Avoid statements that will soon be out of date
 
 Avoid words like "currently" and "new." A feature that is new today might not be
 considered new in a few months.
diff --git a/docs/contribute/write-new-topic.md b/docs/contribute/write-new-topic.md
index 3ecae45674..52256390da 100644
--- a/docs/contribute/write-new-topic.md
+++ b/docs/contribute/write-new-topic.md
@@ -13,7 +13,7 @@ Create a fork of the Kubernetes documentation repository as described in
 
 {% capture steps %}
 
-### Choosing a page type
+## Choosing a page type
 
 As you prepare to write a new topic, think about which of these page types
 is the best fit for your content:
@@ -42,7 +42,7 @@ Each page type has a
 that you can use as you write your topic.
 Using templates helps ensure consistency among topics of a given type.
 
-### Choosing a title and filename
+## Choosing a title and filename
 
 Choose a title that has the keywords you want search engines to find.
 Create a filename that uses the words in your title separated by hyphens.
@@ -54,18 +54,18 @@ URL for the topic, for example:
 
        http://kubernetes.io/docs/tasks/access-kubernetes-api/http-proxy-access-api/
 
-### Adding the topic title to the front matter
+## Adding the topic title to the front matter
 
 In your topic, put a `title` field in the
 [front matter](https://jekyllrb.com/docs/frontmatter/).
-The front matter is the YAML block that is between the 
+The front matter is the YAML block that is between the
 triple-dashed lines at the top of the page. Here's an example:
 
     ---
     title: Using an HTTP Proxy to Access the Kubernetes API
     ---
 
-### Choosing a directory
+## Choosing a directory
 
 Depending on your page type, put your new file in a subdirectory of one of these:
 
@@ -76,7 +76,7 @@ Depending on your page type, put your new file in a subdirectory of one of these
 You can put your file in an existing subdirectory, or you can create a new
 subdirectory.
 
-### Creating an entry in the table of contents
+## Creating an entry in the table of contents
 
 Depending page type, create an entry in one of these files:
 
@@ -88,7 +88,7 @@ Here's an example of an entry in /_data/tasks.yaml:
 
     - docs/tasks/configure-pod-container/configure-volume-storage.md
 
-### Including code from another file
+## Including code from another file
 
 To include a code file in your topic, place the code file in the Kubernetes
 documentation repository, preferably in the same directory as your topic
@@ -107,7 +107,7 @@ Here's an example of using the `include` tag:
 
 
    {% include code.html language="yaml" file="gce-volume.yaml" ghlink="/docs/tutorials/stateful-application/gce-volume.yaml" %}
    
 
-### Showing how to create an API object from a configuration file
+## Showing how to create an API object from a configuration file
 
 If you need to show the reader how to create an API object based on a
 configuration file, place the configuration file in the Kubernetes documentation
@@ -127,7 +127,7 @@ Here's an example of a command that creates an API object from a configuration f
 For an example of a topic that uses this technique, see
 [Running a Single-Instance Stateful Application](/docs/tutorials/stateful-application/run-stateful-application/).
 
-### Adding images to a topic
+## Adding images to a topic
 
 Put image files in the `/images` directory. The preferred
 image format is SVG.

From 21e74e1e122d18f1af3cf66cc1d2b4aaa488ba3d Mon Sep 17 00:00:00 2001
From: Phillip Wittrock 
Date: Thu, 19 Jan 2017 15:19:01 -0800
Subject: [PATCH 35/44] Fix API Group for some resources on resource
 reference-docs

---
 docs/resources-reference/v1.5/index.html | 50 ++++++++++++------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/docs/resources-reference/v1.5/index.html b/docs/resources-reference/v1.5/index.html
index 688ce5a06e..c3902110de 100644
--- a/docs/resources-reference/v1.5/index.html
+++ b/docs/resources-reference/v1.5/index.html
@@ -202,7 +202,7 @@ Appears In PodStatus 
 
 
 
-Core
+Batch
 v2alpha1
 CronJob
 
@@ -373,7 +373,7 @@ Appears In CronJob 
 
 
 
-Core
+Extensions
 v1beta1
 DaemonSet
 
@@ -530,7 +530,7 @@ Appears In DaemonSet 
 
 
 
-Core
+Extensions
 v1beta1
 Deployment
 
@@ -794,7 +794,7 @@ apiVersion: batch/v1
 
 
 
-Core
+Batch
 v1
 Job
 
@@ -1201,7 +1201,7 @@ Appears In Pod 
 
 
 
-Core
+Extensions
 v1beta1
 ReplicaSet
 
@@ -1529,7 +1529,7 @@ Appears In ReplicationController 
 
 
-Core
+Apps
 v1beta1
 StatefulSet
 
@@ -1766,7 +1766,7 @@ Appears In EndpointsList 
 
 
 
-Core
+Extensions
 v1beta1
 Ingress
 
@@ -2371,7 +2371,7 @@ Appears In PersistentVolumeClaim 
 
 
-Core
+Storage
 v1beta1
 StorageClass
 
@@ -2788,7 +2788,7 @@ Appears In LimitRange 
 
 
 
-Core
+Autoscaling
 v1
 HorizontalPodAutoscaler
 
@@ -3031,7 +3031,7 @@ Appears In DaemonSetSpec PodDisruptionBudget 
 
 
-Core
+Extensions
 v1beta1
 ThirdPartyResource
 
@@ -3297,7 +3297,7 @@ Appears In ThirdPartyResourceList
 
 
 
-Core
+Certificates
 v1alpha1
 CertificateSigningRequest
 
@@ -3428,7 +3428,7 @@ Appears In CertificateSigningReque
 
 
 
-Core
+RbacAuthorization
 v1alpha1
 ClusterRole
 
@@ -3503,7 +3503,7 @@ Appears In ClusterRoleList 
 
 
 
-Core
+RbacAuthorization
 v1alpha1
 ClusterRoleBinding
 
@@ -3657,7 +3657,7 @@ Appears In ComponentStatusList 
 
 
 
-Core
+Authorization
 v1beta1
 LocalSubjectAccessReview
 
@@ -4315,7 +4315,7 @@ Appears In ResourceQuota 
 
 
 
-Core
+RbacAuthorization
 v1alpha1
 Role
 
@@ -4390,7 +4390,7 @@ Appears In RoleList 
 
 
 
-Core
+RbacAuthorization
 v1alpha1
 RoleBinding
 
@@ -4469,7 +4469,7 @@ Appears In RoleBindingList 
 
 
 
-Core
+Authorization
 v1beta1
 SelfSubjectAccessReview
 
@@ -4619,7 +4619,7 @@ Appears In ServiceAccountList 
 
 
 
-Core
+Authorization
 v1beta1
 SubjectAccessReview
 
@@ -4728,7 +4728,7 @@ Appears In LocalSubjectAccessReview<
 
 
 
-Core
+Authentication
 v1beta1
 TokenReview
 
@@ -4821,7 +4821,7 @@ Appears In TokenReview 
 
 
 
-Core
+Extensions
 v1beta1
 NetworkPolicy
 
@@ -10173,7 +10173,7 @@ Appears In  PersistentVolumeSpec  
 
 
-Core
+Extensions
 v1beta1
 HorizontalPodAutoscaler
 
@@ -10319,7 +10319,7 @@ Appears In HorizontalPodAutoscaler
 
 
-Core
+Extensions
 v1beta1
 Job
 
@@ -10477,7 +10477,7 @@ Appears In Job 
 
 
 
-Core
+Batch
 v2alpha1
 Job
 
@@ -10846,4 +10846,4 @@ Appears In Scale 
 
 
 
-
+
\ No newline at end of file

From 503ddad7a37bed80fdcac32174c05061b7ba4817 Mon Sep 17 00:00:00 2001
From: scjane 
Date: Fri, 20 Jan 2017 11:26:02 +0800
Subject: [PATCH 36/44] Update quick-start.md

---
 docs/user-guide/quick-start.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md
index 78e43eb1ce..6ad7940526 100644
--- a/docs/user-guide/quick-start.md
+++ b/docs/user-guide/quick-start.md
@@ -22,7 +22,7 @@ $ kubectl run my-nginx --image=nginx --replicas=2 --port=80
 deployment "my-nginx" created
 ```
 
-To expose your service to the public internet, run:
+To expose your service to the public Internet, run:
 
 ```shell
 $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer
@@ -49,7 +49,7 @@ NAME         CLUSTER_IP       EXTERNAL_IP       PORT(S)                AGE
 my-nginx     10.179.240.1     25.1.2.3          80/TCP                 8s
 ```
 
-You may need to wait for a minute or two for the external ip address to be provisioned.
+You may need to wait for a minute or two for the external IP address to be provisioned.
 
 In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a [firewall to allow traffic on port 80](/docs/user-guide/services-firewalls).
 

From 1c6d3b40d904bcb9520b9ef363069adddc890b3a Mon Sep 17 00:00:00 2001
From: Phillip Wittrock 
Date: Thu, 19 Jan 2017 20:29:59 -0800
Subject: [PATCH 37/44] Fix issue with "Status" operations not showing up for
 some resource types.

---
 docs/api-reference/v1.5/index.html | 6134 +++++++++++++++++++++++++---
 docs/api-reference/v1.5/navData.js |    2 +-
 2 files changed, 5657 insertions(+), 479 deletions(-)

diff --git a/docs/api-reference/v1.5/index.html b/docs/api-reference/v1.5/index.html
index a665a89afe..84caadbe95 100644
--- a/docs/api-reference/v1.5/index.html
+++ b/docs/api-reference/v1.5/index.html
@@ -11,7 +11,7 @@
 
 
 
-
+
 
    
 
    • kubectl
    • curl
    
 
    API OVERVIEW
    
@@ -2779,7 +2779,100 @@ $ curl -X GET http://
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of DaemonSet
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/daemonsets
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -2857,9 +2950,9 @@ $ curl -X GET http://
 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -2951,7 +3044,7 @@ $ curl -X GET http://
 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -3028,7 +3121,7 @@ $ curl -X GET http://
 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -3414,9 +3507,9 @@ Appears In DeploymentStrategy 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -3601,7 +3694,7 @@ spec:
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -3795,7 +3888,7 @@ spec:
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -3960,7 +4053,7 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-Delete
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -4070,7 +4163,7 @@ orphanDependents: false
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -4163,9 +4256,9 @@ orphanDependents: false
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -4387,7 +4480,7 @@ $ curl -X GET http://
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -4761,7 +4854,7 @@ $ kubectl get deployment -o json
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -4839,7 +4932,7 @@ $ kubectl get deployment -o json
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -5083,7 +5176,7 @@ $ kubectl get deployment deployment-example 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -5176,7 +5269,7 @@ $ kubectl get deployment deployment-example 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -5254,9 +5347,9 @@ $ kubectl get deployment deployment-example 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -5348,7 +5441,7 @@ $ kubectl get deployment deployment-example 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -5425,7 +5518,7 @@ $ kubectl get deployment deployment-example 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -6074,9 +6167,9 @@ Appears In Job 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -6246,7 +6339,7 @@ spec:
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -6338,7 +6431,7 @@ spec:
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -6430,7 +6523,7 @@ spec:
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -6540,7 +6633,7 @@ orphanDependents: false
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -6633,9 +6726,9 @@ orphanDependents: false
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -6831,7 +6924,7 @@ $ curl -X GET http://
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -7051,7 +7144,7 @@ $ kubectl get job -o json
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -7129,7 +7222,7 @@ $ kubectl get job -o json
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -7347,7 +7440,7 @@ $ kubectl get job example-job Watch List
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -7440,7 +7533,7 @@ $ kubectl get job example-job Watch List All Namespaces
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -7518,6 +7611,269 @@ $ kubectl get job example-job Status Operations
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Job
    
+
    HTTP Request
    
+
    PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Job
    
+
    HTTP Request
    
+
    GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Job
    
+
    HTTP Request
    
+
    PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Job
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
 
    
 
    Pod v1
    
 
    
@@ -7759,9 +8115,9 @@ Appears In Pod 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -7849,7 +8205,7 @@ Appears In Pod 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -7941,7 +8297,7 @@ Appears In Pod 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -8033,7 +8389,7 @@ Appears In Pod 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -8133,7 +8489,7 @@ Appears In Pod 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -8226,9 +8582,9 @@ Appears In Pod 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -8313,7 +8669,7 @@ Appears In Pod 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -8406,7 +8762,7 @@ Appears In Pod 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -8484,7 +8840,7 @@ Appears In Pod 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -8581,7 +8937,7 @@ Appears In Pod 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -8674,7 +9030,7 @@ Appears In Pod 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -8752,6 +9108,269 @@ Appears In Pod 
 
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Pod
    
+
    HTTP Request
    
+
    PATCH /api/v1/namespaces/{namespace}/pods/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Pod
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Pod    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Pod
    
+
    HTTP Request
    
+
    GET /api/v1/namespaces/{namespace}/pods/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Pod
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Pod    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Pod
    
+
    HTTP Request
    
+
    PUT /api/v1/namespaces/{namespace}/pods/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Pod
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Pod
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Pod    		OK
    
 
    Proxy Operations
    
 
    See supported operations below...
    
 
    Create Connect Portforward
    
@@ -10180,7 +10799,7 @@ Appears In Pod 
 
 
 
-
    Misc Operations
    
+
    Misc Operations
    
 
    See supported operations below...
    
 
    Read Log
    
 
    
@@ -10488,9 +11107,9 @@ Appears In ReplicaSet 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -10578,7 +11197,7 @@ Appears In ReplicaSet 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -10670,7 +11289,7 @@ Appears In ReplicaSet 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -10762,7 +11381,7 @@ Appears In ReplicaSet 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -10862,7 +11481,7 @@ Appears In ReplicaSet 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -10955,9 +11574,9 @@ Appears In ReplicaSet 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -11042,7 +11661,7 @@ Appears In ReplicaSet 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -11135,7 +11754,7 @@ Appears In ReplicaSet 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -11213,7 +11832,7 @@ Appears In ReplicaSet 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -11310,7 +11929,7 @@ Appears In ReplicaSet 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -11403,7 +12022,7 @@ Appears In ReplicaSet 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -11481,9 +12100,272 @@ Appears In ReplicaSet 
 
 
 
-
    Misc Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Read Scale
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified ReplicaSet
    
+
    HTTP Request
    
+
    PATCH /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicaSet
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicaSet    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified ReplicaSet
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicaSet
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicaSet    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified ReplicaSet
    
+
    HTTP Request
    
+
    PUT /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicaSet
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     ReplicaSet
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicaSet    		OK
    
+
    Misc Operations
    
+
    See supported operations below...
    
+
    Read Scale
    
 
    
 
     kubectl Command
    
 
    
@@ -11560,7 +12442,7 @@ Appears In ReplicaSet 
 
 
 
-
    Replace Scale
    
+
    Replace Scale
    
 
    
 
     kubectl Command
    
 
    
@@ -11652,7 +12534,7 @@ Appears In ReplicaSet 
 
 
 
-
    Patch Scale
    
+
    Patch Scale
    
 
    
 
     kubectl Command
    
 
    
@@ -11941,9 +12823,9 @@ Appears In ReplicationController 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -12031,7 +12913,7 @@ Appears In ReplicationController 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -12123,7 +13005,7 @@ Appears In ReplicationController 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -12215,7 +13097,7 @@ Appears In ReplicationController 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -12315,7 +13197,7 @@ Appears In ReplicationController 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -12408,9 +13290,9 @@ Appears In ReplicationController 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -12495,7 +13377,7 @@ Appears In ReplicationController 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -12588,7 +13470,7 @@ Appears In ReplicationController 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -12666,7 +13548,7 @@ Appears In ReplicationController 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -12763,7 +13645,100 @@ Appears In ReplicationController 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of ReplicationController
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -12841,6 +13816,269 @@ Appears In ReplicationController 
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified ReplicationController
    
+
    HTTP Request
    
+
    PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicationController
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicationController    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified ReplicationController
    
+
    HTTP Request
    
+
    GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicationController
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicationController    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified ReplicationController
    
+
    HTTP Request
    
+
    PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the ReplicationController
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     ReplicationController
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     ReplicationController    		OK
    
 
    
 
    StatefulSet v1beta1
    
 
@@ -12981,9 +14219,9 @@ Appears In StatefulSet
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -13071,7 +14309,7 @@ Appears In StatefulSet 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -13163,7 +14401,7 @@ Appears In StatefulSet 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -13255,7 +14493,7 @@ Appears In StatefulSet 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -13355,7 +14593,7 @@ Appears In StatefulSet 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -13448,9 +14686,9 @@ Appears In StatefulSet 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -13535,7 +14773,7 @@ Appears In StatefulSet 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -13628,7 +14866,7 @@ Appears In StatefulSet 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -13706,7 +14944,7 @@ Appears In StatefulSet 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -13803,7 +15041,7 @@ Appears In StatefulSet 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -13896,7 +15134,7 @@ Appears In StatefulSet 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -13974,9 +15212,9 @@ Appears In StatefulSet 
 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -14068,7 +15306,7 @@ Appears In StatefulSet 
 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -14145,7 +15383,7 @@ Appears In StatefulSet 
 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -14334,9 +15572,9 @@ Appears In EndpointsList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -14424,7 +15662,7 @@ Appears In EndpointsList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -14516,7 +15754,7 @@ Appears In EndpointsList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -14608,7 +15846,7 @@ Appears In EndpointsList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -14708,7 +15946,7 @@ Appears In EndpointsList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -14801,9 +16039,9 @@ Appears In EndpointsList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -14888,7 +16126,7 @@ Appears In EndpointsList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -14981,7 +16219,7 @@ Appears In EndpointsList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -15059,7 +16297,7 @@ Appears In EndpointsList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -15156,7 +16394,7 @@ Appears In EndpointsList 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -15249,7 +16487,7 @@ Appears In EndpointsList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -15450,9 +16688,9 @@ Appears In Ingress 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -15540,7 +16778,7 @@ Appears In Ingress 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -15632,7 +16870,7 @@ Appears In Ingress 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -15724,7 +16962,7 @@ Appears In Ingress 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -15824,7 +17062,7 @@ Appears In Ingress 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -15917,9 +17155,9 @@ Appears In Ingress 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -16004,7 +17242,7 @@ Appears In Ingress 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -16097,7 +17335,7 @@ Appears In Ingress 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -16175,7 +17413,7 @@ Appears In Ingress 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -16272,7 +17510,100 @@ Appears In Ingress 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Ingress
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/ingresses
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -16350,6 +17681,269 @@ Appears In Ingress 
 
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Ingress
    
+
    HTTP Request
    
+
    PATCH /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Ingress
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Ingress    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Ingress
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Ingress
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Ingress    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Ingress
    
+
    HTTP Request
    
+
    PUT /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Ingress
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Ingress
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Ingress    		OK
    
 
    
 
    Service v1
    
 
    
@@ -16549,9 +18143,9 @@ Appears In Service 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -16696,7 +18290,7 @@ spec:
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -16861,7 +18455,7 @@ spec:
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -16994,7 +18588,7 @@ $ curl -X PATCH -H 'Content-Type: application/strategic-Delete
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -17081,9 +18675,9 @@ orphanDependents: false
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -17243,7 +18837,7 @@ $ kubectl get service deployment-
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -17335,7 +18929,7 @@ $ kubectl get service -o json
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -17413,7 +19007,7 @@ $ kubectl get service -o json
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -17591,7 +19185,100 @@ $ kubectl get service deployment-example 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Service
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/services
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -17669,9 +19356,9 @@ $ kubectl get service deployment-example 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -17763,7 +19450,7 @@ $ kubectl get service deployment-example 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -17840,7 +19527,7 @@ $ kubectl get service deployment-example 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -17932,9 +19619,9 @@ $ kubectl get service deployment-example 
 
 
-
    Proxy Operations
    
+
    Proxy Operations
    
 
    See supported operations below...
    
-
    Create Connect Proxy
    
+
    Create Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18011,7 +19698,7 @@ $ kubectl get service deployment-example 
 
 
-
    Create Connect Proxy Path
    
+
    Create Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18092,7 +19779,7 @@ $ kubectl get service deployment-example 
 
 
-
    Create Proxy
    
+
    Create Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18154,7 +19841,7 @@ $ kubectl get service deployment-example 
 
 
-
    Create Proxy Path
    
+
    Create Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18220,7 +19907,7 @@ $ kubectl get service deployment-example 
 
 
-
    Delete Connect Proxy
    
+
    Delete Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18297,7 +19984,7 @@ $ kubectl get service deployment-example 
 
 
-
    Delete Connect Proxy Path
    
+
    Delete Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18378,7 +20065,7 @@ $ kubectl get service deployment-example 
 
 
-
    Delete Proxy
    
+
    Delete Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18440,7 +20127,7 @@ $ kubectl get service deployment-example 
 
 
-
    Delete Proxy Path
    
+
    Delete Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18506,7 +20193,7 @@ $ kubectl get service deployment-example 
 
 
-
    Get Connect Proxy
    
+
    Get Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18583,7 +20270,7 @@ $ kubectl get service deployment-example 
 
 
-
    Get Connect Proxy Path
    
+
    Get Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18664,7 +20351,7 @@ $ kubectl get service deployment-example 
 
 
-
    Get Proxy
    
+
    Get Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18726,7 +20413,7 @@ $ kubectl get service deployment-example 
 
 
-
    Get Proxy Path
    
+
    Get Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18792,7 +20479,7 @@ $ kubectl get service deployment-example 
 
 
-
    Head Connect Proxy
    
+
    Head Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -18869,7 +20556,7 @@ $ kubectl get service deployment-example 
 
 
-
    Head Connect Proxy Path
    
+
    Head Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -18950,7 +20637,7 @@ $ kubectl get service deployment-example 
 
 
-
    Replace Connect Proxy
    
+
    Replace Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -19027,7 +20714,7 @@ $ kubectl get service deployment-example 
 
 
-
    Replace Connect Proxy Path
    
+
    Replace Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -19108,7 +20795,7 @@ $ kubectl get service deployment-example 
 
 
-
    Replace Proxy
    
+
    Replace Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -19170,7 +20857,7 @@ $ kubectl get service deployment-example 
 
 
-
    Replace Proxy Path
    
+
    Replace Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -19320,9 +21007,9 @@ Appears In ConfigMapList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -19410,7 +21097,7 @@ Appears In ConfigMapList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -19502,7 +21189,7 @@ Appears In ConfigMapList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -19594,7 +21281,7 @@ Appears In ConfigMapList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -19694,7 +21381,7 @@ Appears In ConfigMapList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -19787,9 +21474,9 @@ Appears In ConfigMapList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -19874,7 +21561,7 @@ Appears In ConfigMapList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -19967,7 +21654,7 @@ Appears In ConfigMapList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -20045,7 +21732,7 @@ Appears In ConfigMapList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -20142,7 +21829,100 @@ Appears In ConfigMapList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of ConfigMap
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/configmaps
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -20303,9 +22083,9 @@ Appears In SecretList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -20393,7 +22173,7 @@ Appears In SecretList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -20485,7 +22265,7 @@ Appears In SecretList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -20577,7 +22357,7 @@ Appears In SecretList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -20677,7 +22457,7 @@ Appears In SecretList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -20770,9 +22550,9 @@ Appears In SecretList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -20857,7 +22637,7 @@ Appears In SecretList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -20950,7 +22730,7 @@ Appears In SecretList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -21028,7 +22808,7 @@ Appears In SecretList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -21125,7 +22905,7 @@ Appears In SecretList 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -21218,7 +22998,7 @@ Appears In SecretList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -21436,9 +23216,9 @@ Appears In PersistentVolumeClaim 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -21526,7 +23306,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -21618,7 +23398,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -21710,7 +23490,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -21810,7 +23590,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -21903,9 +23683,9 @@ Appears In PersistentVolumeClaim 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -21990,7 +23770,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -22083,7 +23863,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -22161,7 +23941,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -22258,7 +24038,100 @@ Appears In PersistentVolumeClaim 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of PersistentVolumeClaim
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -22336,9 +24209,9 @@ Appears In PersistentVolumeClaim 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -22430,7 +24303,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -22507,7 +24380,7 @@ Appears In PersistentVolumeClaim 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -22679,9 +24552,9 @@ Appears In StorageClassList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -22754,7 +24627,7 @@ Appears In StorageClassList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -22842,7 +24715,7 @@ Appears In StorageClassList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -22930,7 +24803,7 @@ Appears In StorageClassList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -23026,7 +24899,7 @@ Appears In StorageClassList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -23104,9 +24977,9 @@ Appears In StorageClassList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -23187,7 +25060,7 @@ Appears In StorageClassList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -23265,7 +25138,7 @@ Appears In StorageClassList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -23358,6 +25231,84 @@ Appears In StorageClassList 
 
 
 
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of StorageClass
    
+
    HTTP Request
    
+
    GET /apis/storage.k8s.io/v1beta1/watch/storageclasses
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
 
    
 
    Volume v1
    
 
@@ -23602,9 +25553,9 @@ Appears In EventList
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -23692,7 +25643,7 @@ Appears In EventList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -23784,7 +25735,7 @@ Appears In EventList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -23876,7 +25827,7 @@ Appears In EventList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -23976,7 +25927,7 @@ Appears In EventList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -24069,9 +26020,9 @@ Appears In EventList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -24156,7 +26107,7 @@ Appears In EventList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -24249,7 +26200,7 @@ Appears In EventList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -24327,7 +26278,7 @@ Appears In EventList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -24424,7 +26375,100 @@ Appears In EventList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Event
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/events
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -24595,9 +26639,9 @@ Appears In LimitRange 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -24685,7 +26729,7 @@ Appears In LimitRange 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -24777,7 +26821,7 @@ Appears In LimitRange 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -24869,7 +26913,7 @@ Appears In LimitRange 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -24969,7 +27013,7 @@ Appears In LimitRange 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -25062,9 +27106,9 @@ Appears In LimitRange 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -25149,7 +27193,7 @@ Appears In LimitRange 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -25242,7 +27286,7 @@ Appears In LimitRange 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -25320,7 +27364,7 @@ Appears In LimitRange 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -25417,7 +27461,100 @@ Appears In LimitRange 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of LimitRange
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/limitranges
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -25641,9 +27778,9 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -25731,7 +27868,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -25823,7 +27960,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -25915,7 +28052,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -26015,7 +28152,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -26108,9 +28245,9 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -26195,7 +28332,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -26288,7 +28425,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -26366,7 +28503,7 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -26463,7 +28600,100 @@ Appears In HorizontalPodAutoscaler 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -26541,6 +28771,269 @@ Appears In HorizontalPodAutoscaler 
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     HorizontalPodAutoscaler
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
 
    
 
    PodTemplate v1
    
 
@@ -26638,9 +29131,9 @@ Appears In DaemonSetSpecWrite Operations
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -26728,7 +29221,7 @@ Appears In     DaemonSetSpecReplace
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -26820,7 +29313,7 @@ Appears In     DaemonSetSpecPatch
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -26912,7 +29405,7 @@ Appears In     DaemonSetSpecDelete
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -27012,7 +29505,7 @@ Appears In     DaemonSetSpecDelete Collection
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -27105,9 +29598,9 @@ Appears In     DaemonSetSpecRead Operations
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -27192,7 +29685,7 @@ Appears In     DaemonSetSpecList
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -27285,7 +29778,7 @@ Appears In     DaemonSetSpecList All Namespaces
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -27363,7 +29856,7 @@ Appears In     DaemonSetSpecWatch
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -27460,7 +29953,100 @@ Appears In     DaemonSetSpecWatch List All Namespaces
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of PodTemplate
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/podtemplates
    
+
    Path Parameters
    
+
              
    
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -27677,9 +30263,9 @@ Appears In     PodDisruptionBudget 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -27767,7 +30353,7 @@ Appears In PodDisruptionBudget 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -27859,7 +30445,7 @@ Appears In PodDisruptionBudget 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -27951,7 +30537,7 @@ Appears In PodDisruptionBudget 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -28051,7 +30637,7 @@ Appears In PodDisruptionBudget 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -28144,9 +30730,9 @@ Appears In PodDisruptionBudget 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -28231,7 +30817,7 @@ Appears In PodDisruptionBudget 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -28324,7 +30910,7 @@ Appears In PodDisruptionBudget 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -28402,7 +30988,7 @@ Appears In PodDisruptionBudget 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -28499,7 +31085,100 @@ Appears In PodDisruptionBudget 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of PodDisruptionBudget
    
+
    HTTP Request
    
+
    GET /apis/policy/v1beta1/watch/namespaces/{namespace}/poddisruptionbudgets
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -28577,6 +31256,269 @@ Appears In PodDisruptionBudget 
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified PodDisruptionBudget
    
+
    HTTP Request
    
+
    PATCH /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the PodDisruptionBudget
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     PodDisruptionBudget    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified PodDisruptionBudget
    
+
    HTTP Request
    
+
    GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the PodDisruptionBudget
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     PodDisruptionBudget    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified PodDisruptionBudget
    
+
    HTTP Request
    
+
    PUT /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the PodDisruptionBudget
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     PodDisruptionBudget
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     PodDisruptionBudget    		OK
    
 
    
 
    ThirdPartyResource v1beta1
    
 
@@ -28656,9 +31598,9 @@ Appears In ThirdPartyResourceList
    
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -28731,7 +31673,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -28819,7 +31761,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -28907,7 +31849,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -29003,7 +31945,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -29081,9 +32023,9 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -29164,7 +32106,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -29242,7 +32184,7 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -29335,6 +32277,84 @@ Appears In ThirdPartyResourceList
 
 
 
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of ThirdPartyResource
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/thirdpartyresources
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
 
    CLUSTER
    
 
    Cluster resources are responsible for defining configuration of the cluster itself, and are generally only used by cluster operators.
    
 
    
@@ -29383,9 +32403,9 @@ Appears In ThirdPartyResourceList
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -29604,9 +32624,9 @@ Appears In CertificateSigningReque
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -29679,7 +32699,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -29767,7 +32787,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -29855,7 +32875,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -29951,7 +32971,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -30029,9 +33049,9 @@ Appears In     CertificateSigningReque
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -30112,7 +33132,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -30190,7 +33210,7 @@ Appears In     CertificateSigningReque
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -30283,6 +33303,174 @@ Appears In     CertificateSigningReque
 
 
 
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of CertificateSigningRequest
    
+
    HTTP Request
    
+
    GET /apis/certificates.k8s.io/v1alpha1/watch/certificatesigningrequests
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Status Operations
    
+
    See supported operations below...
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified CertificateSigningRequest
    
+
    HTTP Request
    
+
    PUT /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the CertificateSigningRequest
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     CertificateSigningRequest
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     CertificateSigningRequest    		OK
    
 
    
 
    ClusterRole v1alpha1
    
 
@@ -30358,9 +33546,9 @@ Appears In ClusterRoleList
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -30433,7 +33621,7 @@ Appears In ClusterRoleList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -30521,7 +33709,7 @@ Appears In ClusterRoleList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -30609,7 +33797,7 @@ Appears In ClusterRoleList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -30705,7 +33893,7 @@ Appears In ClusterRoleList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -30783,9 +33971,9 @@ Appears In ClusterRoleList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -30858,7 +34046,7 @@ Appears In ClusterRoleList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -30936,7 +34124,7 @@ Appears In ClusterRoleList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -31029,6 +34217,84 @@ Appears In ClusterRoleList 
 
 
 
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of ClusterRole
    
+
    HTTP Request
    
+
    GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
 
    
 
    ClusterRoleBinding v1alpha1
    
 
@@ -31108,9 +34374,9 @@ Appears In ClusterRoleBindingList
    
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -31183,7 +34449,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -31271,7 +34537,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -31359,7 +34625,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -31455,7 +34721,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -31533,9 +34799,9 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -31608,7 +34874,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -31686,7 +34952,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -31779,7 +35045,7 @@ Appears In ClusterRoleBindingList
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -31932,9 +35198,9 @@ Appears In ComponentStatusList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -32007,7 +35273,7 @@ Appears In ComponentStatusList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -32134,9 +35400,9 @@ Appears In ComponentStatusList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -32339,9 +35605,9 @@ Appears In Namespace 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -32414,7 +35680,7 @@ Appears In Namespace 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -32502,7 +35768,7 @@ Appears In Namespace 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -32590,7 +35856,7 @@ Appears In Namespace 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -32686,7 +35952,7 @@ Appears In Namespace 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -32764,9 +36030,9 @@ Appears In Namespace 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -32847,7 +36113,7 @@ Appears In Namespace 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -32925,7 +36191,7 @@ Appears In Namespace 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -33018,6 +36284,335 @@ Appears In Namespace 
 
 
 
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Namespace
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Namespace
    
+
    HTTP Request
    
+
    PATCH /api/v1/namespaces/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Namespace
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Namespace    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Namespace
    
+
    HTTP Request
    
+
    GET /api/v1/namespaces/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Namespace
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Namespace    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Namespace
    
+
    HTTP Request
    
+
    PUT /api/v1/namespaces/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Namespace
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Namespace
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Namespace    		OK
    
 
    
 
    Node v1
    
 
@@ -33181,9 +36776,9 @@ Appears In Node
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -33256,7 +36851,7 @@ Appears In Node 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -33344,7 +36939,7 @@ Appears In Node 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -33432,7 +37027,7 @@ Appears In Node 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -33528,7 +37123,7 @@ Appears In Node 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -33606,9 +37201,9 @@ Appears In Node 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -33689,7 +37284,7 @@ Appears In Node 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -33767,7 +37362,7 @@ Appears In Node 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -33860,9 +37455,338 @@ Appears In Node 
 
 
 
-
    Proxy Operations
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Node
    
+
    HTTP Request
    
+
    GET /api/v1/watch/nodes
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Create Connect Proxy
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Node
    
+
    HTTP Request
    
+
    PATCH /api/v1/nodes/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Node
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Node    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Node
    
+
    HTTP Request
    
+
    GET /api/v1/nodes/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Node
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Node    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Node
    
+
    HTTP Request
    
+
    PUT /api/v1/nodes/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Node
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Node
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Node    		OK
    
+
    Proxy Operations
    
+
    See supported operations below...
    
+
    Create Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -33935,7 +37859,7 @@ Appears In Node 
 
 
 
-
    Create Connect Proxy Path
    
+
    Create Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34012,7 +37936,7 @@ Appears In Node 
 
 
 
-
    Create Proxy
    
+
    Create Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34070,7 +37994,7 @@ Appears In Node 
 
 
 
-
    Create Proxy Path
    
+
    Create Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34132,7 +38056,7 @@ Appears In Node 
 
 
 
-
    Delete Connect Proxy
    
+
    Delete Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34205,7 +38129,7 @@ Appears In Node 
 
 
 
-
    Delete Connect Proxy Path
    
+
    Delete Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34282,7 +38206,7 @@ Appears In Node 
 
 
 
-
    Delete Proxy
    
+
    Delete Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34340,7 +38264,7 @@ Appears In Node 
 
 
 
-
    Delete Proxy Path
    
+
    Delete Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34402,7 +38326,7 @@ Appears In Node 
 
 
 
-
    Get Connect Proxy
    
+
    Get Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34475,7 +38399,7 @@ Appears In Node 
 
 
 
-
    Get Connect Proxy Path
    
+
    Get Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34552,7 +38476,7 @@ Appears In Node 
 
 
 
-
    Get Proxy
    
+
    Get Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34610,7 +38534,7 @@ Appears In Node 
 
 
 
-
    Get Proxy Path
    
+
    Get Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34672,7 +38596,7 @@ Appears In Node 
 
 
 
-
    Head Connect Proxy
    
+
    Head Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34745,7 +38669,7 @@ Appears In Node 
 
 
 
-
    Head Connect Proxy Path
    
+
    Head Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34822,7 +38746,7 @@ Appears In Node 
 
 
 
-
    Replace Connect Proxy
    
+
    Replace Connect Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -34895,7 +38819,7 @@ Appears In Node 
 
 
 
-
    Replace Connect Proxy Path
    
+
    Replace Connect Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -34972,7 +38896,7 @@ Appears In Node 
 
 
 
-
    Replace Proxy
    
+
    Replace Proxy
    
 
    
 
     kubectl Command
    
 
    
@@ -35030,7 +38954,7 @@ Appears In Node 
 
 
 
-
    Replace Proxy Path
    
+
    Replace Proxy Path
    
 
    
 
     kubectl Command
    
 
    
@@ -35300,9 +39224,9 @@ Appears In PersistentVolume 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -35375,7 +39299,7 @@ Appears In PersistentVolume 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -35463,7 +39387,7 @@ Appears In PersistentVolume 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -35551,7 +39475,7 @@ Appears In PersistentVolume 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -35647,7 +39571,7 @@ Appears In PersistentVolume 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -35725,9 +39649,9 @@ Appears In PersistentVolume 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -35808,7 +39732,7 @@ Appears In PersistentVolume 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -35886,7 +39810,7 @@ Appears In PersistentVolume 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -35979,7 +39903,7 @@ Appears In PersistentVolume 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -36057,9 +39981,9 @@ Appears In PersistentVolume 
 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -36147,7 +40071,7 @@ Appears In PersistentVolume 
 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -36220,7 +40144,7 @@ Appears In PersistentVolume 
 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -36431,9 +40355,9 @@ Appears In ResourceQuota 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -36521,7 +40445,7 @@ Appears In ResourceQuota 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -36613,7 +40537,7 @@ Appears In ResourceQuota 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -36705,7 +40629,7 @@ Appears In ResourceQuota 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -36805,7 +40729,7 @@ Appears In ResourceQuota 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -36898,9 +40822,9 @@ Appears In ResourceQuota 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -36985,7 +40909,7 @@ Appears In ResourceQuota 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -37078,7 +41002,7 @@ Appears In ResourceQuota 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -37156,7 +41080,7 @@ Appears In ResourceQuota 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -37253,7 +41177,100 @@ Appears In ResourceQuota 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of ResourceQuota
    
+
    HTTP Request
    
+
    GET /api/v1/watch/namespaces/{namespace}/resourcequotas
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -37331,9 +41348,9 @@ Appears In ResourceQuota 
 
 
 
-
    Status Operations
    
+
    Status Operations
    
 
    See supported operations below...
    
-
    Patch Status
    
+
    Patch Status
    
 
    
 
     kubectl Command
    
 
    
@@ -37425,7 +41442,7 @@ Appears In ResourceQuota 
 
 
 
-
    Read Status
    
+
    Read Status
    
 
    
 
     kubectl Command
    
 
    
@@ -37502,7 +41519,7 @@ Appears In ResourceQuota 
 
 
 
-
    Replace Status
    
+
    Replace Status
    
 
    
 
     kubectl Command
    
 
    
@@ -37669,9 +41686,9 @@ Appears In RoleList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -37759,7 +41776,7 @@ Appears In RoleList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -37851,7 +41868,7 @@ Appears In RoleList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -37943,7 +41960,7 @@ Appears In RoleList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -38043,7 +42060,7 @@ Appears In RoleList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -38136,9 +42153,9 @@ Appears In RoleList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -38215,7 +42232,7 @@ Appears In RoleList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -38308,7 +42325,7 @@ Appears In RoleList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -38386,7 +42403,7 @@ Appears In RoleList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -38483,7 +42500,7 @@ Appears In RoleList 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -38576,7 +42593,7 @@ Appears In RoleList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -38733,9 +42750,9 @@ Appears In RoleBindingList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -38823,7 +42840,7 @@ Appears In RoleBindingList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -38915,7 +42932,7 @@ Appears In RoleBindingList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -39007,7 +43024,7 @@ Appears In RoleBindingList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -39107,7 +43124,7 @@ Appears In RoleBindingList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -39200,9 +43217,9 @@ Appears In RoleBindingList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -39279,7 +43296,7 @@ Appears In RoleBindingList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -39372,7 +43389,7 @@ Appears In RoleBindingList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -39450,7 +43467,7 @@ Appears In RoleBindingList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -39547,7 +43564,7 @@ Appears In RoleBindingList 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -39640,7 +43657,7 @@ Appears In RoleBindingList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -39789,9 +43806,9 @@ Appears In SelfSubjectAccessReview
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -39943,9 +43960,9 @@ Appears In ServiceAccountList 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -40033,7 +44050,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -40125,7 +44142,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -40217,7 +44234,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -40317,7 +44334,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -40410,9 +44427,9 @@ Appears In ServiceAccountList 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -40497,7 +44514,7 @@ Appears In ServiceAccountList 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -40590,7 +44607,7 @@ Appears In ServiceAccountList 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -40668,7 +44685,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -40765,7 +44782,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Watch List
    
+
    Watch List
    
 
    
 
     kubectl Command
    
 
    
@@ -40858,7 +44875,7 @@ Appears In ServiceAccountList 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -41045,9 +45062,9 @@ Appears In LocalSubjectAccessReview<
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -41213,9 +45230,9 @@ Appears In     TokenReview 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -41384,9 +45401,9 @@ Appears In NetworkPolicy 
 
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -41474,7 +45491,7 @@ Appears In NetworkPolicy 
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -41566,7 +45583,7 @@ Appears In NetworkPolicy 
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -41658,7 +45675,7 @@ Appears In NetworkPolicy 
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -41758,7 +45775,7 @@ Appears In NetworkPolicy 
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -41851,9 +45868,9 @@ Appears In NetworkPolicy 
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -41938,7 +45955,7 @@ Appears In NetworkPolicy 
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -42031,7 +46048,7 @@ Appears In NetworkPolicy 
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -42109,7 +46126,7 @@ Appears In NetworkPolicy 
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -42206,7 +46223,100 @@ Appears In NetworkPolicy 
 
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of NetworkPolicy
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/networkpolicies
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -47686,9 +51796,9 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -47776,7 +51886,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -47868,7 +51978,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -47960,7 +52070,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -48060,7 +52170,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -48153,9 +52263,9 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -48240,7 +52350,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -48333,7 +52443,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -48411,7 +52521,7 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -48508,7 +52618,100 @@ Appears In HorizontalPodAutoscaler
 
 
-
    Watch List All Namespaces
    
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/horizontalpodautoscalers
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -48586,6 +52789,269 @@ Appears In HorizontalPodAutoscaler
 
 
+
    Status Operations
    
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    PATCH /apis/extensions/v1beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified HorizontalPodAutoscaler
    
+
    HTTP Request
    
+
    PUT /apis/extensions/v1beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the HorizontalPodAutoscaler
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     HorizontalPodAutoscaler
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     HorizontalPodAutoscaler    		OK
    
 
    
 
    Job v1beta1
    
 
@@ -48744,9 +53210,9 @@ Appears In Job
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -48916,7 +53382,7 @@ spec:
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -49008,7 +53474,7 @@ spec:
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -49100,7 +53566,7 @@ spec:
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -49210,7 +53676,7 @@ orphanDependents: false
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -49303,9 +53769,9 @@ orphanDependents: false
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -49501,7 +53967,7 @@ $ curl -X GET http://
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -49721,7 +54187,7 @@ $ kubectl get job -o json
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -49799,7 +54265,7 @@ $ kubectl get job -o json
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -50017,7 +54483,100 @@ $ kubectl get job example-job Watch List All Namespaces
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Job
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/jobs
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -50095,6 +54654,269 @@ $ kubectl get job example-job Status Operations
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Job
    
+
    HTTP Request
    
+
    PATCH /apis/extensions/v1beta1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Job
    
+
    HTTP Request
    
+
    GET /apis/extensions/v1beta1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Job
    
+
    HTTP Request
    
+
    PUT /apis/extensions/v1beta1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Job
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
 
    
 
    Job v2alpha1
    
 
@@ -50253,9 +55075,9 @@ Appears In Job
     
 
 
 
    
-
    Write Operations
    
+
    Write Operations
    
 
    See supported operations below...
    
-
    Create
    
+
    Create
    
 
    
 
     kubectl Command
    
 
    
@@ -50425,7 +55247,7 @@ spec:
 
 
 
-
    Replace
    
+
    Replace
    
 
    
 
     kubectl Command
    
 
    
@@ -50517,7 +55339,7 @@ spec:
 
 
 
-
    Patch
    
+
    Patch
    
 
    
 
     kubectl Command
    
 
    
@@ -50609,7 +55431,7 @@ spec:
 
 
 
-
    Delete
    
+
    Delete
    
 
    
 
     kubectl Command
    
 
    
@@ -50719,7 +55541,7 @@ orphanDependents: false
 
 
 
-
    Delete Collection
    
+
    Delete Collection
    
 
    
 
     kubectl Command
    
 
    
@@ -50812,9 +55634,9 @@ orphanDependents: false
 
 
 
-
    Read Operations
    
+
    Read Operations
    
 
    See supported operations below...
    
-
    Read
    
+
    Read
    
 
    
 
     kubectl Command
    
 
    
@@ -51010,7 +55832,7 @@ $ curl -X GET http://
 
 
 
-
    List
    
+
    List
    
 
    
 
     kubectl Command
    
 
    
@@ -51230,7 +56052,7 @@ $ kubectl get job -o json
 
 
 
-
    List All Namespaces
    
+
    List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -51308,7 +56130,7 @@ $ kubectl get job -o json
 
 
 
-
    Watch
    
+
    Watch
    
 
    
 
     kubectl Command
    
 
    
@@ -51526,7 +56348,100 @@ $ kubectl get job example-job Watch List All Namespaces
+
    Watch List
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    watch individual changes to a list of Job
    
+
    HTTP Request
    
+
    GET /apis/batch/v2alpha1/watch/namespaces/{namespace}/jobs
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    fieldSelectorA selector to restrict the list of returned objects by their fields. Defaults to everything.
    labelSelectorA selector to restrict the list of returned objects by their labels. Defaults to everything.
    prettyIf 'true', then the output is pretty printed.
    resourceVersionWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
    timeoutSecondsTimeout for the list/watch call.
    watchWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Event    		OK
    
+
    Watch List All Namespaces
    
 
    
 
     kubectl Command
    
 
    
@@ -51604,6 +56519,269 @@ $ kubectl get job example-job Status Operations
+
    See supported operations below...
    
+
    Patch Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    partially update status of the specified Job
    
+
    HTTP Request
    
+
    PATCH /apis/batch/v2alpha1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Patch
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Read Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    read status of the specified Job
    
+
    HTTP Request
    
+
    GET /apis/batch/v2alpha1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
+
    Replace Status
    
+
    
+
     kubectl Command
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     curl Command (requires kubectl proxy to be running)
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Output
    
+
    
+
    
+Coming Soon
+
    
+
    
+
     Response Body
    
+
    
+
    
+Coming Soon
+
    
+
    replace status of the specified Job
    
+
    HTTP Request
    
+
    PUT /apis/batch/v2alpha1/namespaces/{namespace}/jobs/{name}/status
    
+
    Path Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    namename of the Job
    namespaceobject name and auth scope, such as for teams and projects
    
+
    Query Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    prettyIf 'true', then the output is pretty printed.
    
+
    Body Parameters
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ParameterDescription
    body 
     Job
    
+
    Response
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    CodeDescription
    200 
     Job    		OK
    
 
    
 
    JobCondition v1beta1
    
 
@@ -51827,4 +57005,4 @@ Appears In Scale
-
+
\ No newline at end of file
diff --git a/docs/api-reference/v1.5/navData.js b/docs/api-reference/v1.5/navData.js
index 2b19be8860..fc3b93deea 100644
--- a/docs/api-reference/v1.5/navData.js
+++ b/docs/api-reference/v1.5/navData.js
@@ -1 +1 @@
-(function(){navData = {"toc":[{"section":"scale-v1beta1","subsections":[]},{"section":"jobcondition-v2alpha1","subsections":[]},{"section":"jobcondition-v1beta1","subsections":[]},{"section":"job-v2alpha1","subsections":[{"section":"-strong-read-operations-strong--484","subsections":[{"section":"watch-list-all-namespaces-489"},{"section":"watch-488"},{"section":"list-all-namespaces-487"},{"section":"list-486"},{"section":"read-485"}]},{"section":"-strong-write-operations-strong--478","subsections":[{"section":"delete-collection-483"},{"section":"delete-482"},{"section":"patch-481"},{"section":"replace-480"},{"section":"create-479"}]}]},{"section":"job-v1beta1","subsections":[{"section":"-strong-read-operations-strong--472","subsections":[{"section":"watch-list-all-namespaces-477"},{"section":"watch-476"},{"section":"list-all-namespaces-475"},{"section":"list-474"},{"section":"read-473"}]},{"section":"-strong-write-operations-strong--466","subsections":[{"section":"delete-collection-471"},{"section":"delete-470"},{"section":"patch-469"},{"section":"replace-468"},{"section":"create-467"}]}]},{"section":"horizontalpodautoscaler-v1beta1","subsections":[{"section":"-strong-read-operations-strong--460","subsections":[{"section":"watch-list-all-namespaces-465"},{"section":"watch-464"},{"section":"list-all-namespaces-463"},{"section":"list-462"},{"section":"read-461"}]},{"section":"-strong-write-operations-strong--454","subsections":[{"section":"delete-collection-459"},{"section":"delete-458"},{"section":"patch-457"},{"section":"replace-456"},{"section":"create-455"}]}]},{"section":"event-versioned","subsections":[]},{"section":"-strong-old-api-versions-strong-","subsections":[]},{"section":"-strong-definitions-strong-","subsections":[{"section":"vspherevirtualdiskvolumesource-v1"},{"section":"volumemount-v1"},{"section":"userinfo-v1beta1"},{"section":"time-unversioned"},{"section":"tcpsocketaction-v1"},{"section":"subresourcereference-v1beta1"},{"section":"subject-v1alpha1"},{"section":"statusdetails-unversioned"},{"section":"statuscause-unversioned"},{"section":"status-unversioned"},{"section":"serviceport-v1"},{"section":"serveraddressbyclientcidr-unversioned"},{"section":"securitycontext-v1"},{"section":"secretvolumesource-v1"},{"section":"secretkeyselector-v1"},{"section":"scale-v1"},{"section":"selinuxoptions-v1"},{"section":"rollbackconfig-v1beta1"},{"section":"roleref-v1alpha1"},{"section":"resourcerequirements-v1"},{"section":"resourcefieldselector-v1"},{"section":"resourceattributes-v1beta1"},{"section":"replicationcontrollercondition-v1"},{"section":"replicasetcondition-v1beta1"},{"section":"rawextension-runtime"},{"section":"rbdvolumesource-v1"},{"section":"quobytevolumesource-v1"},{"section":"quantity-resource"},{"section":"probe-v1"},{"section":"preconditions-v1"},{"section":"policyrule-v1alpha1"},{"section":"podsecuritycontext-v1"},{"section":"podcondition-v1"},{"section":"photonpersistentdiskvolumesource-v1"},{"section":"persistentvolumeclaimvolumesource-v1"},{"section":"patch-unversioned"},{"section":"ownerreference-v1"},{"section":"objectreference-v1"},{"section":"objectmeta-v1"},{"section":"objectfieldselector-v1"},{"section":"nonresourceattributes-v1beta1"},{"section":"nodesysteminfo-v1"},{"section":"nodedaemonendpoints-v1"},{"section":"nodecondition-v1"},{"section":"nodeaddress-v1"},{"section":"networkpolicyport-v1beta1"},{"section":"networkpolicypeer-v1beta1"},{"section":"networkpolicyingressrule-v1beta1"},{"section":"nfsvolumesource-v1"},{"section":"localobjectreference-v1"},{"section":"loadbalancerstatus-v1"},{"section":"loadbalanceringress-v1"},{"section":"listmeta-unversioned"},{"section":"limitrangeitem-v1"},{"section":"lifecycle-v1"},{"section":"labelselectorrequirement-unversioned"},{"section":"labelselector-unversioned"},{"section":"keytopath-v1"},{"section":"jobtemplatespec-v2alpha1"},{"section":"jobcondition-v1"},{"section":"intorstring-intstr"},{"section":"ingresstls-v1beta1"},{"section":"ingressrule-v1beta1"},{"section":"ingressbackend-v1beta1"},{"section":"info-version"},{"section":"iscsivolumesource-v1"},{"section":"hostpathvolumesource-v1"},{"section":"handler-v1"},{"section":"httpingressrulevalue-v1beta1"},{"section":"httpingresspath-v1beta1"},{"section":"httpheader-v1"},{"section":"httpgetaction-v1"},{"section":"groupversionfordiscovery-unversioned"},{"section":"glusterfsvolumesource-v1"},{"section":"gitrepovolumesource-v1"},{"section":"gcepersistentdiskvolumesource-v1"},{"section":"flockervolumesource-v1"},{"section":"flexvolumesource-v1"},{"section":"fcvolumesource-v1"},{"section":"execaction-v1"},{"section":"eviction-v1beta1"},{"section":"eventsource-v1"},{"section":"envvarsource-v1"},{"section":"envvar-v1"},{"section":"endpointsubset-v1"},{"section":"endpointport-v1"},{"section":"endpointaddress-v1"},{"section":"emptydirvolumesource-v1"},{"section":"downwardapivolumesource-v1"},{"section":"downwardapivolumefile-v1"},{"section":"deploymentcondition-v1beta1"},{"section":"deleteoptions-v1"},{"section":"daemonendpoint-v1"},{"section":"crossversionobjectreference-v1"},{"section":"containerstatewaiting-v1"},{"section":"containerstateterminated-v1"},{"section":"containerstaterunning-v1"},{"section":"containerstate-v1"},{"section":"containerport-v1"},{"section":"containerimage-v1"},{"section":"configmapvolumesource-v1"},{"section":"configmapkeyselector-v1"},{"section":"componentcondition-v1"},{"section":"cindervolumesource-v1"},{"section":"certificatesigningrequestcondition-v1alpha1"},{"section":"cephfsvolumesource-v1"},{"section":"capabilities-v1"},{"section":"cputargetutilization-v1beta1"},{"section":"azurefilevolumesource-v1"},{"section":"azurediskvolumesource-v1"},{"section":"attachedvolume-v1"},{"section":"awselasticblockstorevolumesource-v1"},{"section":"apiversions-unversioned"},{"section":"apiversion-v1beta1"},{"section":"apiresource-unversioned"},{"section":"apigroup-unversioned"}]},{"section":"networkpolicy-v1beta1","subsections":[{"section":"-strong-read-operations-strong--448","subsections":[{"section":"watch-list-all-namespaces-453"},{"section":"watch-452"},{"section":"list-all-namespaces-451"},{"section":"list-450"},{"section":"read-449"}]},{"section":"-strong-write-operations-strong--442","subsections":[{"section":"delete-collection-447"},{"section":"delete-446"},{"section":"patch-445"},{"section":"replace-444"},{"section":"create-443"}]}]},{"section":"tokenreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--440","subsections":[{"section":"create-441"}]}]},{"section":"subjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--438","subsections":[{"section":"create-439"}]}]},{"section":"serviceaccount-v1","subsections":[{"section":"-strong-read-operations-strong--431","subsections":[{"section":"watch-list-all-namespaces-437"},{"section":"watch-list-436"},{"section":"watch-435"},{"section":"list-all-namespaces-434"},{"section":"list-433"},{"section":"read-432"}]},{"section":"-strong-write-operations-strong--425","subsections":[{"section":"delete-collection-430"},{"section":"delete-429"},{"section":"patch-428"},{"section":"replace-427"},{"section":"create-426"}]}]},{"section":"selfsubjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--423","subsections":[{"section":"create-424"}]}]},{"section":"rolebinding-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--416","subsections":[{"section":"watch-list-all-namespaces-422"},{"section":"watch-list-421"},{"section":"watch-420"},{"section":"list-all-namespaces-419"},{"section":"list-418"},{"section":"read-417"}]},{"section":"-strong-write-operations-strong--410","subsections":[{"section":"delete-collection-415"},{"section":"delete-414"},{"section":"patch-413"},{"section":"replace-412"},{"section":"create-411"}]}]},{"section":"role-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--403","subsections":[{"section":"watch-list-all-namespaces-409"},{"section":"watch-list-408"},{"section":"watch-407"},{"section":"list-all-namespaces-406"},{"section":"list-405"},{"section":"read-404"}]},{"section":"-strong-write-operations-strong--397","subsections":[{"section":"delete-collection-402"},{"section":"delete-401"},{"section":"patch-400"},{"section":"replace-399"},{"section":"create-398"}]}]},{"section":"resourcequota-v1","subsections":[{"section":"-strong-status-operations-strong--393","subsections":[{"section":"replace-status-396"},{"section":"read-status-395"},{"section":"patch-status-394"}]},{"section":"-strong-read-operations-strong--387","subsections":[{"section":"watch-list-all-namespaces-392"},{"section":"watch-391"},{"section":"list-all-namespaces-390"},{"section":"list-389"},{"section":"read-388"}]},{"section":"-strong-write-operations-strong--381","subsections":[{"section":"delete-collection-386"},{"section":"delete-385"},{"section":"patch-384"},{"section":"replace-383"},{"section":"create-382"}]}]},{"section":"persistentvolume-v1","subsections":[{"section":"-strong-status-operations-strong--377","subsections":[{"section":"replace-status-380"},{"section":"read-status-379"},{"section":"patch-status-378"}]},{"section":"-strong-read-operations-strong--372","subsections":[{"section":"watch-list-376"},{"section":"watch-375"},{"section":"list-374"},{"section":"read-373"}]},{"section":"-strong-write-operations-strong--366","subsections":[{"section":"delete-collection-371"},{"section":"delete-370"},{"section":"patch-369"},{"section":"replace-368"},{"section":"create-367"}]}]},{"section":"node-v1","subsections":[{"section":"-strong-proxy-operations-strong--347","subsections":[{"section":"replace-proxy-path-365"},{"section":"replace-proxy-364"},{"section":"replace-connect-proxy-path-363"},{"section":"replace-connect-proxy-362"},{"section":"head-connect-proxy-path-361"},{"section":"head-connect-proxy-360"},{"section":"get-proxy-path-359"},{"section":"get-proxy-358"},{"section":"get-connect-proxy-path-357"},{"section":"get-connect-proxy-356"},{"section":"delete-proxy-path-355"},{"section":"delete-proxy-354"},{"section":"delete-connect-proxy-path-353"},{"section":"delete-connect-proxy-352"},{"section":"create-proxy-path-351"},{"section":"create-proxy-350"},{"section":"create-connect-proxy-path-349"},{"section":"create-connect-proxy-348"}]},{"section":"-strong-read-operations-strong--343","subsections":[{"section":"watch-346"},{"section":"list-345"},{"section":"read-344"}]},{"section":"-strong-write-operations-strong--337","subsections":[{"section":"delete-collection-342"},{"section":"delete-341"},{"section":"patch-340"},{"section":"replace-339"},{"section":"create-338"}]}]},{"section":"namespace-v1","subsections":[{"section":"-strong-read-operations-strong--333","subsections":[{"section":"watch-336"},{"section":"list-335"},{"section":"read-334"}]},{"section":"-strong-write-operations-strong--327","subsections":[{"section":"delete-collection-332"},{"section":"delete-331"},{"section":"patch-330"},{"section":"replace-329"},{"section":"create-328"}]}]},{"section":"localsubjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--325","subsections":[{"section":"create-326"}]}]},{"section":"componentstatus-v1","subsections":[{"section":"-strong-read-operations-strong--322","subsections":[{"section":"list-324"},{"section":"read-323"}]}]},{"section":"clusterrolebinding-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--317","subsections":[{"section":"watch-list-321"},{"section":"watch-320"},{"section":"list-319"},{"section":"read-318"}]},{"section":"-strong-write-operations-strong--311","subsections":[{"section":"delete-collection-316"},{"section":"delete-315"},{"section":"patch-314"},{"section":"replace-313"},{"section":"create-312"}]}]},{"section":"clusterrole-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--307","subsections":[{"section":"watch-310"},{"section":"list-309"},{"section":"read-308"}]},{"section":"-strong-write-operations-strong--301","subsections":[{"section":"delete-collection-306"},{"section":"delete-305"},{"section":"patch-304"},{"section":"replace-303"},{"section":"create-302"}]}]},{"section":"certificatesigningrequest-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--297","subsections":[{"section":"watch-300"},{"section":"list-299"},{"section":"read-298"}]},{"section":"-strong-write-operations-strong--291","subsections":[{"section":"delete-collection-296"},{"section":"delete-295"},{"section":"patch-294"},{"section":"replace-293"},{"section":"create-292"}]}]},{"section":"binding-v1","subsections":[{"section":"-strong-write-operations-strong--289","subsections":[{"section":"create-290"}]}]},{"section":"-strong-cluster-strong-","subsections":[]},{"section":"thirdpartyresource-v1beta1","subsections":[{"section":"-strong-read-operations-strong--285","subsections":[{"section":"watch-288"},{"section":"list-287"},{"section":"read-286"}]},{"section":"-strong-write-operations-strong--279","subsections":[{"section":"delete-collection-284"},{"section":"delete-283"},{"section":"patch-282"},{"section":"replace-281"},{"section":"create-280"}]}]},{"section":"poddisruptionbudget-v1beta1","subsections":[{"section":"-strong-read-operations-strong--273","subsections":[{"section":"watch-list-all-namespaces-278"},{"section":"watch-277"},{"section":"list-all-namespaces-276"},{"section":"list-275"},{"section":"read-274"}]},{"section":"-strong-write-operations-strong--267","subsections":[{"section":"delete-collection-272"},{"section":"delete-271"},{"section":"patch-270"},{"section":"replace-269"},{"section":"create-268"}]}]},{"section":"podtemplate-v1","subsections":[{"section":"-strong-read-operations-strong--261","subsections":[{"section":"watch-list-all-namespaces-266"},{"section":"watch-265"},{"section":"list-all-namespaces-264"},{"section":"list-263"},{"section":"read-262"}]},{"section":"-strong-write-operations-strong--255","subsections":[{"section":"delete-collection-260"},{"section":"delete-259"},{"section":"patch-258"},{"section":"replace-257"},{"section":"create-256"}]}]},{"section":"horizontalpodautoscaler-v1","subsections":[{"section":"-strong-read-operations-strong--249","subsections":[{"section":"watch-list-all-namespaces-254"},{"section":"watch-253"},{"section":"list-all-namespaces-252"},{"section":"list-251"},{"section":"read-250"}]},{"section":"-strong-write-operations-strong--243","subsections":[{"section":"delete-collection-248"},{"section":"delete-247"},{"section":"patch-246"},{"section":"replace-245"},{"section":"create-244"}]}]},{"section":"limitrange-v1","subsections":[{"section":"-strong-read-operations-strong--237","subsections":[{"section":"watch-list-all-namespaces-242"},{"section":"watch-241"},{"section":"list-all-namespaces-240"},{"section":"list-239"},{"section":"read-238"}]},{"section":"-strong-write-operations-strong--231","subsections":[{"section":"delete-collection-236"},{"section":"delete-235"},{"section":"patch-234"},{"section":"replace-233"},{"section":"create-232"}]}]},{"section":"event-v1","subsections":[{"section":"-strong-read-operations-strong--225","subsections":[{"section":"watch-list-all-namespaces-230"},{"section":"watch-229"},{"section":"list-all-namespaces-228"},{"section":"list-227"},{"section":"read-226"}]},{"section":"-strong-write-operations-strong--219","subsections":[{"section":"delete-collection-224"},{"section":"delete-223"},{"section":"patch-222"},{"section":"replace-221"},{"section":"create-220"}]}]},{"section":"-strong-metadata-strong-","subsections":[]},{"section":"volume-v1","subsections":[]},{"section":"storageclass-v1beta1","subsections":[{"section":"-strong-read-operations-strong--215","subsections":[{"section":"watch-218"},{"section":"list-217"},{"section":"read-216"}]},{"section":"-strong-write-operations-strong--209","subsections":[{"section":"delete-collection-214"},{"section":"delete-213"},{"section":"patch-212"},{"section":"replace-211"},{"section":"create-210"}]}]},{"section":"persistentvolumeclaim-v1","subsections":[{"section":"-strong-status-operations-strong--205","subsections":[{"section":"replace-status-208"},{"section":"read-status-207"},{"section":"patch-status-206"}]},{"section":"-strong-read-operations-strong--199","subsections":[{"section":"watch-list-all-namespaces-204"},{"section":"watch-203"},{"section":"list-all-namespaces-202"},{"section":"list-201"},{"section":"read-200"}]},{"section":"-strong-write-operations-strong--193","subsections":[{"section":"delete-collection-198"},{"section":"delete-197"},{"section":"patch-196"},{"section":"replace-195"},{"section":"create-194"}]}]},{"section":"secret-v1","subsections":[{"section":"-strong-read-operations-strong--186","subsections":[{"section":"watch-list-all-namespaces-192"},{"section":"watch-list-191"},{"section":"watch-190"},{"section":"list-all-namespaces-189"},{"section":"list-188"},{"section":"read-187"}]},{"section":"-strong-write-operations-strong--180","subsections":[{"section":"delete-collection-185"},{"section":"delete-184"},{"section":"patch-183"},{"section":"replace-182"},{"section":"create-181"}]}]},{"section":"configmap-v1","subsections":[{"section":"-strong-read-operations-strong--174","subsections":[{"section":"watch-list-all-namespaces-179"},{"section":"watch-178"},{"section":"list-all-namespaces-177"},{"section":"list-176"},{"section":"read-175"}]},{"section":"-strong-write-operations-strong--168","subsections":[{"section":"delete-collection-173"},{"section":"delete-172"},{"section":"patch-171"},{"section":"replace-170"},{"section":"create-169"}]}]},{"section":"-strong-config-storage-strong-","subsections":[]},{"section":"service-v1","subsections":[{"section":"-strong-proxy-operations-strong--149","subsections":[{"section":"replace-proxy-path-167"},{"section":"replace-proxy-166"},{"section":"replace-connect-proxy-path-165"},{"section":"replace-connect-proxy-164"},{"section":"head-connect-proxy-path-163"},{"section":"head-connect-proxy-162"},{"section":"get-proxy-path-161"},{"section":"get-proxy-160"},{"section":"get-connect-proxy-path-159"},{"section":"get-connect-proxy-158"},{"section":"delete-proxy-path-157"},{"section":"delete-proxy-156"},{"section":"delete-connect-proxy-path-155"},{"section":"delete-connect-proxy-154"},{"section":"create-proxy-path-153"},{"section":"create-proxy-152"},{"section":"create-connect-proxy-path-151"},{"section":"create-connect-proxy-150"}]},{"section":"-strong-status-operations-strong--145","subsections":[{"section":"replace-status-148"},{"section":"read-status-147"},{"section":"patch-status-146"}]},{"section":"-strong-read-operations-strong--139","subsections":[{"section":"watch-list-all-namespaces-144"},{"section":"watch-143"},{"section":"list-all-namespaces-142"},{"section":"list-141"},{"section":"read-140"}]},{"section":"-strong-write-operations-strong--134","subsections":[{"section":"delete-138"},{"section":"patch-137"},{"section":"replace-136"},{"section":"create-135"}]}]},{"section":"ingress-v1beta1","subsections":[{"section":"-strong-read-operations-strong--128","subsections":[{"section":"watch-list-all-namespaces-133"},{"section":"watch-132"},{"section":"list-all-namespaces-131"},{"section":"list-130"},{"section":"read-129"}]},{"section":"-strong-write-operations-strong--122","subsections":[{"section":"delete-collection-127"},{"section":"delete-126"},{"section":"patch-125"},{"section":"replace-124"},{"section":"create-123"}]}]},{"section":"endpoints-v1","subsections":[{"section":"-strong-read-operations-strong--115","subsections":[{"section":"watch-list-all-namespaces-121"},{"section":"watch-list-120"},{"section":"watch-119"},{"section":"list-all-namespaces-118"},{"section":"list-117"},{"section":"read-116"}]},{"section":"-strong-write-operations-strong--109","subsections":[{"section":"delete-collection-114"},{"section":"delete-113"},{"section":"patch-112"},{"section":"replace-111"},{"section":"create-110"}]}]},{"section":"-strong-discovery-load-balancing-strong-","subsections":[]},{"section":"statefulset-v1beta1","subsections":[{"section":"-strong-status-operations-strong--105","subsections":[{"section":"replace-status-108"},{"section":"read-status-107"},{"section":"patch-status-106"}]},{"section":"-strong-read-operations-strong--98","subsections":[{"section":"watch-list-all-namespaces-104"},{"section":"watch-list-103"},{"section":"watch-102"},{"section":"list-all-namespaces-101"},{"section":"list-100"},{"section":"read-99"}]},{"section":"-strong-write-operations-strong--92","subsections":[{"section":"delete-collection-97"},{"section":"delete-96"},{"section":"patch-95"},{"section":"replace-94"},{"section":"create-93"}]}]},{"section":"replicationcontroller-v1","subsections":[{"section":"-strong-read-operations-strong--86","subsections":[{"section":"watch-list-all-namespaces-91"},{"section":"watch-90"},{"section":"list-all-namespaces-89"},{"section":"list-88"},{"section":"read-87"}]},{"section":"-strong-write-operations-strong--80","subsections":[{"section":"delete-collection-85"},{"section":"delete-84"},{"section":"patch-83"},{"section":"replace-82"},{"section":"create-81"}]}]},{"section":"replicaset-v1beta1","subsections":[{"section":"-strong-misc-operations-strong--76","subsections":[{"section":"patch-scale-79"},{"section":"replace-scale-78"},{"section":"read-scale-77"}]},{"section":"-strong-read-operations-strong--69","subsections":[{"section":"watch-list-all-namespaces-75"},{"section":"watch-list-74"},{"section":"watch-73"},{"section":"list-all-namespaces-72"},{"section":"list-71"},{"section":"read-70"}]},{"section":"-strong-write-operations-strong--63","subsections":[{"section":"delete-collection-68"},{"section":"delete-67"},{"section":"patch-66"},{"section":"replace-65"},{"section":"create-64"}]}]},{"section":"pod-v1","subsections":[{"section":"-strong-misc-operations-strong--62","subsections":[{"section":"read-log"}]},{"section":"-strong-proxy-operations-strong-","subsections":[{"section":"replace-proxy-path"},{"section":"replace-proxy"},{"section":"replace-connect-proxy-path"},{"section":"replace-connect-proxy"},{"section":"head-connect-proxy-path"},{"section":"head-connect-proxy"},{"section":"get-proxy-path"},{"section":"get-proxy"},{"section":"get-connect-proxy-path"},{"section":"get-connect-proxy"},{"section":"get-connect-portforward"},{"section":"delete-proxy-path"},{"section":"delete-proxy"},{"section":"delete-connect-proxy-path"},{"section":"delete-connect-proxy"},{"section":"create-proxy-path"},{"section":"create-proxy"},{"section":"create-connect-proxy-path"},{"section":"create-connect-proxy"},{"section":"create-connect-portforward"}]},{"section":"-strong-read-operations-strong--55","subsections":[{"section":"watch-list-all-namespaces-61"},{"section":"watch-list-60"},{"section":"watch-59"},{"section":"list-all-namespaces-58"},{"section":"list-57"},{"section":"read-56"}]},{"section":"-strong-write-operations-strong--49","subsections":[{"section":"delete-collection-54"},{"section":"delete-53"},{"section":"patch-52"},{"section":"replace-51"},{"section":"create-50"}]}]},{"section":"job-v1","subsections":[{"section":"-strong-read-operations-strong--42","subsections":[{"section":"watch-list-all-namespaces-48"},{"section":"watch-list-47"},{"section":"watch-46"},{"section":"list-all-namespaces-45"},{"section":"list-44"},{"section":"read-43"}]},{"section":"-strong-write-operations-strong--36","subsections":[{"section":"delete-collection-41"},{"section":"delete-40"},{"section":"patch-39"},{"section":"replace-38"},{"section":"create-37"}]}]},{"section":"deployment-v1beta1","subsections":[{"section":"-strong-misc-operations-strong-","subsections":[{"section":"rollback"},{"section":"patch-scale"},{"section":"replace-scale"},{"section":"read-scale"}]},{"section":"-strong-status-operations-strong--32","subsections":[{"section":"replace-status-35"},{"section":"read-status-34"},{"section":"patch-status-33"}]},{"section":"-strong-read-operations-strong--25","subsections":[{"section":"watch-list-all-namespaces-31"},{"section":"watch-list-30"},{"section":"watch-29"},{"section":"list-all-namespaces-28"},{"section":"list-27"},{"section":"read-26"}]},{"section":"-strong-write-operations-strong--19","subsections":[{"section":"delete-collection-24"},{"section":"delete-23"},{"section":"patch-22"},{"section":"replace-21"},{"section":"create-20"}]}]},{"section":"daemonset-v1beta1","subsections":[{"section":"-strong-status-operations-strong--15","subsections":[{"section":"replace-status-18"},{"section":"read-status-17"},{"section":"patch-status-16"}]},{"section":"-strong-read-operations-strong--9","subsections":[{"section":"watch-list-all-namespaces-14"},{"section":"watch-13"},{"section":"list-all-namespaces-12"},{"section":"list-11"},{"section":"read-10"}]},{"section":"-strong-write-operations-strong--3","subsections":[{"section":"delete-collection-8"},{"section":"delete-7"},{"section":"patch-6"},{"section":"replace-5"},{"section":"create-4"}]}]},{"section":"cronjob-v2alpha1","subsections":[{"section":"-strong-status-operations-strong-","subsections":[{"section":"replace-status"},{"section":"read-status"},{"section":"patch-status"}]},{"section":"-strong-read-operations-strong-","subsections":[{"section":"watch-list-all-namespaces"},{"section":"watch-list"},{"section":"watch"},{"section":"list-all-namespaces"},{"section":"list"},{"section":"read-2"}]},{"section":"-strong-write-operations-strong-","subsections":[{"section":"delete-collection"},{"section":"delete-1"},{"section":"patch"},{"section":"replace"},{"section":"create"}]}]},{"section":"container-v1","subsections":[]},{"section":"-strong-workloads-strong-","subsections":[]},{"section":"-strong-api-overview-strong-","subsections":[{"section":"resource-operations"},{"section":"resource-objects"},{"section":"resource-categories"}]}],"flatToc":["scale-v1beta1","jobcondition-v2alpha1","jobcondition-v1beta1","watch-list-all-namespaces-489","watch-488","list-all-namespaces-487","list-486","read-485","-strong-read-operations-strong--484","delete-collection-483","delete-482","patch-481","replace-480","create-479","-strong-write-operations-strong--478","job-v2alpha1","watch-list-all-namespaces-477","watch-476","list-all-namespaces-475","list-474","read-473","-strong-read-operations-strong--472","delete-collection-471","delete-470","patch-469","replace-468","create-467","-strong-write-operations-strong--466","job-v1beta1","watch-list-all-namespaces-465","watch-464","list-all-namespaces-463","list-462","read-461","-strong-read-operations-strong--460","delete-collection-459","delete-458","patch-457","replace-456","create-455","-strong-write-operations-strong--454","horizontalpodautoscaler-v1beta1","event-versioned","-strong-old-api-versions-strong-","vspherevirtualdiskvolumesource-v1","volumemount-v1","userinfo-v1beta1","time-unversioned","tcpsocketaction-v1","subresourcereference-v1beta1","subject-v1alpha1","statusdetails-unversioned","statuscause-unversioned","status-unversioned","serviceport-v1","serveraddressbyclientcidr-unversioned","securitycontext-v1","secretvolumesource-v1","secretkeyselector-v1","scale-v1","selinuxoptions-v1","rollbackconfig-v1beta1","roleref-v1alpha1","resourcerequirements-v1","resourcefieldselector-v1","resourceattributes-v1beta1","replicationcontrollercondition-v1","replicasetcondition-v1beta1","rawextension-runtime","rbdvolumesource-v1","quobytevolumesource-v1","quantity-resource","probe-v1","preconditions-v1","policyrule-v1alpha1","podsecuritycontext-v1","podcondition-v1","photonpersistentdiskvolumesource-v1","persistentvolumeclaimvolumesource-v1","patch-unversioned","ownerreference-v1","objectreference-v1","objectmeta-v1","objectfieldselector-v1","nonresourceattributes-v1beta1","nodesysteminfo-v1","nodedaemonendpoints-v1","nodecondition-v1","nodeaddress-v1","networkpolicyport-v1beta1","networkpolicypeer-v1beta1","networkpolicyingressrule-v1beta1","nfsvolumesource-v1","localobjectreference-v1","loadbalancerstatus-v1","loadbalanceringress-v1","listmeta-unversioned","limitrangeitem-v1","lifecycle-v1","labelselectorrequirement-unversioned","labelselector-unversioned","keytopath-v1","jobtemplatespec-v2alpha1","jobcondition-v1","intorstring-intstr","ingresstls-v1beta1","ingressrule-v1beta1","ingressbackend-v1beta1","info-version","iscsivolumesource-v1","hostpathvolumesource-v1","handler-v1","httpingressrulevalue-v1beta1","httpingresspath-v1beta1","httpheader-v1","httpgetaction-v1","groupversionfordiscovery-unversioned","glusterfsvolumesource-v1","gitrepovolumesource-v1","gcepersistentdiskvolumesource-v1","flockervolumesource-v1","flexvolumesource-v1","fcvolumesource-v1","execaction-v1","eviction-v1beta1","eventsource-v1","envvarsource-v1","envvar-v1","endpointsubset-v1","endpointport-v1","endpointaddress-v1","emptydirvolumesource-v1","downwardapivolumesource-v1","downwardapivolumefile-v1","deploymentcondition-v1beta1","deleteoptions-v1","daemonendpoint-v1","crossversionobjectreference-v1","containerstatewaiting-v1","containerstateterminated-v1","containerstaterunning-v1","containerstate-v1","containerport-v1","containerimage-v1","configmapvolumesource-v1","configmapkeyselector-v1","componentcondition-v1","cindervolumesource-v1","certificatesigningrequestcondition-v1alpha1","cephfsvolumesource-v1","capabilities-v1","cputargetutilization-v1beta1","azurefilevolumesource-v1","azurediskvolumesource-v1","attachedvolume-v1","awselasticblockstorevolumesource-v1","apiversions-unversioned","apiversion-v1beta1","apiresource-unversioned","apigroup-unversioned","-strong-definitions-strong-","watch-list-all-namespaces-453","watch-452","list-all-namespaces-451","list-450","read-449","-strong-read-operations-strong--448","delete-collection-447","delete-446","patch-445","replace-444","create-443","-strong-write-operations-strong--442","networkpolicy-v1beta1","create-441","-strong-write-operations-strong--440","tokenreview-v1beta1","create-439","-strong-write-operations-strong--438","subjectaccessreview-v1beta1","watch-list-all-namespaces-437","watch-list-436","watch-435","list-all-namespaces-434","list-433","read-432","-strong-read-operations-strong--431","delete-collection-430","delete-429","patch-428","replace-427","create-426","-strong-write-operations-strong--425","serviceaccount-v1","create-424","-strong-write-operations-strong--423","selfsubjectaccessreview-v1beta1","watch-list-all-namespaces-422","watch-list-421","watch-420","list-all-namespaces-419","list-418","read-417","-strong-read-operations-strong--416","delete-collection-415","delete-414","patch-413","replace-412","create-411","-strong-write-operations-strong--410","rolebinding-v1alpha1","watch-list-all-namespaces-409","watch-list-408","watch-407","list-all-namespaces-406","list-405","read-404","-strong-read-operations-strong--403","delete-collection-402","delete-401","patch-400","replace-399","create-398","-strong-write-operations-strong--397","role-v1alpha1","replace-status-396","read-status-395","patch-status-394","-strong-status-operations-strong--393","watch-list-all-namespaces-392","watch-391","list-all-namespaces-390","list-389","read-388","-strong-read-operations-strong--387","delete-collection-386","delete-385","patch-384","replace-383","create-382","-strong-write-operations-strong--381","resourcequota-v1","replace-status-380","read-status-379","patch-status-378","-strong-status-operations-strong--377","watch-list-376","watch-375","list-374","read-373","-strong-read-operations-strong--372","delete-collection-371","delete-370","patch-369","replace-368","create-367","-strong-write-operations-strong--366","persistentvolume-v1","replace-proxy-path-365","replace-proxy-364","replace-connect-proxy-path-363","replace-connect-proxy-362","head-connect-proxy-path-361","head-connect-proxy-360","get-proxy-path-359","get-proxy-358","get-connect-proxy-path-357","get-connect-proxy-356","delete-proxy-path-355","delete-proxy-354","delete-connect-proxy-path-353","delete-connect-proxy-352","create-proxy-path-351","create-proxy-350","create-connect-proxy-path-349","create-connect-proxy-348","-strong-proxy-operations-strong--347","watch-346","list-345","read-344","-strong-read-operations-strong--343","delete-collection-342","delete-341","patch-340","replace-339","create-338","-strong-write-operations-strong--337","node-v1","watch-336","list-335","read-334","-strong-read-operations-strong--333","delete-collection-332","delete-331","patch-330","replace-329","create-328","-strong-write-operations-strong--327","namespace-v1","create-326","-strong-write-operations-strong--325","localsubjectaccessreview-v1beta1","list-324","read-323","-strong-read-operations-strong--322","componentstatus-v1","watch-list-321","watch-320","list-319","read-318","-strong-read-operations-strong--317","delete-collection-316","delete-315","patch-314","replace-313","create-312","-strong-write-operations-strong--311","clusterrolebinding-v1alpha1","watch-310","list-309","read-308","-strong-read-operations-strong--307","delete-collection-306","delete-305","patch-304","replace-303","create-302","-strong-write-operations-strong--301","clusterrole-v1alpha1","watch-300","list-299","read-298","-strong-read-operations-strong--297","delete-collection-296","delete-295","patch-294","replace-293","create-292","-strong-write-operations-strong--291","certificatesigningrequest-v1alpha1","create-290","-strong-write-operations-strong--289","binding-v1","-strong-cluster-strong-","watch-288","list-287","read-286","-strong-read-operations-strong--285","delete-collection-284","delete-283","patch-282","replace-281","create-280","-strong-write-operations-strong--279","thirdpartyresource-v1beta1","watch-list-all-namespaces-278","watch-277","list-all-namespaces-276","list-275","read-274","-strong-read-operations-strong--273","delete-collection-272","delete-271","patch-270","replace-269","create-268","-strong-write-operations-strong--267","poddisruptionbudget-v1beta1","watch-list-all-namespaces-266","watch-265","list-all-namespaces-264","list-263","read-262","-strong-read-operations-strong--261","delete-collection-260","delete-259","patch-258","replace-257","create-256","-strong-write-operations-strong--255","podtemplate-v1","watch-list-all-namespaces-254","watch-253","list-all-namespaces-252","list-251","read-250","-strong-read-operations-strong--249","delete-collection-248","delete-247","patch-246","replace-245","create-244","-strong-write-operations-strong--243","horizontalpodautoscaler-v1","watch-list-all-namespaces-242","watch-241","list-all-namespaces-240","list-239","read-238","-strong-read-operations-strong--237","delete-collection-236","delete-235","patch-234","replace-233","create-232","-strong-write-operations-strong--231","limitrange-v1","watch-list-all-namespaces-230","watch-229","list-all-namespaces-228","list-227","read-226","-strong-read-operations-strong--225","delete-collection-224","delete-223","patch-222","replace-221","create-220","-strong-write-operations-strong--219","event-v1","-strong-metadata-strong-","volume-v1","watch-218","list-217","read-216","-strong-read-operations-strong--215","delete-collection-214","delete-213","patch-212","replace-211","create-210","-strong-write-operations-strong--209","storageclass-v1beta1","replace-status-208","read-status-207","patch-status-206","-strong-status-operations-strong--205","watch-list-all-namespaces-204","watch-203","list-all-namespaces-202","list-201","read-200","-strong-read-operations-strong--199","delete-collection-198","delete-197","patch-196","replace-195","create-194","-strong-write-operations-strong--193","persistentvolumeclaim-v1","watch-list-all-namespaces-192","watch-list-191","watch-190","list-all-namespaces-189","list-188","read-187","-strong-read-operations-strong--186","delete-collection-185","delete-184","patch-183","replace-182","create-181","-strong-write-operations-strong--180","secret-v1","watch-list-all-namespaces-179","watch-178","list-all-namespaces-177","list-176","read-175","-strong-read-operations-strong--174","delete-collection-173","delete-172","patch-171","replace-170","create-169","-strong-write-operations-strong--168","configmap-v1","-strong-config-storage-strong-","replace-proxy-path-167","replace-proxy-166","replace-connect-proxy-path-165","replace-connect-proxy-164","head-connect-proxy-path-163","head-connect-proxy-162","get-proxy-path-161","get-proxy-160","get-connect-proxy-path-159","get-connect-proxy-158","delete-proxy-path-157","delete-proxy-156","delete-connect-proxy-path-155","delete-connect-proxy-154","create-proxy-path-153","create-proxy-152","create-connect-proxy-path-151","create-connect-proxy-150","-strong-proxy-operations-strong--149","replace-status-148","read-status-147","patch-status-146","-strong-status-operations-strong--145","watch-list-all-namespaces-144","watch-143","list-all-namespaces-142","list-141","read-140","-strong-read-operations-strong--139","delete-138","patch-137","replace-136","create-135","-strong-write-operations-strong--134","service-v1","watch-list-all-namespaces-133","watch-132","list-all-namespaces-131","list-130","read-129","-strong-read-operations-strong--128","delete-collection-127","delete-126","patch-125","replace-124","create-123","-strong-write-operations-strong--122","ingress-v1beta1","watch-list-all-namespaces-121","watch-list-120","watch-119","list-all-namespaces-118","list-117","read-116","-strong-read-operations-strong--115","delete-collection-114","delete-113","patch-112","replace-111","create-110","-strong-write-operations-strong--109","endpoints-v1","-strong-discovery-load-balancing-strong-","replace-status-108","read-status-107","patch-status-106","-strong-status-operations-strong--105","watch-list-all-namespaces-104","watch-list-103","watch-102","list-all-namespaces-101","list-100","read-99","-strong-read-operations-strong--98","delete-collection-97","delete-96","patch-95","replace-94","create-93","-strong-write-operations-strong--92","statefulset-v1beta1","watch-list-all-namespaces-91","watch-90","list-all-namespaces-89","list-88","read-87","-strong-read-operations-strong--86","delete-collection-85","delete-84","patch-83","replace-82","create-81","-strong-write-operations-strong--80","replicationcontroller-v1","patch-scale-79","replace-scale-78","read-scale-77","-strong-misc-operations-strong--76","watch-list-all-namespaces-75","watch-list-74","watch-73","list-all-namespaces-72","list-71","read-70","-strong-read-operations-strong--69","delete-collection-68","delete-67","patch-66","replace-65","create-64","-strong-write-operations-strong--63","replicaset-v1beta1","read-log","-strong-misc-operations-strong--62","replace-proxy-path","replace-proxy","replace-connect-proxy-path","replace-connect-proxy","head-connect-proxy-path","head-connect-proxy","get-proxy-path","get-proxy","get-connect-proxy-path","get-connect-proxy","get-connect-portforward","delete-proxy-path","delete-proxy","delete-connect-proxy-path","delete-connect-proxy","create-proxy-path","create-proxy","create-connect-proxy-path","create-connect-proxy","create-connect-portforward","-strong-proxy-operations-strong-","watch-list-all-namespaces-61","watch-list-60","watch-59","list-all-namespaces-58","list-57","read-56","-strong-read-operations-strong--55","delete-collection-54","delete-53","patch-52","replace-51","create-50","-strong-write-operations-strong--49","pod-v1","watch-list-all-namespaces-48","watch-list-47","watch-46","list-all-namespaces-45","list-44","read-43","-strong-read-operations-strong--42","delete-collection-41","delete-40","patch-39","replace-38","create-37","-strong-write-operations-strong--36","job-v1","rollback","patch-scale","replace-scale","read-scale","-strong-misc-operations-strong-","replace-status-35","read-status-34","patch-status-33","-strong-status-operations-strong--32","watch-list-all-namespaces-31","watch-list-30","watch-29","list-all-namespaces-28","list-27","read-26","-strong-read-operations-strong--25","delete-collection-24","delete-23","patch-22","replace-21","create-20","-strong-write-operations-strong--19","deployment-v1beta1","replace-status-18","read-status-17","patch-status-16","-strong-status-operations-strong--15","watch-list-all-namespaces-14","watch-13","list-all-namespaces-12","list-11","read-10","-strong-read-operations-strong--9","delete-collection-8","delete-7","patch-6","replace-5","create-4","-strong-write-operations-strong--3","daemonset-v1beta1","replace-status","read-status","patch-status","-strong-status-operations-strong-","watch-list-all-namespaces","watch-list","watch","list-all-namespaces","list","read-2","-strong-read-operations-strong-","delete-collection","delete-1","patch","replace","create","-strong-write-operations-strong-","cronjob-v2alpha1","container-v1","-strong-workloads-strong-","resource-operations","resource-objects","resource-categories","-strong-api-overview-strong-"]}})();
\ No newline at end of file
+(function(){navData = {"toc":[{"section":"scale-v1beta1","subsections":[]},{"section":"jobcondition-v2alpha1","subsections":[]},{"section":"jobcondition-v1beta1","subsections":[]},{"section":"job-v2alpha1","subsections":[{"section":"-strong-status-operations-strong--558","subsections":[{"section":"replace-status-561"},{"section":"read-status-560"},{"section":"patch-status-559"}]},{"section":"-strong-read-operations-strong--551","subsections":[{"section":"watch-list-all-namespaces-557"},{"section":"watch-list-556"},{"section":"watch-555"},{"section":"list-all-namespaces-554"},{"section":"list-553"},{"section":"read-552"}]},{"section":"-strong-write-operations-strong--545","subsections":[{"section":"delete-collection-550"},{"section":"delete-549"},{"section":"patch-548"},{"section":"replace-547"},{"section":"create-546"}]}]},{"section":"job-v1beta1","subsections":[{"section":"-strong-status-operations-strong--541","subsections":[{"section":"replace-status-544"},{"section":"read-status-543"},{"section":"patch-status-542"}]},{"section":"-strong-read-operations-strong--534","subsections":[{"section":"watch-list-all-namespaces-540"},{"section":"watch-list-539"},{"section":"watch-538"},{"section":"list-all-namespaces-537"},{"section":"list-536"},{"section":"read-535"}]},{"section":"-strong-write-operations-strong--528","subsections":[{"section":"delete-collection-533"},{"section":"delete-532"},{"section":"patch-531"},{"section":"replace-530"},{"section":"create-529"}]}]},{"section":"horizontalpodautoscaler-v1beta1","subsections":[{"section":"-strong-status-operations-strong--524","subsections":[{"section":"replace-status-527"},{"section":"read-status-526"},{"section":"patch-status-525"}]},{"section":"-strong-read-operations-strong--517","subsections":[{"section":"watch-list-all-namespaces-523"},{"section":"watch-list-522"},{"section":"watch-521"},{"section":"list-all-namespaces-520"},{"section":"list-519"},{"section":"read-518"}]},{"section":"-strong-write-operations-strong--511","subsections":[{"section":"delete-collection-516"},{"section":"delete-515"},{"section":"patch-514"},{"section":"replace-513"},{"section":"create-512"}]}]},{"section":"event-versioned","subsections":[]},{"section":"-strong-old-api-versions-strong-","subsections":[]},{"section":"-strong-definitions-strong-","subsections":[{"section":"vspherevirtualdiskvolumesource-v1"},{"section":"volumemount-v1"},{"section":"userinfo-v1beta1"},{"section":"time-unversioned"},{"section":"tcpsocketaction-v1"},{"section":"subresourcereference-v1beta1"},{"section":"subject-v1alpha1"},{"section":"statusdetails-unversioned"},{"section":"statuscause-unversioned"},{"section":"status-unversioned"},{"section":"serviceport-v1"},{"section":"serveraddressbyclientcidr-unversioned"},{"section":"securitycontext-v1"},{"section":"secretvolumesource-v1"},{"section":"secretkeyselector-v1"},{"section":"scale-v1"},{"section":"selinuxoptions-v1"},{"section":"rollbackconfig-v1beta1"},{"section":"roleref-v1alpha1"},{"section":"resourcerequirements-v1"},{"section":"resourcefieldselector-v1"},{"section":"resourceattributes-v1beta1"},{"section":"replicationcontrollercondition-v1"},{"section":"replicasetcondition-v1beta1"},{"section":"rawextension-runtime"},{"section":"rbdvolumesource-v1"},{"section":"quobytevolumesource-v1"},{"section":"quantity-resource"},{"section":"probe-v1"},{"section":"preconditions-v1"},{"section":"policyrule-v1alpha1"},{"section":"podsecuritycontext-v1"},{"section":"podcondition-v1"},{"section":"photonpersistentdiskvolumesource-v1"},{"section":"persistentvolumeclaimvolumesource-v1"},{"section":"patch-unversioned"},{"section":"ownerreference-v1"},{"section":"objectreference-v1"},{"section":"objectmeta-v1"},{"section":"objectfieldselector-v1"},{"section":"nonresourceattributes-v1beta1"},{"section":"nodesysteminfo-v1"},{"section":"nodedaemonendpoints-v1"},{"section":"nodecondition-v1"},{"section":"nodeaddress-v1"},{"section":"networkpolicyport-v1beta1"},{"section":"networkpolicypeer-v1beta1"},{"section":"networkpolicyingressrule-v1beta1"},{"section":"nfsvolumesource-v1"},{"section":"localobjectreference-v1"},{"section":"loadbalancerstatus-v1"},{"section":"loadbalanceringress-v1"},{"section":"listmeta-unversioned"},{"section":"limitrangeitem-v1"},{"section":"lifecycle-v1"},{"section":"labelselectorrequirement-unversioned"},{"section":"labelselector-unversioned"},{"section":"keytopath-v1"},{"section":"jobtemplatespec-v2alpha1"},{"section":"jobcondition-v1"},{"section":"intorstring-intstr"},{"section":"ingresstls-v1beta1"},{"section":"ingressrule-v1beta1"},{"section":"ingressbackend-v1beta1"},{"section":"info-version"},{"section":"iscsivolumesource-v1"},{"section":"hostpathvolumesource-v1"},{"section":"handler-v1"},{"section":"httpingressrulevalue-v1beta1"},{"section":"httpingresspath-v1beta1"},{"section":"httpheader-v1"},{"section":"httpgetaction-v1"},{"section":"groupversionfordiscovery-unversioned"},{"section":"glusterfsvolumesource-v1"},{"section":"gitrepovolumesource-v1"},{"section":"gcepersistentdiskvolumesource-v1"},{"section":"flockervolumesource-v1"},{"section":"flexvolumesource-v1"},{"section":"fcvolumesource-v1"},{"section":"execaction-v1"},{"section":"eviction-v1beta1"},{"section":"eventsource-v1"},{"section":"envvarsource-v1"},{"section":"envvar-v1"},{"section":"endpointsubset-v1"},{"section":"endpointport-v1"},{"section":"endpointaddress-v1"},{"section":"emptydirvolumesource-v1"},{"section":"downwardapivolumesource-v1"},{"section":"downwardapivolumefile-v1"},{"section":"deploymentcondition-v1beta1"},{"section":"deleteoptions-v1"},{"section":"daemonendpoint-v1"},{"section":"crossversionobjectreference-v1"},{"section":"containerstatewaiting-v1"},{"section":"containerstateterminated-v1"},{"section":"containerstaterunning-v1"},{"section":"containerstate-v1"},{"section":"containerport-v1"},{"section":"containerimage-v1"},{"section":"configmapvolumesource-v1"},{"section":"configmapkeyselector-v1"},{"section":"componentcondition-v1"},{"section":"cindervolumesource-v1"},{"section":"certificatesigningrequestcondition-v1alpha1"},{"section":"cephfsvolumesource-v1"},{"section":"capabilities-v1"},{"section":"cputargetutilization-v1beta1"},{"section":"azurefilevolumesource-v1"},{"section":"azurediskvolumesource-v1"},{"section":"attachedvolume-v1"},{"section":"awselasticblockstorevolumesource-v1"},{"section":"apiversions-unversioned"},{"section":"apiversion-v1beta1"},{"section":"apiresource-unversioned"},{"section":"apigroup-unversioned"}]},{"section":"networkpolicy-v1beta1","subsections":[{"section":"-strong-read-operations-strong--504","subsections":[{"section":"watch-list-all-namespaces-510"},{"section":"watch-list-509"},{"section":"watch-508"},{"section":"list-all-namespaces-507"},{"section":"list-506"},{"section":"read-505"}]},{"section":"-strong-write-operations-strong--498","subsections":[{"section":"delete-collection-503"},{"section":"delete-502"},{"section":"patch-501"},{"section":"replace-500"},{"section":"create-499"}]}]},{"section":"tokenreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--496","subsections":[{"section":"create-497"}]}]},{"section":"subjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--494","subsections":[{"section":"create-495"}]}]},{"section":"serviceaccount-v1","subsections":[{"section":"-strong-read-operations-strong--487","subsections":[{"section":"watch-list-all-namespaces-493"},{"section":"watch-list-492"},{"section":"watch-491"},{"section":"list-all-namespaces-490"},{"section":"list-489"},{"section":"read-488"}]},{"section":"-strong-write-operations-strong--481","subsections":[{"section":"delete-collection-486"},{"section":"delete-485"},{"section":"patch-484"},{"section":"replace-483"},{"section":"create-482"}]}]},{"section":"selfsubjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--479","subsections":[{"section":"create-480"}]}]},{"section":"rolebinding-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--472","subsections":[{"section":"watch-list-all-namespaces-478"},{"section":"watch-list-477"},{"section":"watch-476"},{"section":"list-all-namespaces-475"},{"section":"list-474"},{"section":"read-473"}]},{"section":"-strong-write-operations-strong--466","subsections":[{"section":"delete-collection-471"},{"section":"delete-470"},{"section":"patch-469"},{"section":"replace-468"},{"section":"create-467"}]}]},{"section":"role-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--459","subsections":[{"section":"watch-list-all-namespaces-465"},{"section":"watch-list-464"},{"section":"watch-463"},{"section":"list-all-namespaces-462"},{"section":"list-461"},{"section":"read-460"}]},{"section":"-strong-write-operations-strong--453","subsections":[{"section":"delete-collection-458"},{"section":"delete-457"},{"section":"patch-456"},{"section":"replace-455"},{"section":"create-454"}]}]},{"section":"resourcequota-v1","subsections":[{"section":"-strong-status-operations-strong--449","subsections":[{"section":"replace-status-452"},{"section":"read-status-451"},{"section":"patch-status-450"}]},{"section":"-strong-read-operations-strong--442","subsections":[{"section":"watch-list-all-namespaces-448"},{"section":"watch-list-447"},{"section":"watch-446"},{"section":"list-all-namespaces-445"},{"section":"list-444"},{"section":"read-443"}]},{"section":"-strong-write-operations-strong--436","subsections":[{"section":"delete-collection-441"},{"section":"delete-440"},{"section":"patch-439"},{"section":"replace-438"},{"section":"create-437"}]}]},{"section":"persistentvolume-v1","subsections":[{"section":"-strong-status-operations-strong--432","subsections":[{"section":"replace-status-435"},{"section":"read-status-434"},{"section":"patch-status-433"}]},{"section":"-strong-read-operations-strong--427","subsections":[{"section":"watch-list-431"},{"section":"watch-430"},{"section":"list-429"},{"section":"read-428"}]},{"section":"-strong-write-operations-strong--421","subsections":[{"section":"delete-collection-426"},{"section":"delete-425"},{"section":"patch-424"},{"section":"replace-423"},{"section":"create-422"}]}]},{"section":"node-v1","subsections":[{"section":"-strong-proxy-operations-strong--402","subsections":[{"section":"replace-proxy-path-420"},{"section":"replace-proxy-419"},{"section":"replace-connect-proxy-path-418"},{"section":"replace-connect-proxy-417"},{"section":"head-connect-proxy-path-416"},{"section":"head-connect-proxy-415"},{"section":"get-proxy-path-414"},{"section":"get-proxy-413"},{"section":"get-connect-proxy-path-412"},{"section":"get-connect-proxy-411"},{"section":"delete-proxy-path-410"},{"section":"delete-proxy-409"},{"section":"delete-connect-proxy-path-408"},{"section":"delete-connect-proxy-407"},{"section":"create-proxy-path-406"},{"section":"create-proxy-405"},{"section":"create-connect-proxy-path-404"},{"section":"create-connect-proxy-403"}]},{"section":"-strong-status-operations-strong--398","subsections":[{"section":"replace-status-401"},{"section":"read-status-400"},{"section":"patch-status-399"}]},{"section":"-strong-read-operations-strong--393","subsections":[{"section":"watch-list-397"},{"section":"watch-396"},{"section":"list-395"},{"section":"read-394"}]},{"section":"-strong-write-operations-strong--387","subsections":[{"section":"delete-collection-392"},{"section":"delete-391"},{"section":"patch-390"},{"section":"replace-389"},{"section":"create-388"}]}]},{"section":"namespace-v1","subsections":[{"section":"-strong-status-operations-strong--383","subsections":[{"section":"replace-status-386"},{"section":"read-status-385"},{"section":"patch-status-384"}]},{"section":"-strong-read-operations-strong--378","subsections":[{"section":"watch-list-382"},{"section":"watch-381"},{"section":"list-380"},{"section":"read-379"}]},{"section":"-strong-write-operations-strong--372","subsections":[{"section":"delete-collection-377"},{"section":"delete-376"},{"section":"patch-375"},{"section":"replace-374"},{"section":"create-373"}]}]},{"section":"localsubjectaccessreview-v1beta1","subsections":[{"section":"-strong-write-operations-strong--370","subsections":[{"section":"create-371"}]}]},{"section":"componentstatus-v1","subsections":[{"section":"-strong-read-operations-strong--367","subsections":[{"section":"list-369"},{"section":"read-368"}]}]},{"section":"clusterrolebinding-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--362","subsections":[{"section":"watch-list-366"},{"section":"watch-365"},{"section":"list-364"},{"section":"read-363"}]},{"section":"-strong-write-operations-strong--356","subsections":[{"section":"delete-collection-361"},{"section":"delete-360"},{"section":"patch-359"},{"section":"replace-358"},{"section":"create-357"}]}]},{"section":"clusterrole-v1alpha1","subsections":[{"section":"-strong-read-operations-strong--351","subsections":[{"section":"watch-list-355"},{"section":"watch-354"},{"section":"list-353"},{"section":"read-352"}]},{"section":"-strong-write-operations-strong--345","subsections":[{"section":"delete-collection-350"},{"section":"delete-349"},{"section":"patch-348"},{"section":"replace-347"},{"section":"create-346"}]}]},{"section":"certificatesigningrequest-v1alpha1","subsections":[{"section":"-strong-status-operations-strong--343","subsections":[{"section":"replace-status-344"}]},{"section":"-strong-read-operations-strong--338","subsections":[{"section":"watch-list-342"},{"section":"watch-341"},{"section":"list-340"},{"section":"read-339"}]},{"section":"-strong-write-operations-strong--332","subsections":[{"section":"delete-collection-337"},{"section":"delete-336"},{"section":"patch-335"},{"section":"replace-334"},{"section":"create-333"}]}]},{"section":"binding-v1","subsections":[{"section":"-strong-write-operations-strong--330","subsections":[{"section":"create-331"}]}]},{"section":"-strong-cluster-strong-","subsections":[]},{"section":"thirdpartyresource-v1beta1","subsections":[{"section":"-strong-read-operations-strong--325","subsections":[{"section":"watch-list-329"},{"section":"watch-328"},{"section":"list-327"},{"section":"read-326"}]},{"section":"-strong-write-operations-strong--319","subsections":[{"section":"delete-collection-324"},{"section":"delete-323"},{"section":"patch-322"},{"section":"replace-321"},{"section":"create-320"}]}]},{"section":"poddisruptionbudget-v1beta1","subsections":[{"section":"-strong-status-operations-strong--315","subsections":[{"section":"replace-status-318"},{"section":"read-status-317"},{"section":"patch-status-316"}]},{"section":"-strong-read-operations-strong--308","subsections":[{"section":"watch-list-all-namespaces-314"},{"section":"watch-list-313"},{"section":"watch-312"},{"section":"list-all-namespaces-311"},{"section":"list-310"},{"section":"read-309"}]},{"section":"-strong-write-operations-strong--302","subsections":[{"section":"delete-collection-307"},{"section":"delete-306"},{"section":"patch-305"},{"section":"replace-304"},{"section":"create-303"}]}]},{"section":"podtemplate-v1","subsections":[{"section":"-strong-read-operations-strong--295","subsections":[{"section":"watch-list-all-namespaces-301"},{"section":"watch-list-300"},{"section":"watch-299"},{"section":"list-all-namespaces-298"},{"section":"list-297"},{"section":"read-296"}]},{"section":"-strong-write-operations-strong--289","subsections":[{"section":"delete-collection-294"},{"section":"delete-293"},{"section":"patch-292"},{"section":"replace-291"},{"section":"create-290"}]}]},{"section":"horizontalpodautoscaler-v1","subsections":[{"section":"-strong-status-operations-strong--285","subsections":[{"section":"replace-status-288"},{"section":"read-status-287"},{"section":"patch-status-286"}]},{"section":"-strong-read-operations-strong--278","subsections":[{"section":"watch-list-all-namespaces-284"},{"section":"watch-list-283"},{"section":"watch-282"},{"section":"list-all-namespaces-281"},{"section":"list-280"},{"section":"read-279"}]},{"section":"-strong-write-operations-strong--272","subsections":[{"section":"delete-collection-277"},{"section":"delete-276"},{"section":"patch-275"},{"section":"replace-274"},{"section":"create-273"}]}]},{"section":"limitrange-v1","subsections":[{"section":"-strong-read-operations-strong--265","subsections":[{"section":"watch-list-all-namespaces-271"},{"section":"watch-list-270"},{"section":"watch-269"},{"section":"list-all-namespaces-268"},{"section":"list-267"},{"section":"read-266"}]},{"section":"-strong-write-operations-strong--259","subsections":[{"section":"delete-collection-264"},{"section":"delete-263"},{"section":"patch-262"},{"section":"replace-261"},{"section":"create-260"}]}]},{"section":"event-v1","subsections":[{"section":"-strong-read-operations-strong--252","subsections":[{"section":"watch-list-all-namespaces-258"},{"section":"watch-list-257"},{"section":"watch-256"},{"section":"list-all-namespaces-255"},{"section":"list-254"},{"section":"read-253"}]},{"section":"-strong-write-operations-strong--246","subsections":[{"section":"delete-collection-251"},{"section":"delete-250"},{"section":"patch-249"},{"section":"replace-248"},{"section":"create-247"}]}]},{"section":"-strong-metadata-strong-","subsections":[]},{"section":"volume-v1","subsections":[]},{"section":"storageclass-v1beta1","subsections":[{"section":"-strong-read-operations-strong--241","subsections":[{"section":"watch-list-245"},{"section":"watch-244"},{"section":"list-243"},{"section":"read-242"}]},{"section":"-strong-write-operations-strong--235","subsections":[{"section":"delete-collection-240"},{"section":"delete-239"},{"section":"patch-238"},{"section":"replace-237"},{"section":"create-236"}]}]},{"section":"persistentvolumeclaim-v1","subsections":[{"section":"-strong-status-operations-strong--231","subsections":[{"section":"replace-status-234"},{"section":"read-status-233"},{"section":"patch-status-232"}]},{"section":"-strong-read-operations-strong--224","subsections":[{"section":"watch-list-all-namespaces-230"},{"section":"watch-list-229"},{"section":"watch-228"},{"section":"list-all-namespaces-227"},{"section":"list-226"},{"section":"read-225"}]},{"section":"-strong-write-operations-strong--218","subsections":[{"section":"delete-collection-223"},{"section":"delete-222"},{"section":"patch-221"},{"section":"replace-220"},{"section":"create-219"}]}]},{"section":"secret-v1","subsections":[{"section":"-strong-read-operations-strong--211","subsections":[{"section":"watch-list-all-namespaces-217"},{"section":"watch-list-216"},{"section":"watch-215"},{"section":"list-all-namespaces-214"},{"section":"list-213"},{"section":"read-212"}]},{"section":"-strong-write-operations-strong--205","subsections":[{"section":"delete-collection-210"},{"section":"delete-209"},{"section":"patch-208"},{"section":"replace-207"},{"section":"create-206"}]}]},{"section":"configmap-v1","subsections":[{"section":"-strong-read-operations-strong--198","subsections":[{"section":"watch-list-all-namespaces-204"},{"section":"watch-list-203"},{"section":"watch-202"},{"section":"list-all-namespaces-201"},{"section":"list-200"},{"section":"read-199"}]},{"section":"-strong-write-operations-strong--192","subsections":[{"section":"delete-collection-197"},{"section":"delete-196"},{"section":"patch-195"},{"section":"replace-194"},{"section":"create-193"}]}]},{"section":"-strong-config-storage-strong-","subsections":[]},{"section":"service-v1","subsections":[{"section":"-strong-proxy-operations-strong--173","subsections":[{"section":"replace-proxy-path-191"},{"section":"replace-proxy-190"},{"section":"replace-connect-proxy-path-189"},{"section":"replace-connect-proxy-188"},{"section":"head-connect-proxy-path-187"},{"section":"head-connect-proxy-186"},{"section":"get-proxy-path-185"},{"section":"get-proxy-184"},{"section":"get-connect-proxy-path-183"},{"section":"get-connect-proxy-182"},{"section":"delete-proxy-path-181"},{"section":"delete-proxy-180"},{"section":"delete-connect-proxy-path-179"},{"section":"delete-connect-proxy-178"},{"section":"create-proxy-path-177"},{"section":"create-proxy-176"},{"section":"create-connect-proxy-path-175"},{"section":"create-connect-proxy-174"}]},{"section":"-strong-status-operations-strong--169","subsections":[{"section":"replace-status-172"},{"section":"read-status-171"},{"section":"patch-status-170"}]},{"section":"-strong-read-operations-strong--162","subsections":[{"section":"watch-list-all-namespaces-168"},{"section":"watch-list-167"},{"section":"watch-166"},{"section":"list-all-namespaces-165"},{"section":"list-164"},{"section":"read-163"}]},{"section":"-strong-write-operations-strong--157","subsections":[{"section":"delete-161"},{"section":"patch-160"},{"section":"replace-159"},{"section":"create-158"}]}]},{"section":"ingress-v1beta1","subsections":[{"section":"-strong-status-operations-strong--153","subsections":[{"section":"replace-status-156"},{"section":"read-status-155"},{"section":"patch-status-154"}]},{"section":"-strong-read-operations-strong--146","subsections":[{"section":"watch-list-all-namespaces-152"},{"section":"watch-list-151"},{"section":"watch-150"},{"section":"list-all-namespaces-149"},{"section":"list-148"},{"section":"read-147"}]},{"section":"-strong-write-operations-strong--140","subsections":[{"section":"delete-collection-145"},{"section":"delete-144"},{"section":"patch-143"},{"section":"replace-142"},{"section":"create-141"}]}]},{"section":"endpoints-v1","subsections":[{"section":"-strong-read-operations-strong--133","subsections":[{"section":"watch-list-all-namespaces-139"},{"section":"watch-list-138"},{"section":"watch-137"},{"section":"list-all-namespaces-136"},{"section":"list-135"},{"section":"read-134"}]},{"section":"-strong-write-operations-strong--127","subsections":[{"section":"delete-collection-132"},{"section":"delete-131"},{"section":"patch-130"},{"section":"replace-129"},{"section":"create-128"}]}]},{"section":"-strong-discovery-load-balancing-strong-","subsections":[]},{"section":"statefulset-v1beta1","subsections":[{"section":"-strong-status-operations-strong--123","subsections":[{"section":"replace-status-126"},{"section":"read-status-125"},{"section":"patch-status-124"}]},{"section":"-strong-read-operations-strong--116","subsections":[{"section":"watch-list-all-namespaces-122"},{"section":"watch-list-121"},{"section":"watch-120"},{"section":"list-all-namespaces-119"},{"section":"list-118"},{"section":"read-117"}]},{"section":"-strong-write-operations-strong--110","subsections":[{"section":"delete-collection-115"},{"section":"delete-114"},{"section":"patch-113"},{"section":"replace-112"},{"section":"create-111"}]}]},{"section":"replicationcontroller-v1","subsections":[{"section":"-strong-status-operations-strong--106","subsections":[{"section":"replace-status-109"},{"section":"read-status-108"},{"section":"patch-status-107"}]},{"section":"-strong-read-operations-strong--99","subsections":[{"section":"watch-list-all-namespaces-105"},{"section":"watch-list-104"},{"section":"watch-103"},{"section":"list-all-namespaces-102"},{"section":"list-101"},{"section":"read-100"}]},{"section":"-strong-write-operations-strong--93","subsections":[{"section":"delete-collection-98"},{"section":"delete-97"},{"section":"patch-96"},{"section":"replace-95"},{"section":"create-94"}]}]},{"section":"replicaset-v1beta1","subsections":[{"section":"-strong-misc-operations-strong--89","subsections":[{"section":"patch-scale-92"},{"section":"replace-scale-91"},{"section":"read-scale-90"}]},{"section":"-strong-status-operations-strong--85","subsections":[{"section":"replace-status-88"},{"section":"read-status-87"},{"section":"patch-status-86"}]},{"section":"-strong-read-operations-strong--78","subsections":[{"section":"watch-list-all-namespaces-84"},{"section":"watch-list-83"},{"section":"watch-82"},{"section":"list-all-namespaces-81"},{"section":"list-80"},{"section":"read-79"}]},{"section":"-strong-write-operations-strong--72","subsections":[{"section":"delete-collection-77"},{"section":"delete-76"},{"section":"patch-75"},{"section":"replace-74"},{"section":"create-73"}]}]},{"section":"pod-v1","subsections":[{"section":"-strong-misc-operations-strong--71","subsections":[{"section":"read-log"}]},{"section":"-strong-proxy-operations-strong-","subsections":[{"section":"replace-proxy-path"},{"section":"replace-proxy"},{"section":"replace-connect-proxy-path"},{"section":"replace-connect-proxy"},{"section":"head-connect-proxy-path"},{"section":"head-connect-proxy"},{"section":"get-proxy-path"},{"section":"get-proxy"},{"section":"get-connect-proxy-path"},{"section":"get-connect-proxy"},{"section":"get-connect-portforward"},{"section":"delete-proxy-path"},{"section":"delete-proxy"},{"section":"delete-connect-proxy-path"},{"section":"delete-connect-proxy"},{"section":"create-proxy-path"},{"section":"create-proxy"},{"section":"create-connect-proxy-path"},{"section":"create-connect-proxy"},{"section":"create-connect-portforward"}]},{"section":"-strong-status-operations-strong--67","subsections":[{"section":"replace-status-70"},{"section":"read-status-69"},{"section":"patch-status-68"}]},{"section":"-strong-read-operations-strong--60","subsections":[{"section":"watch-list-all-namespaces-66"},{"section":"watch-list-65"},{"section":"watch-64"},{"section":"list-all-namespaces-63"},{"section":"list-62"},{"section":"read-61"}]},{"section":"-strong-write-operations-strong--54","subsections":[{"section":"delete-collection-59"},{"section":"delete-58"},{"section":"patch-57"},{"section":"replace-56"},{"section":"create-55"}]}]},{"section":"job-v1","subsections":[{"section":"-strong-status-operations-strong--50","subsections":[{"section":"replace-status-53"},{"section":"read-status-52"},{"section":"patch-status-51"}]},{"section":"-strong-read-operations-strong--43","subsections":[{"section":"watch-list-all-namespaces-49"},{"section":"watch-list-48"},{"section":"watch-47"},{"section":"list-all-namespaces-46"},{"section":"list-45"},{"section":"read-44"}]},{"section":"-strong-write-operations-strong--37","subsections":[{"section":"delete-collection-42"},{"section":"delete-41"},{"section":"patch-40"},{"section":"replace-39"},{"section":"create-38"}]}]},{"section":"deployment-v1beta1","subsections":[{"section":"-strong-misc-operations-strong-","subsections":[{"section":"rollback"},{"section":"patch-scale"},{"section":"replace-scale"},{"section":"read-scale"}]},{"section":"-strong-status-operations-strong--33","subsections":[{"section":"replace-status-36"},{"section":"read-status-35"},{"section":"patch-status-34"}]},{"section":"-strong-read-operations-strong--26","subsections":[{"section":"watch-list-all-namespaces-32"},{"section":"watch-list-31"},{"section":"watch-30"},{"section":"list-all-namespaces-29"},{"section":"list-28"},{"section":"read-27"}]},{"section":"-strong-write-operations-strong--20","subsections":[{"section":"delete-collection-25"},{"section":"delete-24"},{"section":"patch-23"},{"section":"replace-22"},{"section":"create-21"}]}]},{"section":"daemonset-v1beta1","subsections":[{"section":"-strong-status-operations-strong--16","subsections":[{"section":"replace-status-19"},{"section":"read-status-18"},{"section":"patch-status-17"}]},{"section":"-strong-read-operations-strong--9","subsections":[{"section":"watch-list-all-namespaces-15"},{"section":"watch-list-14"},{"section":"watch-13"},{"section":"list-all-namespaces-12"},{"section":"list-11"},{"section":"read-10"}]},{"section":"-strong-write-operations-strong--3","subsections":[{"section":"delete-collection-8"},{"section":"delete-7"},{"section":"patch-6"},{"section":"replace-5"},{"section":"create-4"}]}]},{"section":"cronjob-v2alpha1","subsections":[{"section":"-strong-status-operations-strong-","subsections":[{"section":"replace-status"},{"section":"read-status"},{"section":"patch-status"}]},{"section":"-strong-read-operations-strong-","subsections":[{"section":"watch-list-all-namespaces"},{"section":"watch-list"},{"section":"watch"},{"section":"list-all-namespaces"},{"section":"list"},{"section":"read-2"}]},{"section":"-strong-write-operations-strong-","subsections":[{"section":"delete-collection"},{"section":"delete-1"},{"section":"patch"},{"section":"replace"},{"section":"create"}]}]},{"section":"container-v1","subsections":[]},{"section":"-strong-workloads-strong-","subsections":[]},{"section":"-strong-api-overview-strong-","subsections":[{"section":"resource-operations"},{"section":"resource-objects"},{"section":"resource-categories"}]}],"flatToc":["scale-v1beta1","jobcondition-v2alpha1","jobcondition-v1beta1","replace-status-561","read-status-560","patch-status-559","-strong-status-operations-strong--558","watch-list-all-namespaces-557","watch-list-556","watch-555","list-all-namespaces-554","list-553","read-552","-strong-read-operations-strong--551","delete-collection-550","delete-549","patch-548","replace-547","create-546","-strong-write-operations-strong--545","job-v2alpha1","replace-status-544","read-status-543","patch-status-542","-strong-status-operations-strong--541","watch-list-all-namespaces-540","watch-list-539","watch-538","list-all-namespaces-537","list-536","read-535","-strong-read-operations-strong--534","delete-collection-533","delete-532","patch-531","replace-530","create-529","-strong-write-operations-strong--528","job-v1beta1","replace-status-527","read-status-526","patch-status-525","-strong-status-operations-strong--524","watch-list-all-namespaces-523","watch-list-522","watch-521","list-all-namespaces-520","list-519","read-518","-strong-read-operations-strong--517","delete-collection-516","delete-515","patch-514","replace-513","create-512","-strong-write-operations-strong--511","horizontalpodautoscaler-v1beta1","event-versioned","-strong-old-api-versions-strong-","vspherevirtualdiskvolumesource-v1","volumemount-v1","userinfo-v1beta1","time-unversioned","tcpsocketaction-v1","subresourcereference-v1beta1","subject-v1alpha1","statusdetails-unversioned","statuscause-unversioned","status-unversioned","serviceport-v1","serveraddressbyclientcidr-unversioned","securitycontext-v1","secretvolumesource-v1","secretkeyselector-v1","scale-v1","selinuxoptions-v1","rollbackconfig-v1beta1","roleref-v1alpha1","resourcerequirements-v1","resourcefieldselector-v1","resourceattributes-v1beta1","replicationcontrollercondition-v1","replicasetcondition-v1beta1","rawextension-runtime","rbdvolumesource-v1","quobytevolumesource-v1","quantity-resource","probe-v1","preconditions-v1","policyrule-v1alpha1","podsecuritycontext-v1","podcondition-v1","photonpersistentdiskvolumesource-v1","persistentvolumeclaimvolumesource-v1","patch-unversioned","ownerreference-v1","objectreference-v1","objectmeta-v1","objectfieldselector-v1","nonresourceattributes-v1beta1","nodesysteminfo-v1","nodedaemonendpoints-v1","nodecondition-v1","nodeaddress-v1","networkpolicyport-v1beta1","networkpolicypeer-v1beta1","networkpolicyingressrule-v1beta1","nfsvolumesource-v1","localobjectreference-v1","loadbalancerstatus-v1","loadbalanceringress-v1","listmeta-unversioned","limitrangeitem-v1","lifecycle-v1","labelselectorrequirement-unversioned","labelselector-unversioned","keytopath-v1","jobtemplatespec-v2alpha1","jobcondition-v1","intorstring-intstr","ingresstls-v1beta1","ingressrule-v1beta1","ingressbackend-v1beta1","info-version","iscsivolumesource-v1","hostpathvolumesource-v1","handler-v1","httpingressrulevalue-v1beta1","httpingresspath-v1beta1","httpheader-v1","httpgetaction-v1","groupversionfordiscovery-unversioned","glusterfsvolumesource-v1","gitrepovolumesource-v1","gcepersistentdiskvolumesource-v1","flockervolumesource-v1","flexvolumesource-v1","fcvolumesource-v1","execaction-v1","eviction-v1beta1","eventsource-v1","envvarsource-v1","envvar-v1","endpointsubset-v1","endpointport-v1","endpointaddress-v1","emptydirvolumesource-v1","downwardapivolumesource-v1","downwardapivolumefile-v1","deploymentcondition-v1beta1","deleteoptions-v1","daemonendpoint-v1","crossversionobjectreference-v1","containerstatewaiting-v1","containerstateterminated-v1","containerstaterunning-v1","containerstate-v1","containerport-v1","containerimage-v1","configmapvolumesource-v1","configmapkeyselector-v1","componentcondition-v1","cindervolumesource-v1","certificatesigningrequestcondition-v1alpha1","cephfsvolumesource-v1","capabilities-v1","cputargetutilization-v1beta1","azurefilevolumesource-v1","azurediskvolumesource-v1","attachedvolume-v1","awselasticblockstorevolumesource-v1","apiversions-unversioned","apiversion-v1beta1","apiresource-unversioned","apigroup-unversioned","-strong-definitions-strong-","watch-list-all-namespaces-510","watch-list-509","watch-508","list-all-namespaces-507","list-506","read-505","-strong-read-operations-strong--504","delete-collection-503","delete-502","patch-501","replace-500","create-499","-strong-write-operations-strong--498","networkpolicy-v1beta1","create-497","-strong-write-operations-strong--496","tokenreview-v1beta1","create-495","-strong-write-operations-strong--494","subjectaccessreview-v1beta1","watch-list-all-namespaces-493","watch-list-492","watch-491","list-all-namespaces-490","list-489","read-488","-strong-read-operations-strong--487","delete-collection-486","delete-485","patch-484","replace-483","create-482","-strong-write-operations-strong--481","serviceaccount-v1","create-480","-strong-write-operations-strong--479","selfsubjectaccessreview-v1beta1","watch-list-all-namespaces-478","watch-list-477","watch-476","list-all-namespaces-475","list-474","read-473","-strong-read-operations-strong--472","delete-collection-471","delete-470","patch-469","replace-468","create-467","-strong-write-operations-strong--466","rolebinding-v1alpha1","watch-list-all-namespaces-465","watch-list-464","watch-463","list-all-namespaces-462","list-461","read-460","-strong-read-operations-strong--459","delete-collection-458","delete-457","patch-456","replace-455","create-454","-strong-write-operations-strong--453","role-v1alpha1","replace-status-452","read-status-451","patch-status-450","-strong-status-operations-strong--449","watch-list-all-namespaces-448","watch-list-447","watch-446","list-all-namespaces-445","list-444","read-443","-strong-read-operations-strong--442","delete-collection-441","delete-440","patch-439","replace-438","create-437","-strong-write-operations-strong--436","resourcequota-v1","replace-status-435","read-status-434","patch-status-433","-strong-status-operations-strong--432","watch-list-431","watch-430","list-429","read-428","-strong-read-operations-strong--427","delete-collection-426","delete-425","patch-424","replace-423","create-422","-strong-write-operations-strong--421","persistentvolume-v1","replace-proxy-path-420","replace-proxy-419","replace-connect-proxy-path-418","replace-connect-proxy-417","head-connect-proxy-path-416","head-connect-proxy-415","get-proxy-path-414","get-proxy-413","get-connect-proxy-path-412","get-connect-proxy-411","delete-proxy-path-410","delete-proxy-409","delete-connect-proxy-path-408","delete-connect-proxy-407","create-proxy-path-406","create-proxy-405","create-connect-proxy-path-404","create-connect-proxy-403","-strong-proxy-operations-strong--402","replace-status-401","read-status-400","patch-status-399","-strong-status-operations-strong--398","watch-list-397","watch-396","list-395","read-394","-strong-read-operations-strong--393","delete-collection-392","delete-391","patch-390","replace-389","create-388","-strong-write-operations-strong--387","node-v1","replace-status-386","read-status-385","patch-status-384","-strong-status-operations-strong--383","watch-list-382","watch-381","list-380","read-379","-strong-read-operations-strong--378","delete-collection-377","delete-376","patch-375","replace-374","create-373","-strong-write-operations-strong--372","namespace-v1","create-371","-strong-write-operations-strong--370","localsubjectaccessreview-v1beta1","list-369","read-368","-strong-read-operations-strong--367","componentstatus-v1","watch-list-366","watch-365","list-364","read-363","-strong-read-operations-strong--362","delete-collection-361","delete-360","patch-359","replace-358","create-357","-strong-write-operations-strong--356","clusterrolebinding-v1alpha1","watch-list-355","watch-354","list-353","read-352","-strong-read-operations-strong--351","delete-collection-350","delete-349","patch-348","replace-347","create-346","-strong-write-operations-strong--345","clusterrole-v1alpha1","replace-status-344","-strong-status-operations-strong--343","watch-list-342","watch-341","list-340","read-339","-strong-read-operations-strong--338","delete-collection-337","delete-336","patch-335","replace-334","create-333","-strong-write-operations-strong--332","certificatesigningrequest-v1alpha1","create-331","-strong-write-operations-strong--330","binding-v1","-strong-cluster-strong-","watch-list-329","watch-328","list-327","read-326","-strong-read-operations-strong--325","delete-collection-324","delete-323","patch-322","replace-321","create-320","-strong-write-operations-strong--319","thirdpartyresource-v1beta1","replace-status-318","read-status-317","patch-status-316","-strong-status-operations-strong--315","watch-list-all-namespaces-314","watch-list-313","watch-312","list-all-namespaces-311","list-310","read-309","-strong-read-operations-strong--308","delete-collection-307","delete-306","patch-305","replace-304","create-303","-strong-write-operations-strong--302","poddisruptionbudget-v1beta1","watch-list-all-namespaces-301","watch-list-300","watch-299","list-all-namespaces-298","list-297","read-296","-strong-read-operations-strong--295","delete-collection-294","delete-293","patch-292","replace-291","create-290","-strong-write-operations-strong--289","podtemplate-v1","replace-status-288","read-status-287","patch-status-286","-strong-status-operations-strong--285","watch-list-all-namespaces-284","watch-list-283","watch-282","list-all-namespaces-281","list-280","read-279","-strong-read-operations-strong--278","delete-collection-277","delete-276","patch-275","replace-274","create-273","-strong-write-operations-strong--272","horizontalpodautoscaler-v1","watch-list-all-namespaces-271","watch-list-270","watch-269","list-all-namespaces-268","list-267","read-266","-strong-read-operations-strong--265","delete-collection-264","delete-263","patch-262","replace-261","create-260","-strong-write-operations-strong--259","limitrange-v1","watch-list-all-namespaces-258","watch-list-257","watch-256","list-all-namespaces-255","list-254","read-253","-strong-read-operations-strong--252","delete-collection-251","delete-250","patch-249","replace-248","create-247","-strong-write-operations-strong--246","event-v1","-strong-metadata-strong-","volume-v1","watch-list-245","watch-244","list-243","read-242","-strong-read-operations-strong--241","delete-collection-240","delete-239","patch-238","replace-237","create-236","-strong-write-operations-strong--235","storageclass-v1beta1","replace-status-234","read-status-233","patch-status-232","-strong-status-operations-strong--231","watch-list-all-namespaces-230","watch-list-229","watch-228","list-all-namespaces-227","list-226","read-225","-strong-read-operations-strong--224","delete-collection-223","delete-222","patch-221","replace-220","create-219","-strong-write-operations-strong--218","persistentvolumeclaim-v1","watch-list-all-namespaces-217","watch-list-216","watch-215","list-all-namespaces-214","list-213","read-212","-strong-read-operations-strong--211","delete-collection-210","delete-209","patch-208","replace-207","create-206","-strong-write-operations-strong--205","secret-v1","watch-list-all-namespaces-204","watch-list-203","watch-202","list-all-namespaces-201","list-200","read-199","-strong-read-operations-strong--198","delete-collection-197","delete-196","patch-195","replace-194","create-193","-strong-write-operations-strong--192","configmap-v1","-strong-config-storage-strong-","replace-proxy-path-191","replace-proxy-190","replace-connect-proxy-path-189","replace-connect-proxy-188","head-connect-proxy-path-187","head-connect-proxy-186","get-proxy-path-185","get-proxy-184","get-connect-proxy-path-183","get-connect-proxy-182","delete-proxy-path-181","delete-proxy-180","delete-connect-proxy-path-179","delete-connect-proxy-178","create-proxy-path-177","create-proxy-176","create-connect-proxy-path-175","create-connect-proxy-174","-strong-proxy-operations-strong--173","replace-status-172","read-status-171","patch-status-170","-strong-status-operations-strong--169","watch-list-all-namespaces-168","watch-list-167","watch-166","list-all-namespaces-165","list-164","read-163","-strong-read-operations-strong--162","delete-161","patch-160","replace-159","create-158","-strong-write-operations-strong--157","service-v1","replace-status-156","read-status-155","patch-status-154","-strong-status-operations-strong--153","watch-list-all-namespaces-152","watch-list-151","watch-150","list-all-namespaces-149","list-148","read-147","-strong-read-operations-strong--146","delete-collection-145","delete-144","patch-143","replace-142","create-141","-strong-write-operations-strong--140","ingress-v1beta1","watch-list-all-namespaces-139","watch-list-138","watch-137","list-all-namespaces-136","list-135","read-134","-strong-read-operations-strong--133","delete-collection-132","delete-131","patch-130","replace-129","create-128","-strong-write-operations-strong--127","endpoints-v1","-strong-discovery-load-balancing-strong-","replace-status-126","read-status-125","patch-status-124","-strong-status-operations-strong--123","watch-list-all-namespaces-122","watch-list-121","watch-120","list-all-namespaces-119","list-118","read-117","-strong-read-operations-strong--116","delete-collection-115","delete-114","patch-113","replace-112","create-111","-strong-write-operations-strong--110","statefulset-v1beta1","replace-status-109","read-status-108","patch-status-107","-strong-status-operations-strong--106","watch-list-all-namespaces-105","watch-list-104","watch-103","list-all-namespaces-102","list-101","read-100","-strong-read-operations-strong--99","delete-collection-98","delete-97","patch-96","replace-95","create-94","-strong-write-operations-strong--93","replicationcontroller-v1","patch-scale-92","replace-scale-91","read-scale-90","-strong-misc-operations-strong--89","replace-status-88","read-status-87","patch-status-86","-strong-status-operations-strong--85","watch-list-all-namespaces-84","watch-list-83","watch-82","list-all-namespaces-81","list-80","read-79","-strong-read-operations-strong--78","delete-collection-77","delete-76","patch-75","replace-74","create-73","-strong-write-operations-strong--72","replicaset-v1beta1","read-log","-strong-misc-operations-strong--71","replace-proxy-path","replace-proxy","replace-connect-proxy-path","replace-connect-proxy","head-connect-proxy-path","head-connect-proxy","get-proxy-path","get-proxy","get-connect-proxy-path","get-connect-proxy","get-connect-portforward","delete-proxy-path","delete-proxy","delete-connect-proxy-path","delete-connect-proxy","create-proxy-path","create-proxy","create-connect-proxy-path","create-connect-proxy","create-connect-portforward","-strong-proxy-operations-strong-","replace-status-70","read-status-69","patch-status-68","-strong-status-operations-strong--67","watch-list-all-namespaces-66","watch-list-65","watch-64","list-all-namespaces-63","list-62","read-61","-strong-read-operations-strong--60","delete-collection-59","delete-58","patch-57","replace-56","create-55","-strong-write-operations-strong--54","pod-v1","replace-status-53","read-status-52","patch-status-51","-strong-status-operations-strong--50","watch-list-all-namespaces-49","watch-list-48","watch-47","list-all-namespaces-46","list-45","read-44","-strong-read-operations-strong--43","delete-collection-42","delete-41","patch-40","replace-39","create-38","-strong-write-operations-strong--37","job-v1","rollback","patch-scale","replace-scale","read-scale","-strong-misc-operations-strong-","replace-status-36","read-status-35","patch-status-34","-strong-status-operations-strong--33","watch-list-all-namespaces-32","watch-list-31","watch-30","list-all-namespaces-29","list-28","read-27","-strong-read-operations-strong--26","delete-collection-25","delete-24","patch-23","replace-22","create-21","-strong-write-operations-strong--20","deployment-v1beta1","replace-status-19","read-status-18","patch-status-17","-strong-status-operations-strong--16","watch-list-all-namespaces-15","watch-list-14","watch-13","list-all-namespaces-12","list-11","read-10","-strong-read-operations-strong--9","delete-collection-8","delete-7","patch-6","replace-5","create-4","-strong-write-operations-strong--3","daemonset-v1beta1","replace-status","read-status","patch-status","-strong-status-operations-strong-","watch-list-all-namespaces","watch-list","watch","list-all-namespaces","list","read-2","-strong-read-operations-strong-","delete-collection","delete-1","patch","replace","create","-strong-write-operations-strong-","cronjob-v2alpha1","container-v1","-strong-workloads-strong-","resource-operations","resource-objects","resource-categories","-strong-api-overview-strong-"]}})();
\ No newline at end of file

From 0e8bb958a5e83f78724ffef1a0164f10a362ca93 Mon Sep 17 00:00:00 2001
From: Phillip Wittrock 
Date: Thu, 19 Jan 2017 20:30:41 -0800
Subject: [PATCH 38/44] Delete unused reference generated files

---
 docs/api-reference/v1.5/documents/_cluster.md |    5 -
 docs/api-reference/v1.5/documents/_config.md  |   11 -
 .../v1.5/documents/_definitions.md            |    3 -
 ..._generated_apigroup_unversioned_concept.md |   46 -
 ...nerated_apigroup_unversioned_definition.md |   22 -
 ...erated_apigrouplist_unversioned_concept.md |   32 -
 ...ted_apigrouplist_unversioned_definition.md |   18 -
 ...nerated_apiresource_unversioned_concept.md |   44 -
 ...ated_apiresource_unversioned_definition.md |   19 -
 ...ted_apiresourcelist_unversioned_concept.md |   33 -
 ..._apiresourcelist_unversioned_definition.md |   19 -
 .../_generated_apiversion_v1beta1_concept.md  |   31 -
 ...generated_apiversion_v1beta1_definition.md |   17 -
 ...nerated_apiversions_unversioned_concept.md |   33 -
 ...ated_apiversions_unversioned_definition.md |   19 -
 .../_generated_attachedvolume_v1_concept.md   |   32 -
 ..._generated_attachedvolume_v1_definition.md |   18 -
 ...lasticblockstorevolumesource_v1_concept.md |   36 -
 ...ticblockstorevolumesource_v1_definition.md |   22 -
 ...erated_azurediskvolumesource_v1_concept.md |   35 -
 ...ted_azurediskvolumesource_v1_definition.md |   21 -
 ...erated_azurefilevolumesource_v1_concept.md |   33 -
 ...ted_azurefilevolumesource_v1_definition.md |   19 -
 .../_generated_binding_v1_concept.md          |  104 -
 .../_generated_binding_v1_definition.md       |   19 -
 .../_generated_capabilities_v1_concept.md     |   32 -
 .../_generated_capabilities_v1_definition.md  |   18 -
 ...generated_cephfsvolumesource_v1_concept.md |   36 -
 ...erated_cephfsvolumesource_v1_definition.md |   22 -
 ...tificatesigningrequest_v1alpha1_concept.md |  590 -----
 ...icatesigningrequest_v1alpha1_definition.md |   21 -
 ...igningrequestcondition_v1alpha1_concept.md |   34 -
 ...ingrequestcondition_v1alpha1_definition.md |   20 -
 ...catesigningrequestlist_v1alpha1_concept.md |   99 -
 ...esigningrequestlist_v1alpha1_definition.md |   19 -
 ...catesigningrequestspec_v1alpha1_concept.md |   34 -
 ...esigningrequestspec_v1alpha1_definition.md |   20 -
 ...tesigningrequeststatus_v1alpha1_concept.md |  103 -
 ...igningrequeststatus_v1alpha1_definition.md |   18 -
 ...generated_cindervolumesource_v1_concept.md |   33 -
 ...erated_cindervolumesource_v1_definition.md |   19 -
 ..._generated_clusterrole_v1alpha1_concept.md |  565 ----
 ...nerated_clusterrole_v1alpha1_definition.md |   20 -
 ...ted_clusterrolebinding_v1alpha1_concept.md |  627 -----
 ..._clusterrolebinding_v1alpha1_definition.md |   21 -
 ...clusterrolebindinglist_v1alpha1_concept.md |   33 -
 ...sterrolebindinglist_v1alpha1_definition.md |   19 -
 ...erated_clusterrolelist_v1alpha1_concept.md |   99 -
 ...ted_clusterrolelist_v1alpha1_definition.md |   19 -
 ...generated_componentcondition_v1_concept.md |   34 -
 ...erated_componentcondition_v1_definition.md |   20 -
 .../_generated_componentstatus_v1_concept.md  |  172 --
 ...generated_componentstatus_v1_definition.md |   20 -
 ...enerated_componentstatuslist_v1_concept.md |   33 -
 ...rated_componentstatuslist_v1_definition.md |   19 -
 .../_generated_configmap_v1_concept.md        |  709 -----
 .../_generated_configmap_v1_definition.md     |   20 -
 ...nerated_configmapkeyselector_v1_concept.md |   32 -
 ...ated_configmapkeyselector_v1_definition.md |   18 -
 .../_generated_configmaplist_v1_concept.md    |  104 -
 .../_generated_configmaplist_v1_definition.md |   19 -
 ...erated_configmapvolumesource_v1_concept.md |   35 -
 ...ted_configmapvolumesource_v1_definition.md |   21 -
 .../_generated_container_v1_concept.md        |   84 -
 .../_generated_container_v1_definition.md     |   34 -
 .../_generated_containerimage_v1_concept.md   |   32 -
 ..._generated_containerimage_v1_definition.md |   18 -
 .../_generated_containerport_v1_concept.md    |   35 -
 .../_generated_containerport_v1_definition.md |   21 -
 .../_generated_containerstate_v1_concept.md   |   33 -
 ..._generated_containerstate_v1_definition.md |   19 -
 ...erated_containerstaterunning_v1_concept.md |   31 -
 ...ted_containerstaterunning_v1_definition.md |   17 -
 ...ted_containerstateterminated_v1_concept.md |   37 -
 ..._containerstateterminated_v1_definition.md |   23 -
 ...erated_containerstatewaiting_v1_concept.md |   32 -
 ...ted_containerstatewaiting_v1_definition.md |   18 -
 .../_generated_containerstatus_v1_concept.md  |   38 -
 ...generated_containerstatus_v1_definition.md |   24 -
 ...ed_cputargetutilization_v1beta1_concept.md |   31 -
 ...cputargetutilization_v1beta1_definition.md |   17 -
 .../_generated_cronjob_v2alpha1_concept.md    | 1000 -------
 .../_generated_cronjob_v2alpha1_definition.md |   21 -
 ..._generated_cronjoblist_v2alpha1_concept.md |   33 -
 ...nerated_cronjoblist_v2alpha1_definition.md |   19 -
 ..._generated_cronjobspec_v2alpha1_concept.md |   35 -
 ...nerated_cronjobspec_v2alpha1_definition.md |   21 -
 ...enerated_cronjobstatus_v2alpha1_concept.md |   32 -
 ...rated_cronjobstatus_v2alpha1_definition.md |   18 -
 ..._crossversionobjectreference_v1_concept.md |   33 -
 ...ossversionobjectreference_v1_definition.md |   19 -
 .../_generated_daemonendpoint_v1_concept.md   |   31 -
 ..._generated_daemonendpoint_v1_definition.md |   17 -
 .../_generated_daemonset_v1beta1_concept.md   | 1110 --------
 ..._generated_daemonset_v1beta1_definition.md |   21 -
 ...generated_daemonsetlist_v1beta1_concept.md |  104 -
 ...erated_daemonsetlist_v1beta1_definition.md |   19 -
 ...generated_daemonsetspec_v1beta1_concept.md |   32 -
 ...erated_daemonsetspec_v1beta1_definition.md |   18 -
 ...nerated_daemonsetstatus_v1beta1_concept.md |   34 -
 ...ated_daemonsetstatus_v1beta1_definition.md |   20 -
 .../_generated_deleteoptions_v1_concept.md    |   35 -
 .../_generated_deleteoptions_v1_definition.md |   21 -
 .../_generated_deployment_v1beta1_concept.md  | 2218 ----------------
 ...generated_deployment_v1beta1_definition.md |   21 -
 ...ted_deploymentcondition_v1beta1_concept.md |   36 -
 ..._deploymentcondition_v1beta1_definition.md |   22 -
 ...enerated_deploymentlist_v1beta1_concept.md |   33 -
 ...rated_deploymentlist_v1beta1_definition.md |   19 -
 ...ated_deploymentrollback_v1beta1_concept.md |   34 -
 ...d_deploymentrollback_v1beta1_definition.md |   20 -
 ...enerated_deploymentspec_v1beta1_concept.md |   39 -
 ...rated_deploymentspec_v1beta1_definition.md |   25 -
 ...erated_deploymentstatus_v1beta1_concept.md |   36 -
 ...ted_deploymentstatus_v1beta1_definition.md |   22 -
 ...ated_deploymentstrategy_v1beta1_concept.md |   32 -
 ...d_deploymentstrategy_v1beta1_definition.md |   18 -
 ...erated_downwardapivolumefile_v1_concept.md |   34 -
 ...ted_downwardapivolumefile_v1_definition.md |   20 -
 ...ated_downwardapivolumesource_v1_concept.md |   32 -
 ...d_downwardapivolumesource_v1_definition.md |   18 -
 ...nerated_emptydirvolumesource_v1_concept.md |   31 -
 ...ated_emptydirvolumesource_v1_definition.md |   17 -
 .../_generated_endpointaddress_v1_concept.md  |   34 -
 ...generated_endpointaddress_v1_definition.md |   20 -
 .../_generated_endpointport_v1_concept.md     |   33 -
 .../_generated_endpointport_v1_definition.md  |   19 -
 .../_generated_endpoints_v1_concept.md        |  786 ------
 .../_generated_endpoints_v1_definition.md     |   31 -
 .../_generated_endpointslist_v1_concept.md    |   33 -
 .../_generated_endpointslist_v1_definition.md |   19 -
 .../_generated_endpointsubset_v1_concept.md   |   40 -
 ..._generated_endpointsubset_v1_definition.md |   26 -
 .../documents/_generated_envvar_v1_concept.md |   33 -
 .../_generated_envvar_v1_definition.md        |   19 -
 .../_generated_envvarsource_v1_concept.md     |   34 -
 .../_generated_envvarsource_v1_definition.md  |   20 -
 .../documents/_generated_event_v1_concept.md  |  716 -----
 .../_generated_event_v1_definition.md         |   27 -
 .../_generated_event_versioned_concept.md     |   31 -
 .../_generated_event_versioned_definition.md  |   17 -
 .../_generated_eventlist_v1_concept.md        |  104 -
 .../_generated_eventlist_v1_definition.md     |   19 -
 .../_generated_eventsource_v1_concept.md      |   32 -
 .../_generated_eventsource_v1_definition.md   |   18 -
 .../_generated_eviction_v1beta1_concept.md    |   33 -
 .../_generated_eviction_v1beta1_definition.md |   19 -
 .../_generated_execaction_v1_concept.md       |   31 -
 .../_generated_execaction_v1_definition.md    |   17 -
 .../_generated_fcvolumesource_v1_concept.md   |   34 -
 ..._generated_fcvolumesource_v1_definition.md |   20 -
 .../_generated_flexvolumesource_v1_concept.md |   35 -
 ...enerated_flexvolumesource_v1_definition.md |   21 -
 ...enerated_flockervolumesource_v1_concept.md |   32 -
 ...rated_flockervolumesource_v1_definition.md |   18 -
 ...cepersistentdiskvolumesource_v1_concept.md |   36 -
 ...ersistentdiskvolumesource_v1_definition.md |   22 -
 ...enerated_gitrepovolumesource_v1_concept.md |   33 -
 ...rated_gitrepovolumesource_v1_definition.md |   19 -
 ...erated_glusterfsvolumesource_v1_concept.md |   33 -
 ...ted_glusterfsvolumesource_v1_definition.md |   19 -
 ...versionfordiscovery_unversioned_concept.md |   32 -
 ...sionfordiscovery_unversioned_definition.md |   18 -
 .../_generated_handler_v1_concept.md          |   33 -
 .../_generated_handler_v1_definition.md       |   19 -
 ...ated_horizontalpodautoscaler_v1_concept.md |  735 ------
 ...d_horizontalpodautoscaler_v1_definition.md |   21 -
 ...horizontalpodautoscaler_v1beta1_concept.md |  735 ------
 ...izontalpodautoscaler_v1beta1_definition.md |   21 -
 ..._horizontalpodautoscalerlist_v1_concept.md |  104 -
 ...rizontalpodautoscalerlist_v1_definition.md |   19 -
 ...zontalpodautoscalerlist_v1beta1_concept.md |  104 -
 ...talpodautoscalerlist_v1beta1_definition.md |   19 -
 ..._horizontalpodautoscalerspec_v1_concept.md |   34 -
 ...rizontalpodautoscalerspec_v1_definition.md |   20 -
 ...zontalpodautoscalerspec_v1beta1_concept.md |   34 -
 ...talpodautoscalerspec_v1beta1_definition.md |   20 -
 ...orizontalpodautoscalerstatus_v1_concept.md |  241 --
 ...zontalpodautoscalerstatus_v1_definition.md |   21 -
 ...ntalpodautoscalerstatus_v1beta1_concept.md |  241 --
 ...lpodautoscalerstatus_v1beta1_definition.md |   21 -
 ...nerated_hostpathvolumesource_v1_concept.md |   31 -
 ...ated_hostpathvolumesource_v1_definition.md |   17 -
 .../_generated_httpgetaction_v1_concept.md    |   35 -
 .../_generated_httpgetaction_v1_definition.md |   21 -
 .../_generated_httpheader_v1_concept.md       |   32 -
 .../_generated_httpheader_v1_definition.md    |   18 -
 ...nerated_httpingresspath_v1beta1_concept.md |   32 -
 ...ated_httpingresspath_v1beta1_definition.md |   18 -
 ...ed_httpingressrulevalue_v1beta1_concept.md |   31 -
 ...httpingressrulevalue_v1beta1_definition.md |   17 -
 .../_generated_info_version_concept.md        |   38 -
 .../_generated_info_version_definition.md     |   24 -
 .../_generated_ingress_v1beta1_concept.md     |  730 -----
 .../_generated_ingress_v1beta1_definition.md  |   21 -
 ...enerated_ingressbackend_v1beta1_concept.md |   32 -
 ...rated_ingressbackend_v1beta1_definition.md |   18 -
 .../_generated_ingresslist_v1beta1_concept.md |  104 -
 ...enerated_ingresslist_v1beta1_definition.md |   19 -
 .../_generated_ingressrule_v1beta1_concept.md |   32 -
 ...enerated_ingressrule_v1beta1_definition.md |   18 -
 .../_generated_ingressspec_v1beta1_concept.md |   33 -
 ...enerated_ingressspec_v1beta1_definition.md |   19 -
 ...generated_ingressstatus_v1beta1_concept.md |  237 --
 ...erated_ingressstatus_v1beta1_definition.md |   17 -
 .../_generated_ingresstls_v1beta1_concept.md  |   32 -
 ...generated_ingresstls_v1beta1_definition.md |   18 -
 .../_generated_intorstring_intstr_concept.md  |   30 -
 ...generated_intorstring_intstr_definition.md |   16 -
 ..._generated_iscsivolumesource_v1_concept.md |   36 -
 ...nerated_iscsivolumesource_v1_definition.md |   22 -
 .../documents/_generated_job_v1_concept.md    | 1304 ---------
 .../documents/_generated_job_v1_definition.md |   21 -
 .../_generated_job_v1beta1_concept.md         | 1190 ---------
 .../_generated_job_v1beta1_definition.md      |   21 -
 .../_generated_job_v2alpha1_concept.md        | 1190 ---------
 .../_generated_job_v2alpha1_definition.md     |   21 -
 .../_generated_jobcondition_v1_concept.md     |   36 -
 .../_generated_jobcondition_v1_definition.md  |   22 -
 ..._generated_jobcondition_v1beta1_concept.md |   36 -
 ...nerated_jobcondition_v1beta1_definition.md |   22 -
 ...generated_jobcondition_v2alpha1_concept.md |   36 -
 ...erated_jobcondition_v2alpha1_definition.md |   22 -
 .../_generated_joblist_v1_concept.md          |   33 -
 .../_generated_joblist_v1_definition.md       |   19 -
 .../_generated_joblist_v1beta1_concept.md     |  104 -
 .../_generated_joblist_v1beta1_definition.md  |   19 -
 .../_generated_joblist_v2alpha1_concept.md    |  104 -
 .../_generated_joblist_v2alpha1_definition.md |   19 -
 .../_generated_jobspec_v1_concept.md          |   36 -
 .../_generated_jobspec_v1_definition.md       |   22 -
 .../_generated_jobspec_v1beta1_concept.md     |   36 -
 .../_generated_jobspec_v1beta1_definition.md  |   22 -
 .../_generated_jobspec_v2alpha1_concept.md    |   36 -
 .../_generated_jobspec_v2alpha1_definition.md |   22 -
 .../_generated_jobstatus_v1_concept.md        |  242 --
 .../_generated_jobstatus_v1_definition.md     |   22 -
 .../_generated_jobstatus_v1beta1_concept.md   |  242 --
 ..._generated_jobstatus_v1beta1_definition.md |   22 -
 .../_generated_jobstatus_v2alpha1_concept.md  |  242 --
 ...generated_jobstatus_v2alpha1_definition.md |   22 -
 ...erated_jobtemplatespec_v2alpha1_concept.md |   32 -
 ...ted_jobtemplatespec_v2alpha1_definition.md |   18 -
 .../_generated_keytopath_v1_concept.md        |   33 -
 .../_generated_keytopath_v1_definition.md     |   19 -
 ...rated_labelselector_unversioned_concept.md |   32 -
 ...ed_labelselector_unversioned_definition.md |   18 -
 ...selectorrequirement_unversioned_concept.md |   33 -
 ...ectorrequirement_unversioned_definition.md |   19 -
 .../_generated_lifecycle_v1_concept.md        |   32 -
 .../_generated_lifecycle_v1_definition.md     |   18 -
 .../_generated_limitrange_v1_concept.md       |  718 -----
 .../_generated_limitrange_v1_definition.md    |   20 -
 .../_generated_limitrangeitem_v1_concept.md   |   36 -
 ..._generated_limitrangeitem_v1_definition.md |   22 -
 .../_generated_limitrangelist_v1_concept.md   |  104 -
 ..._generated_limitrangelist_v1_definition.md |   19 -
 .../_generated_limitrangespec_v1_concept.md   |   31 -
 ..._generated_limitrangespec_v1_definition.md |   17 -
 ..._generated_listmeta_unversioned_concept.md |   32 -
 ...nerated_listmeta_unversioned_definition.md |   18 -
 ...enerated_loadbalanceringress_v1_concept.md |   32 -
 ...rated_loadbalanceringress_v1_definition.md |   18 -
 ...generated_loadbalancerstatus_v1_concept.md |   31 -
 ...erated_loadbalancerstatus_v1_definition.md |   17 -
 ...nerated_localobjectreference_v1_concept.md |   31 -
 ...ated_localobjectreference_v1_definition.md |   17 -
 ...ocalsubjectaccessreview_v1beta1_concept.md |  105 -
 ...lsubjectaccessreview_v1beta1_definition.md |   20 -
 .../_generated_namespace_v1_concept.md        |  586 ----
 .../_generated_namespace_v1_definition.md     |   21 -
 .../_generated_namespacelist_v1_concept.md    |   99 -
 .../_generated_namespacelist_v1_definition.md |   19 -
 .../_generated_namespacespec_v1_concept.md    |   31 -
 .../_generated_namespacespec_v1_definition.md |   17 -
 .../_generated_namespacestatus_v1_concept.md  |  234 --
 ...generated_namespacestatus_v1_definition.md |   17 -
 ...generated_networkpolicy_v1beta1_concept.md |  719 -----
 ...erated_networkpolicy_v1beta1_definition.md |   20 -
 ...etworkpolicyingressrule_v1beta1_concept.md |   32 -
 ...orkpolicyingressrule_v1beta1_definition.md |   18 -
 ...rated_networkpolicylist_v1beta1_concept.md |  104 -
 ...ed_networkpolicylist_v1beta1_definition.md |   19 -
 ...rated_networkpolicypeer_v1beta1_concept.md |   32 -
 ...ed_networkpolicypeer_v1beta1_definition.md |   18 -
 ...rated_networkpolicyport_v1beta1_concept.md |   32 -
 ...ed_networkpolicyport_v1beta1_definition.md |   18 -
 ...rated_networkpolicyspec_v1beta1_concept.md |   32 -
 ...ed_networkpolicyspec_v1beta1_definition.md |   18 -
 .../_generated_nfsvolumesource_v1_concept.md  |   33 -
 ...generated_nfsvolumesource_v1_definition.md |   19 -
 .../documents/_generated_node_v1_concept.md   | 1670 ------------
 .../_generated_node_v1_definition.md          |   21 -
 .../_generated_nodeaddress_v1_concept.md      |   32 -
 .../_generated_nodeaddress_v1_definition.md   |   18 -
 .../_generated_nodecondition_v1_concept.md    |   36 -
 .../_generated_nodecondition_v1_definition.md |   22 -
 ...enerated_nodedaemonendpoints_v1_concept.md |   31 -
 ...rated_nodedaemonendpoints_v1_definition.md |   17 -
 .../_generated_nodelist_v1_concept.md         |   99 -
 .../_generated_nodelist_v1_definition.md      |   19 -
 .../_generated_nodespec_v1_concept.md         |   34 -
 .../_generated_nodespec_v1_definition.md      |   20 -
 .../_generated_nodestatus_v1_concept.md       |  243 --
 .../_generated_nodestatus_v1_definition.md    |   26 -
 .../_generated_nodesysteminfo_v1_concept.md   |   40 -
 ..._generated_nodesysteminfo_v1_definition.md |   26 -
 ...d_nonresourceattributes_v1beta1_concept.md |   32 -
 ...onresourceattributes_v1beta1_definition.md |   18 -
 ...enerated_objectfieldselector_v1_concept.md |   32 -
 ...rated_objectfieldselector_v1_definition.md |   18 -
 .../_generated_objectmeta_v1_concept.md       |   45 -
 .../_generated_objectmeta_v1_definition.md    |   31 -
 .../_generated_objectreference_v1_concept.md  |   37 -
 ...generated_objectreference_v1_definition.md |   23 -
 .../_generated_ownerreference_v1_concept.md   |   35 -
 ..._generated_ownerreference_v1_definition.md |   21 -
 .../_generated_patch_unversioned_concept.md   |   29 -
 ..._generated_patch_unversioned_definition.md |   15 -
 .../_generated_persistentvolume_v1_concept.md |  867 ------
 ...enerated_persistentvolume_v1_definition.md |   21 -
 ...erated_persistentvolumeclaim_v1_concept.md |  934 -------
 ...ted_persistentvolumeclaim_v1_definition.md |   21 -
 ...ed_persistentvolumeclaimlist_v1_concept.md |  104 -
 ...persistentvolumeclaimlist_v1_definition.md |   19 -
 ...ed_persistentvolumeclaimspec_v1_concept.md |   34 -
 ...persistentvolumeclaimspec_v1_definition.md |   20 -
 ..._persistentvolumeclaimstatus_v1_concept.md |   33 -
 ...rsistentvolumeclaimstatus_v1_definition.md |   19 -
 ...stentvolumeclaimvolumesource_v1_concept.md |   32 -
 ...ntvolumeclaimvolumesource_v1_definition.md |   18 -
 ...nerated_persistentvolumelist_v1_concept.md |   33 -
 ...ated_persistentvolumelist_v1_definition.md |   19 -
 ...nerated_persistentvolumespec_v1_concept.md |   51 -
 ...ated_persistentvolumespec_v1_definition.md |   37 -
 ...rated_persistentvolumestatus_v1_concept.md |   33 -
 ...ed_persistentvolumestatus_v1_definition.md |   19 -
 ...onpersistentdiskvolumesource_v1_concept.md |   32 -
 ...ersistentdiskvolumesource_v1_definition.md |   18 -
 .../documents/_generated_pod_v1_concept.md    | 2128 ---------------
 .../documents/_generated_pod_v1_definition.md |   21 -
 .../_generated_podcondition_v1_concept.md     |   36 -
 .../_generated_podcondition_v1_definition.md  |   22 -
 ...ted_poddisruptionbudget_v1beta1_concept.md |  734 ------
 ..._poddisruptionbudget_v1beta1_definition.md |   21 -
 ...poddisruptionbudgetlist_v1beta1_concept.md |  104 -
 ...disruptionbudgetlist_v1beta1_definition.md |   19 -
 ...poddisruptionbudgetspec_v1beta1_concept.md |   32 -
 ...disruptionbudgetspec_v1beta1_definition.md |   18 -
 ...ddisruptionbudgetstatus_v1beta1_concept.md |  242 --
 ...sruptionbudgetstatus_v1beta1_definition.md |   22 -
 .../_generated_podlist_v1_concept.md          |   33 -
 .../_generated_podlist_v1_definition.md       |   19 -
 ...generated_podsecuritycontext_v1_concept.md |   35 -
 ...erated_podsecuritycontext_v1_definition.md |   21 -
 .../_generated_podspec_v1_concept.md          |   47 -
 .../_generated_podspec_v1_definition.md       |   33 -
 .../_generated_podstatus_v1_concept.md        |  244 --
 .../_generated_podstatus_v1_definition.md     |   24 -
 .../_generated_podtemplate_v1_concept.md      |  719 -----
 .../_generated_podtemplate_v1_definition.md   |   20 -
 .../_generated_podtemplatelist_v1_concept.md  |  104 -
 ...generated_podtemplatelist_v1_definition.md |   19 -
 .../_generated_podtemplatespec_v1_concept.md  |   32 -
 ...generated_podtemplatespec_v1_definition.md |   18 -
 .../_generated_policyrule_v1alpha1_concept.md |   36 -
 ...enerated_policyrule_v1alpha1_definition.md |   22 -
 .../_generated_preconditions_v1_concept.md    |   31 -
 .../_generated_preconditions_v1_definition.md |   17 -
 .../documents/_generated_probe_v1_concept.md  |   38 -
 .../_generated_probe_v1_definition.md         |   24 -
 .../_generated_quantity_resource_concept.md   |   30 -
 ..._generated_quantity_resource_definition.md |   16 -
 ...enerated_quobytevolumesource_v1_concept.md |   35 -
 ...rated_quobytevolumesource_v1_definition.md |   21 -
 ..._generated_rawextension_runtime_concept.md |   58 -
 ...nerated_rawextension_runtime_definition.md |   44 -
 .../_generated_rbdvolumesource_v1_concept.md  |   38 -
 ...generated_rbdvolumesource_v1_definition.md |   24 -
 .../_generated_replicaset_v1beta1_concept.md  | 1051 --------
 ...generated_replicaset_v1beta1_definition.md |   21 -
 ...ted_replicasetcondition_v1beta1_concept.md |   35 -
 ..._replicasetcondition_v1beta1_definition.md |   21 -
 ...enerated_replicasetlist_v1beta1_concept.md |   33 -
 ...rated_replicasetlist_v1beta1_definition.md |   19 -
 ...enerated_replicasetspec_v1beta1_concept.md |   34 -
 ...rated_replicasetspec_v1beta1_definition.md |   20 -
 ...erated_replicasetstatus_v1beta1_concept.md |  242 --
 ...ted_replicasetstatus_v1beta1_definition.md |   22 -
 ...erated_replicationcontroller_v1_concept.md |  784 ------
 ...ted_replicationcontroller_v1_definition.md |   21 -
 ...plicationcontrollercondition_v1_concept.md |   35 -
 ...cationcontrollercondition_v1_definition.md |   21 -
 ...ed_replicationcontrollerlist_v1_concept.md |  104 -
 ...replicationcontrollerlist_v1_definition.md |   19 -
 ...ed_replicationcontrollerspec_v1_concept.md |   34 -
 ...replicationcontrollerspec_v1_definition.md |   20 -
 ..._replicationcontrollerstatus_v1_concept.md |  242 --
 ...plicationcontrollerstatus_v1_definition.md |   22 -
 ...ated_resourceattributes_v1beta1_concept.md |   37 -
 ...d_resourceattributes_v1beta1_definition.md |   23 -
 ...erated_resourcefieldselector_v1_concept.md |   33 -
 ...ted_resourcefieldselector_v1_definition.md |   19 -
 .../_generated_resourcequota_v1_concept.md    |  931 -------
 .../_generated_resourcequota_v1_definition.md |   21 -
 ..._generated_resourcequotalist_v1_concept.md |  104 -
 ...nerated_resourcequotalist_v1_definition.md |   19 -
 ..._generated_resourcequotaspec_v1_concept.md |   32 -
 ...nerated_resourcequotaspec_v1_definition.md |   18 -
 ...enerated_resourcequotastatus_v1_concept.md |   32 -
 ...rated_resourcequotastatus_v1_definition.md |   18 -
 ...nerated_resourcerequirements_v1_concept.md |   32 -
 ...ated_resourcerequirements_v1_definition.md |   18 -
 .../_generated_role_v1alpha1_concept.md       |  773 ------
 .../_generated_role_v1alpha1_definition.md    |   20 -
 ..._generated_rolebinding_v1alpha1_concept.md |  774 ------
 ...nerated_rolebinding_v1alpha1_definition.md |   21 -
 ...erated_rolebindinglist_v1alpha1_concept.md |   33 -
 ...ted_rolebindinglist_v1alpha1_definition.md |   19 -
 .../_generated_rolelist_v1alpha1_concept.md   |   33 -
 ..._generated_rolelist_v1alpha1_definition.md |   19 -
 .../_generated_roleref_v1alpha1_concept.md    |   33 -
 .../_generated_roleref_v1alpha1_definition.md |   19 -
 ...enerated_rollbackconfig_v1beta1_concept.md |   31 -
 ...rated_rollbackconfig_v1beta1_definition.md |   17 -
 ...rollingupdatedeployment_v1beta1_concept.md |   32 -
 ...lingupdatedeployment_v1beta1_definition.md |   18 -
 .../documents/_generated_scale_v1_concept.md  |  254 --
 .../_generated_scale_v1_definition.md         |   20 -
 .../_generated_scale_v1beta1_concept.md       |   54 -
 .../_generated_scale_v1beta1_definition.md    |   20 -
 .../_generated_scalespec_v1_concept.md        |   31 -
 .../_generated_scalespec_v1_definition.md     |   17 -
 .../_generated_scalespec_v1beta1_concept.md   |   31 -
 ..._generated_scalespec_v1beta1_definition.md |   17 -
 .../_generated_scalestatus_v1_concept.md      |   32 -
 .../_generated_scalestatus_v1_definition.md   |   18 -
 .../_generated_scalestatus_v1beta1_concept.md |   33 -
 ...enerated_scalestatus_v1beta1_definition.md |   19 -
 .../documents/_generated_secret_v1_concept.md |  777 ------
 .../_generated_secret_v1_definition.md        |   22 -
 ..._generated_secretkeyselector_v1_concept.md |   32 -
 ...nerated_secretkeyselector_v1_definition.md |   18 -
 .../_generated_secretlist_v1_concept.md       |   33 -
 .../_generated_secretlist_v1_definition.md    |   19 -
 ...generated_secretvolumesource_v1_concept.md |   35 -
 ...erated_secretvolumesource_v1_definition.md |   21 -
 .../_generated_securitycontext_v1_concept.md  |   36 -
 ...generated_securitycontext_v1_definition.md |   22 -
 ...selfsubjectaccessreview_v1beta1_concept.md |  110 -
 ...fsubjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   32 -
 ...jectaccessreviewspec_v1beta1_definition.md |   18 -
 .../_generated_selinuxoptions_v1_concept.md   |   34 -
 ..._generated_selinuxoptions_v1_definition.md |   20 -
 ...addressbyclientcidr_unversioned_concept.md |   32 -
 ...ressbyclientcidr_unversioned_definition.md |   18 -
 .../_generated_service_v1_concept.md          | 2346 -----------------
 .../_generated_service_v1_definition.md       |   21 -
 .../_generated_serviceaccount_v1_concept.md   |  776 ------
 ..._generated_serviceaccount_v1_definition.md |   21 -
 ...generated_serviceaccountlist_v1_concept.md |   33 -
 ...erated_serviceaccountlist_v1_definition.md |   19 -
 .../_generated_servicelist_v1_concept.md      |  104 -
 .../_generated_servicelist_v1_definition.md   |   19 -
 .../_generated_serviceport_v1_concept.md      |   35 -
 .../_generated_serviceport_v1_definition.md   |   21 -
 .../_generated_servicespec_v1_concept.md      |   40 -
 .../_generated_servicespec_v1_definition.md   |   26 -
 .../_generated_servicestatus_v1_concept.md    |   31 -
 .../_generated_servicestatus_v1_definition.md |   17 -
 .../_generated_statefulset_v1beta1_concept.md | 1003 -------
 ...enerated_statefulset_v1beta1_definition.md |   24 -
 ...nerated_statefulsetlist_v1beta1_concept.md |   33 -
 ...ated_statefulsetlist_v1beta1_definition.md |   19 -
 ...nerated_statefulsetspec_v1beta1_concept.md |   35 -
 ...ated_statefulsetspec_v1beta1_definition.md |   21 -
 ...rated_statefulsetstatus_v1beta1_concept.md |   32 -
 ...ed_statefulsetstatus_v1beta1_definition.md |   18 -
 .../_generated_status_unversioned_concept.md  |   37 -
 ...generated_status_unversioned_definition.md |   23 -
 ...nerated_statuscause_unversioned_concept.md |   33 -
 ...ated_statuscause_unversioned_definition.md |   19 -
 ...rated_statusdetails_unversioned_concept.md |   35 -
 ...ed_statusdetails_unversioned_definition.md |   21 -
 ..._generated_storageclass_v1beta1_concept.md |  570 ----
 ...nerated_storageclass_v1beta1_definition.md |   23 -
 ...erated_storageclasslist_v1beta1_concept.md |   99 -
 ...ted_storageclasslist_v1beta1_definition.md |   19 -
 .../_generated_subject_v1alpha1_concept.md    |   34 -
 .../_generated_subject_v1alpha1_definition.md |   20 -
 ...ted_subjectaccessreview_v1beta1_concept.md |  124 -
 ..._subjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   35 -
 ...jectaccessreviewspec_v1beta1_definition.md |   21 -
 ...bjectaccessreviewstatus_v1beta1_concept.md |   33 -
 ...ctaccessreviewstatus_v1beta1_definition.md |   19 -
 ...ed_subresourcereference_v1beta1_concept.md |   34 -
 ...subresourcereference_v1beta1_definition.md |   20 -
 .../_generated_tcpsocketaction_v1_concept.md  |   31 -
 ...generated_tcpsocketaction_v1_definition.md |   17 -
 ...ated_thirdpartyresource_v1beta1_concept.md |  568 ----
 ...d_thirdpartyresource_v1beta1_definition.md |   21 -
 ..._thirdpartyresourcelist_v1beta1_concept.md |   99 -
 ...irdpartyresourcelist_v1beta1_definition.md |   19 -
 .../_generated_time_unversioned_concept.md    |   30 -
 .../_generated_time_unversioned_definition.md |   16 -
 .../_generated_tokenreview_v1beta1_concept.md |  120 -
 ...enerated_tokenreview_v1beta1_definition.md |   20 -
 ...nerated_tokenreviewspec_v1beta1_concept.md |   31 -
 ...ated_tokenreviewspec_v1beta1_definition.md |   17 -
 ...rated_tokenreviewstatus_v1beta1_concept.md |   33 -
 ...ed_tokenreviewstatus_v1beta1_definition.md |   19 -
 .../_generated_userinfo_v1beta1_concept.md    |   34 -
 .../_generated_userinfo_v1beta1_definition.md |   20 -
 .../documents/_generated_volume_v1_concept.md |   54 -
 .../_generated_volume_v1_definition.md        |   40 -
 .../_generated_volumemount_v1_concept.md      |   34 -
 .../_generated_volumemount_v1_definition.md   |   20 -
 ...pherevirtualdiskvolumesource_v1_concept.md |   32 -
 ...revirtualdiskvolumesource_v1_definition.md |   18 -
 docs/api-reference/v1.5/documents/_meta.md    |   12 -
 .../v1.5/documents/_oldversions.md            |    3 -
 .../api-reference/v1.5/documents/_overview.md |   92 -
 .../v1.5/documents/_servicediscovery.md       |   13 -
 .../v1.5/documents/_workloads.md              |   14 -
 .../v1.5/documents/deployment-original.md     |  518 ----
 .../v1.5/documents/deployment.md              |  397 ---
 docs/api-reference/v1.5/manifest.json         |  520 ----
 docs/api-reference/v1.5/runbrodocs.sh         |    6 -
 .../v1.5/documents/_cluster.md                |    5 -
 .../v1.5/documents/_config.md                 |   11 -
 .../v1.5/documents/_definitions.md            |    3 -
 ..._generated_apigroup_unversioned_concept.md |   46 -
 ...nerated_apigroup_unversioned_definition.md |   22 -
 ...erated_apigrouplist_unversioned_concept.md |   32 -
 ...ted_apigrouplist_unversioned_definition.md |   18 -
 ...nerated_apiresource_unversioned_concept.md |   44 -
 ...ated_apiresource_unversioned_definition.md |   19 -
 ...ted_apiresourcelist_unversioned_concept.md |   33 -
 ..._apiresourcelist_unversioned_definition.md |   19 -
 .../_generated_apiversion_v1beta1_concept.md  |   31 -
 ...generated_apiversion_v1beta1_definition.md |   17 -
 ...nerated_apiversions_unversioned_concept.md |   33 -
 ...ated_apiversions_unversioned_definition.md |   19 -
 .../_generated_attachedvolume_v1_concept.md   |   32 -
 ..._generated_attachedvolume_v1_definition.md |   18 -
 ...lasticblockstorevolumesource_v1_concept.md |   36 -
 ...ticblockstorevolumesource_v1_definition.md |   22 -
 ...erated_azurediskvolumesource_v1_concept.md |   35 -
 ...ted_azurediskvolumesource_v1_definition.md |   21 -
 ...erated_azurefilevolumesource_v1_concept.md |   33 -
 ...ted_azurefilevolumesource_v1_definition.md |   19 -
 .../_generated_binding_v1_concept.md          |   33 -
 .../_generated_binding_v1_definition.md       |   19 -
 .../_generated_capabilities_v1_concept.md     |   32 -
 .../_generated_capabilities_v1_definition.md  |   18 -
 ...generated_cephfsvolumesource_v1_concept.md |   36 -
 ...erated_cephfsvolumesource_v1_definition.md |   22 -
 ...tificatesigningrequest_v1alpha1_concept.md |   68 -
 ...icatesigningrequest_v1alpha1_definition.md |   21 -
 ...igningrequestcondition_v1alpha1_concept.md |   34 -
 ...ingrequestcondition_v1alpha1_definition.md |   20 -
 ...catesigningrequestlist_v1alpha1_concept.md |   33 -
 ...esigningrequestlist_v1alpha1_definition.md |   19 -
 ...catesigningrequestspec_v1alpha1_concept.md |   34 -
 ...esigningrequestspec_v1alpha1_definition.md |   20 -
 ...tesigningrequeststatus_v1alpha1_concept.md |   32 -
 ...igningrequeststatus_v1alpha1_definition.md |   18 -
 ...generated_cindervolumesource_v1_concept.md |   33 -
 ...erated_cindervolumesource_v1_definition.md |   19 -
 ..._generated_clusterrole_v1alpha1_concept.md |   45 -
 ...nerated_clusterrole_v1alpha1_definition.md |   20 -
 ...ted_clusterrolebinding_v1alpha1_concept.md |   46 -
 ..._clusterrolebinding_v1alpha1_definition.md |   21 -
 ...clusterrolebindinglist_v1alpha1_concept.md |   33 -
 ...sterrolebindinglist_v1alpha1_definition.md |   19 -
 ...erated_clusterrolelist_v1alpha1_concept.md |   33 -
 ...ted_clusterrolelist_v1alpha1_definition.md |   19 -
 ...generated_componentcondition_v1_concept.md |   34 -
 ...erated_componentcondition_v1_definition.md |   20 -
 .../_generated_componentstatus_v1_concept.md  |   45 -
 ...generated_componentstatus_v1_definition.md |   20 -
 ...enerated_componentstatuslist_v1_concept.md |   33 -
 ...rated_componentstatuslist_v1_definition.md |   19 -
 .../_generated_configmap_v1_concept.md        |   45 -
 .../_generated_configmap_v1_definition.md     |   20 -
 ...nerated_configmapkeyselector_v1_concept.md |   32 -
 ...ated_configmapkeyselector_v1_definition.md |   18 -
 .../_generated_configmaplist_v1_concept.md    |   33 -
 .../_generated_configmaplist_v1_definition.md |   19 -
 ...erated_configmapvolumesource_v1_concept.md |   35 -
 ...ted_configmapvolumesource_v1_definition.md |   21 -
 .../_generated_container_v1_concept.md        |   74 -
 .../_generated_container_v1_definition.md     |   34 -
 .../_generated_containerimage_v1_concept.md   |   32 -
 ..._generated_containerimage_v1_definition.md |   18 -
 .../_generated_containerport_v1_concept.md    |   35 -
 .../_generated_containerport_v1_definition.md |   21 -
 .../_generated_containerstate_v1_concept.md   |   33 -
 ..._generated_containerstate_v1_definition.md |   19 -
 ...erated_containerstaterunning_v1_concept.md |   31 -
 ...ted_containerstaterunning_v1_definition.md |   17 -
 ...ted_containerstateterminated_v1_concept.md |   37 -
 ..._containerstateterminated_v1_definition.md |   23 -
 ...erated_containerstatewaiting_v1_concept.md |   32 -
 ...ted_containerstatewaiting_v1_definition.md |   18 -
 .../_generated_containerstatus_v1_concept.md  |   38 -
 ...generated_containerstatus_v1_definition.md |   24 -
 ...ed_cputargetutilization_v1beta1_concept.md |   31 -
 ...cputargetutilization_v1beta1_definition.md |   17 -
 .../_generated_cronjob_v2alpha1_concept.md    |   69 -
 .../_generated_cronjob_v2alpha1_definition.md |   21 -
 ..._generated_cronjoblist_v2alpha1_concept.md |   33 -
 ...nerated_cronjoblist_v2alpha1_definition.md |   19 -
 ..._generated_cronjobspec_v2alpha1_concept.md |   35 -
 ...nerated_cronjobspec_v2alpha1_definition.md |   21 -
 ...enerated_cronjobstatus_v2alpha1_concept.md |   32 -
 ...rated_cronjobstatus_v2alpha1_definition.md |   18 -
 ..._crossversionobjectreference_v1_concept.md |   33 -
 ...ossversionobjectreference_v1_definition.md |   19 -
 .../_generated_daemonendpoint_v1_concept.md   |   31 -
 ..._generated_daemonendpoint_v1_definition.md |   17 -
 .../_generated_daemonset_v1beta1_concept.md   |   99 -
 ..._generated_daemonset_v1beta1_definition.md |   21 -
 ...generated_daemonsetlist_v1beta1_concept.md |   33 -
 ...erated_daemonsetlist_v1beta1_definition.md |   19 -
 ...generated_daemonsetspec_v1beta1_concept.md |   32 -
 ...erated_daemonsetspec_v1beta1_definition.md |   18 -
 ...nerated_daemonsetstatus_v1beta1_concept.md |   34 -
 ...ated_daemonsetstatus_v1beta1_definition.md |   20 -
 .../_generated_deleteoptions_v1_concept.md    |   35 -
 .../_generated_deleteoptions_v1_definition.md |   21 -
 .../_generated_deployment_v1beta1_concept.md  |  137 -
 ...generated_deployment_v1beta1_definition.md |   21 -
 ...ted_deploymentcondition_v1beta1_concept.md |   36 -
 ..._deploymentcondition_v1beta1_definition.md |   22 -
 ...enerated_deploymentlist_v1beta1_concept.md |   33 -
 ...rated_deploymentlist_v1beta1_definition.md |   19 -
 ...ated_deploymentrollback_v1beta1_concept.md |   34 -
 ...d_deploymentrollback_v1beta1_definition.md |   20 -
 ...enerated_deploymentspec_v1beta1_concept.md |   39 -
 ...rated_deploymentspec_v1beta1_definition.md |   25 -
 ...erated_deploymentstatus_v1beta1_concept.md |   36 -
 ...ted_deploymentstatus_v1beta1_definition.md |   22 -
 ...ated_deploymentstrategy_v1beta1_concept.md |   32 -
 ...d_deploymentstrategy_v1beta1_definition.md |   18 -
 ...erated_downwardapivolumefile_v1_concept.md |   34 -
 ...ted_downwardapivolumefile_v1_definition.md |   20 -
 ...ated_downwardapivolumesource_v1_concept.md |   32 -
 ...d_downwardapivolumesource_v1_definition.md |   18 -
 ...nerated_emptydirvolumesource_v1_concept.md |   31 -
 ...ated_emptydirvolumesource_v1_definition.md |   17 -
 .../_generated_endpointaddress_v1_concept.md  |   34 -
 ...generated_endpointaddress_v1_definition.md |   20 -
 .../_generated_endpointport_v1_concept.md     |   33 -
 .../_generated_endpointport_v1_definition.md  |   19 -
 .../_generated_endpoints_v1_concept.md        |   56 -
 .../_generated_endpoints_v1_definition.md     |   31 -
 .../_generated_endpointslist_v1_concept.md    |   33 -
 .../_generated_endpointslist_v1_definition.md |   19 -
 .../_generated_endpointsubset_v1_concept.md   |   40 -
 ..._generated_endpointsubset_v1_definition.md |   26 -
 .../documents/_generated_envvar_v1_concept.md |   33 -
 .../_generated_envvar_v1_definition.md        |   19 -
 .../_generated_envvarsource_v1_concept.md     |   34 -
 .../_generated_envvarsource_v1_definition.md  |   20 -
 .../documents/_generated_event_v1_concept.md  |   52 -
 .../_generated_event_v1_definition.md         |   27 -
 .../_generated_event_versioned_concept.md     |   31 -
 .../_generated_event_versioned_definition.md  |   17 -
 .../_generated_eventlist_v1_concept.md        |   33 -
 .../_generated_eventlist_v1_definition.md     |   19 -
 .../_generated_eventsource_v1_concept.md      |   32 -
 .../_generated_eventsource_v1_definition.md   |   18 -
 .../_generated_eviction_v1beta1_concept.md    |   33 -
 .../_generated_eviction_v1beta1_definition.md |   19 -
 .../_generated_execaction_v1_concept.md       |   31 -
 .../_generated_execaction_v1_definition.md    |   17 -
 .../_generated_fcvolumesource_v1_concept.md   |   34 -
 ..._generated_fcvolumesource_v1_definition.md |   20 -
 .../_generated_flexvolumesource_v1_concept.md |   35 -
 ...enerated_flexvolumesource_v1_definition.md |   21 -
 ...enerated_flockervolumesource_v1_concept.md |   32 -
 ...rated_flockervolumesource_v1_definition.md |   18 -
 ...cepersistentdiskvolumesource_v1_concept.md |   36 -
 ...ersistentdiskvolumesource_v1_definition.md |   22 -
 ...enerated_gitrepovolumesource_v1_concept.md |   33 -
 ...rated_gitrepovolumesource_v1_definition.md |   19 -
 ...erated_glusterfsvolumesource_v1_concept.md |   33 -
 ...ted_glusterfsvolumesource_v1_definition.md |   19 -
 ...versionfordiscovery_unversioned_concept.md |   32 -
 ...sionfordiscovery_unversioned_definition.md |   18 -
 .../_generated_handler_v1_concept.md          |   33 -
 .../_generated_handler_v1_definition.md       |   19 -
 ...ated_horizontalpodautoscaler_v1_concept.md |   71 -
 ...d_horizontalpodautoscaler_v1_definition.md |   21 -
 ...horizontalpodautoscaler_v1beta1_concept.md |   71 -
 ...izontalpodautoscaler_v1beta1_definition.md |   21 -
 ..._horizontalpodautoscalerlist_v1_concept.md |   33 -
 ...rizontalpodautoscalerlist_v1_definition.md |   19 -
 ...zontalpodautoscalerlist_v1beta1_concept.md |   33 -
 ...talpodautoscalerlist_v1beta1_definition.md |   19 -
 ..._horizontalpodautoscalerspec_v1_concept.md |   34 -
 ...rizontalpodautoscalerspec_v1_definition.md |   20 -
 ...zontalpodautoscalerspec_v1beta1_concept.md |   34 -
 ...talpodautoscalerspec_v1beta1_definition.md |   20 -
 ...orizontalpodautoscalerstatus_v1_concept.md |   35 -
 ...zontalpodautoscalerstatus_v1_definition.md |   21 -
 ...ntalpodautoscalerstatus_v1beta1_concept.md |   35 -
 ...lpodautoscalerstatus_v1beta1_definition.md |   21 -
 ...nerated_hostpathvolumesource_v1_concept.md |   31 -
 ...ated_hostpathvolumesource_v1_definition.md |   17 -
 .../_generated_httpgetaction_v1_concept.md    |   35 -
 .../_generated_httpgetaction_v1_definition.md |   21 -
 .../_generated_httpheader_v1_concept.md       |   32 -
 .../_generated_httpheader_v1_definition.md    |   18 -
 ...nerated_httpingresspath_v1beta1_concept.md |   32 -
 ...ated_httpingresspath_v1beta1_definition.md |   18 -
 ...ed_httpingressrulevalue_v1beta1_concept.md |   31 -
 ...httpingressrulevalue_v1beta1_definition.md |   17 -
 .../_generated_info_version_concept.md        |   38 -
 .../_generated_info_version_definition.md     |   24 -
 .../_generated_ingress_v1beta1_concept.md     |   66 -
 .../_generated_ingress_v1beta1_definition.md  |   21 -
 ...enerated_ingressbackend_v1beta1_concept.md |   32 -
 ...rated_ingressbackend_v1beta1_definition.md |   18 -
 .../_generated_ingresslist_v1beta1_concept.md |   33 -
 ...enerated_ingresslist_v1beta1_definition.md |   19 -
 .../_generated_ingressrule_v1beta1_concept.md |   32 -
 ...enerated_ingressrule_v1beta1_definition.md |   18 -
 .../_generated_ingressspec_v1beta1_concept.md |   33 -
 ...enerated_ingressspec_v1beta1_definition.md |   19 -
 ...generated_ingressstatus_v1beta1_concept.md |   31 -
 ...erated_ingressstatus_v1beta1_definition.md |   17 -
 .../_generated_ingresstls_v1beta1_concept.md  |   32 -
 ...generated_ingresstls_v1beta1_definition.md |   18 -
 .../_generated_intorstring_intstr_concept.md  |   30 -
 ...generated_intorstring_intstr_definition.md |   16 -
 ..._generated_iscsivolumesource_v1_concept.md |   36 -
 ...nerated_iscsivolumesource_v1_definition.md |   22 -
 .../documents/_generated_job_v1_concept.md    |   98 -
 .../documents/_generated_job_v1_definition.md |   21 -
 .../_generated_job_v1beta1_concept.md         |   74 -
 .../_generated_job_v1beta1_definition.md      |   21 -
 .../_generated_job_v2alpha1_concept.md        |   74 -
 .../_generated_job_v2alpha1_definition.md     |   21 -
 .../_generated_jobcondition_v1_concept.md     |   36 -
 .../_generated_jobcondition_v1_definition.md  |   22 -
 ..._generated_jobcondition_v1beta1_concept.md |   36 -
 ...nerated_jobcondition_v1beta1_definition.md |   22 -
 ...generated_jobcondition_v2alpha1_concept.md |   36 -
 ...erated_jobcondition_v2alpha1_definition.md |   22 -
 .../_generated_joblist_v1_concept.md          |   33 -
 .../_generated_joblist_v1_definition.md       |   19 -
 .../_generated_joblist_v1beta1_concept.md     |   33 -
 .../_generated_joblist_v1beta1_definition.md  |   19 -
 .../_generated_joblist_v2alpha1_concept.md    |   33 -
 .../_generated_joblist_v2alpha1_definition.md |   19 -
 .../_generated_jobspec_v1_concept.md          |   36 -
 .../_generated_jobspec_v1_definition.md       |   22 -
 .../_generated_jobspec_v1beta1_concept.md     |   36 -
 .../_generated_jobspec_v1beta1_definition.md  |   22 -
 .../_generated_jobspec_v2alpha1_concept.md    |   36 -
 .../_generated_jobspec_v2alpha1_definition.md |   22 -
 .../_generated_jobstatus_v1_concept.md        |   36 -
 .../_generated_jobstatus_v1_definition.md     |   22 -
 .../_generated_jobstatus_v1beta1_concept.md   |   36 -
 ..._generated_jobstatus_v1beta1_definition.md |   22 -
 .../_generated_jobstatus_v2alpha1_concept.md  |   36 -
 ...generated_jobstatus_v2alpha1_definition.md |   22 -
 ...erated_jobtemplatespec_v2alpha1_concept.md |   32 -
 ...ted_jobtemplatespec_v2alpha1_definition.md |   18 -
 .../_generated_keytopath_v1_concept.md        |   33 -
 .../_generated_keytopath_v1_definition.md     |   19 -
 ...rated_labelselector_unversioned_concept.md |   32 -
 ...ed_labelselector_unversioned_definition.md |   18 -
 ...selectorrequirement_unversioned_concept.md |   33 -
 ...ectorrequirement_unversioned_definition.md |   19 -
 .../_generated_lifecycle_v1_concept.md        |   32 -
 .../_generated_lifecycle_v1_definition.md     |   18 -
 .../_generated_limitrange_v1_concept.md       |   54 -
 .../_generated_limitrange_v1_definition.md    |   20 -
 .../_generated_limitrangeitem_v1_concept.md   |   36 -
 ..._generated_limitrangeitem_v1_definition.md |   22 -
 .../_generated_limitrangelist_v1_concept.md   |   33 -
 ..._generated_limitrangelist_v1_definition.md |   19 -
 .../_generated_limitrangespec_v1_concept.md   |   31 -
 ..._generated_limitrangespec_v1_definition.md |   17 -
 ..._generated_listmeta_unversioned_concept.md |   32 -
 ...nerated_listmeta_unversioned_definition.md |   18 -
 ...enerated_loadbalanceringress_v1_concept.md |   32 -
 ...rated_loadbalanceringress_v1_definition.md |   18 -
 ...generated_loadbalancerstatus_v1_concept.md |   31 -
 ...erated_loadbalancerstatus_v1_definition.md |   17 -
 ...nerated_localobjectreference_v1_concept.md |   31 -
 ...ated_localobjectreference_v1_definition.md |   17 -
 ...ocalsubjectaccessreview_v1beta1_concept.md |   34 -
 ...lsubjectaccessreview_v1beta1_definition.md |   20 -
 .../_generated_namespace_v1_concept.md        |   64 -
 .../_generated_namespace_v1_definition.md     |   21 -
 .../_generated_namespacelist_v1_concept.md    |   33 -
 .../_generated_namespacelist_v1_definition.md |   19 -
 .../_generated_namespacespec_v1_concept.md    |   31 -
 .../_generated_namespacespec_v1_definition.md |   17 -
 .../_generated_namespacestatus_v1_concept.md  |   31 -
 ...generated_namespacestatus_v1_definition.md |   17 -
 ...generated_networkpolicy_v1beta1_concept.md |   55 -
 ...erated_networkpolicy_v1beta1_definition.md |   20 -
 ...etworkpolicyingressrule_v1beta1_concept.md |   32 -
 ...orkpolicyingressrule_v1beta1_definition.md |   18 -
 ...rated_networkpolicylist_v1beta1_concept.md |   33 -
 ...ed_networkpolicylist_v1beta1_definition.md |   19 -
 ...rated_networkpolicypeer_v1beta1_concept.md |   32 -
 ...ed_networkpolicypeer_v1beta1_definition.md |   18 -
 ...rated_networkpolicyport_v1beta1_concept.md |   32 -
 ...ed_networkpolicyport_v1beta1_definition.md |   18 -
 ...rated_networkpolicyspec_v1beta1_concept.md |   32 -
 ...ed_networkpolicyspec_v1beta1_definition.md |   18 -
 .../_generated_nfsvolumesource_v1_concept.md  |   33 -
 ...generated_nfsvolumesource_v1_definition.md |   19 -
 .../documents/_generated_node_v1_concept.md   |   76 -
 .../_generated_node_v1_definition.md          |   21 -
 .../_generated_nodeaddress_v1_concept.md      |   32 -
 .../_generated_nodeaddress_v1_definition.md   |   18 -
 .../_generated_nodecondition_v1_concept.md    |   36 -
 .../_generated_nodecondition_v1_definition.md |   22 -
 ...enerated_nodedaemonendpoints_v1_concept.md |   31 -
 ...rated_nodedaemonendpoints_v1_definition.md |   17 -
 .../_generated_nodelist_v1_concept.md         |   33 -
 .../_generated_nodelist_v1_definition.md      |   19 -
 .../_generated_nodespec_v1_concept.md         |   34 -
 .../_generated_nodespec_v1_definition.md      |   20 -
 .../_generated_nodestatus_v1_concept.md       |   40 -
 .../_generated_nodestatus_v1_definition.md    |   26 -
 .../_generated_nodesysteminfo_v1_concept.md   |   40 -
 ..._generated_nodesysteminfo_v1_definition.md |   26 -
 ...d_nonresourceattributes_v1beta1_concept.md |   32 -
 ...onresourceattributes_v1beta1_definition.md |   18 -
 ...enerated_objectfieldselector_v1_concept.md |   32 -
 ...rated_objectfieldselector_v1_definition.md |   18 -
 .../_generated_objectmeta_v1_concept.md       |   45 -
 .../_generated_objectmeta_v1_definition.md    |   31 -
 .../_generated_objectreference_v1_concept.md  |   37 -
 ...generated_objectreference_v1_definition.md |   23 -
 .../_generated_ownerreference_v1_concept.md   |   35 -
 ..._generated_ownerreference_v1_definition.md |   21 -
 .../_generated_patch_unversioned_concept.md   |   29 -
 ..._generated_patch_unversioned_definition.md |   15 -
 .../_generated_persistentvolume_v1_concept.md |   86 -
 ...enerated_persistentvolume_v1_definition.md |   21 -
 ...erated_persistentvolumeclaim_v1_concept.md |   69 -
 ...ted_persistentvolumeclaim_v1_definition.md |   21 -
 ...ed_persistentvolumeclaimlist_v1_concept.md |   33 -
 ...persistentvolumeclaimlist_v1_definition.md |   19 -
 ...ed_persistentvolumeclaimspec_v1_concept.md |   34 -
 ...persistentvolumeclaimspec_v1_definition.md |   20 -
 ..._persistentvolumeclaimstatus_v1_concept.md |   33 -
 ...rsistentvolumeclaimstatus_v1_definition.md |   19 -
 ...stentvolumeclaimvolumesource_v1_concept.md |   32 -
 ...ntvolumeclaimvolumesource_v1_definition.md |   18 -
 ...nerated_persistentvolumelist_v1_concept.md |   33 -
 ...ated_persistentvolumelist_v1_definition.md |   19 -
 ...nerated_persistentvolumespec_v1_concept.md |   51 -
 ...ated_persistentvolumespec_v1_definition.md |   37 -
 ...rated_persistentvolumestatus_v1_concept.md |   33 -
 ...ed_persistentvolumestatus_v1_definition.md |   19 -
 ...onpersistentdiskvolumesource_v1_concept.md |   32 -
 ...ersistentdiskvolumesource_v1_definition.md |   18 -
 .../documents/_generated_pod_v1_concept.md    |  103 -
 .../documents/_generated_pod_v1_definition.md |   21 -
 .../_generated_podcondition_v1_concept.md     |   36 -
 .../_generated_podcondition_v1_definition.md  |   22 -
 ...ted_poddisruptionbudget_v1beta1_concept.md |   70 -
 ..._poddisruptionbudget_v1beta1_definition.md |   21 -
 ...poddisruptionbudgetlist_v1beta1_concept.md |   33 -
 ...disruptionbudgetlist_v1beta1_definition.md |   19 -
 ...poddisruptionbudgetspec_v1beta1_concept.md |   32 -
 ...disruptionbudgetspec_v1beta1_definition.md |   18 -
 ...ddisruptionbudgetstatus_v1beta1_concept.md |   36 -
 ...sruptionbudgetstatus_v1beta1_definition.md |   22 -
 .../_generated_podlist_v1_concept.md          |   33 -
 .../_generated_podlist_v1_definition.md       |   19 -
 ...generated_podsecuritycontext_v1_concept.md |   35 -
 ...erated_podsecuritycontext_v1_definition.md |   21 -
 .../_generated_podspec_v1_concept.md          |   47 -
 .../_generated_podspec_v1_definition.md       |   33 -
 .../_generated_podstatus_v1_concept.md        |   38 -
 .../_generated_podstatus_v1_definition.md     |   24 -
 .../_generated_podtemplate_v1_concept.md      |   55 -
 .../_generated_podtemplate_v1_definition.md   |   20 -
 .../_generated_podtemplatelist_v1_concept.md  |   33 -
 ...generated_podtemplatelist_v1_definition.md |   19 -
 .../_generated_podtemplatespec_v1_concept.md  |   32 -
 ...generated_podtemplatespec_v1_definition.md |   18 -
 .../_generated_policyrule_v1alpha1_concept.md |   36 -
 ...enerated_policyrule_v1alpha1_definition.md |   22 -
 .../_generated_preconditions_v1_concept.md    |   31 -
 .../_generated_preconditions_v1_definition.md |   17 -
 .../documents/_generated_probe_v1_concept.md  |   38 -
 .../_generated_probe_v1_definition.md         |   24 -
 .../_generated_quantity_resource_concept.md   |   30 -
 ..._generated_quantity_resource_definition.md |   16 -
 ...enerated_quobytevolumesource_v1_concept.md |   35 -
 ...rated_quobytevolumesource_v1_definition.md |   21 -
 ..._generated_rawextension_runtime_concept.md |   58 -
 ...nerated_rawextension_runtime_definition.md |   44 -
 .../_generated_rbdvolumesource_v1_concept.md  |   38 -
 ...generated_rbdvolumesource_v1_definition.md |   24 -
 .../_generated_replicaset_v1beta1_concept.md  |   96 -
 ...generated_replicaset_v1beta1_definition.md |   21 -
 ...ted_replicasetcondition_v1beta1_concept.md |   35 -
 ..._replicasetcondition_v1beta1_definition.md |   21 -
 ...enerated_replicasetlist_v1beta1_concept.md |   33 -
 ...rated_replicasetlist_v1beta1_definition.md |   19 -
 ...enerated_replicasetspec_v1beta1_concept.md |   34 -
 ...rated_replicasetspec_v1beta1_definition.md |   20 -
 ...erated_replicasetstatus_v1beta1_concept.md |   36 -
 ...ted_replicasetstatus_v1beta1_definition.md |   22 -
 ...erated_replicationcontroller_v1_concept.md |   96 -
 ...ted_replicationcontroller_v1_definition.md |   21 -
 ...plicationcontrollercondition_v1_concept.md |   35 -
 ...cationcontrollercondition_v1_definition.md |   21 -
 ...ed_replicationcontrollerlist_v1_concept.md |   33 -
 ...replicationcontrollerlist_v1_definition.md |   19 -
 ...ed_replicationcontrollerspec_v1_concept.md |   34 -
 ...replicationcontrollerspec_v1_definition.md |   20 -
 ..._replicationcontrollerstatus_v1_concept.md |   36 -
 ...plicationcontrollerstatus_v1_definition.md |   22 -
 ...ated_resourceattributes_v1beta1_concept.md |   37 -
 ...d_resourceattributes_v1beta1_definition.md |   23 -
 ...erated_resourcefieldselector_v1_concept.md |   33 -
 ...ted_resourcefieldselector_v1_definition.md |   19 -
 .../_generated_resourcequota_v1_concept.md    |   66 -
 .../_generated_resourcequota_v1_definition.md |   21 -
 ..._generated_resourcequotalist_v1_concept.md |   33 -
 ...nerated_resourcequotalist_v1_definition.md |   19 -
 ..._generated_resourcequotaspec_v1_concept.md |   32 -
 ...nerated_resourcequotaspec_v1_definition.md |   18 -
 ...enerated_resourcequotastatus_v1_concept.md |   32 -
 ...rated_resourcequotastatus_v1_definition.md |   18 -
 ...nerated_resourcerequirements_v1_concept.md |   32 -
 ...ated_resourcerequirements_v1_definition.md |   18 -
 .../_generated_role_v1alpha1_concept.md       |   45 -
 .../_generated_role_v1alpha1_definition.md    |   20 -
 ..._generated_rolebinding_v1alpha1_concept.md |   46 -
 ...nerated_rolebinding_v1alpha1_definition.md |   21 -
 ...erated_rolebindinglist_v1alpha1_concept.md |   33 -
 ...ted_rolebindinglist_v1alpha1_definition.md |   19 -
 .../_generated_rolelist_v1alpha1_concept.md   |   33 -
 ..._generated_rolelist_v1alpha1_definition.md |   19 -
 .../_generated_roleref_v1alpha1_concept.md    |   33 -
 .../_generated_roleref_v1alpha1_definition.md |   19 -
 ...enerated_rollbackconfig_v1beta1_concept.md |   31 -
 ...rated_rollbackconfig_v1beta1_definition.md |   17 -
 ...rollingupdatedeployment_v1beta1_concept.md |   32 -
 ...lingupdatedeployment_v1beta1_definition.md |   18 -
 .../documents/_generated_scale_v1_concept.md  |   53 -
 .../_generated_scale_v1_definition.md         |   20 -
 .../_generated_scale_v1beta1_concept.md       |   54 -
 .../_generated_scale_v1beta1_definition.md    |   20 -
 .../_generated_scalespec_v1_concept.md        |   31 -
 .../_generated_scalespec_v1_definition.md     |   17 -
 .../_generated_scalespec_v1beta1_concept.md   |   31 -
 ..._generated_scalespec_v1beta1_definition.md |   17 -
 .../_generated_scalestatus_v1_concept.md      |   32 -
 .../_generated_scalestatus_v1_definition.md   |   18 -
 .../_generated_scalestatus_v1beta1_concept.md |   33 -
 ...enerated_scalestatus_v1beta1_definition.md |   19 -
 .../documents/_generated_secret_v1_concept.md |   47 -
 .../_generated_secret_v1_definition.md        |   22 -
 ..._generated_secretkeyselector_v1_concept.md |   32 -
 ...nerated_secretkeyselector_v1_definition.md |   18 -
 .../_generated_secretlist_v1_concept.md       |   33 -
 .../_generated_secretlist_v1_definition.md    |   19 -
 ...generated_secretvolumesource_v1_concept.md |   35 -
 ...erated_secretvolumesource_v1_definition.md |   21 -
 .../_generated_securitycontext_v1_concept.md  |   36 -
 ...generated_securitycontext_v1_definition.md |   22 -
 ...selfsubjectaccessreview_v1beta1_concept.md |   44 -
 ...fsubjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   32 -
 ...jectaccessreviewspec_v1beta1_definition.md |   18 -
 .../_generated_selinuxoptions_v1_concept.md   |   34 -
 ..._generated_selinuxoptions_v1_definition.md |   20 -
 ...addressbyclientcidr_unversioned_concept.md |   32 -
 ...ressbyclientcidr_unversioned_definition.md |   18 -
 .../_generated_service_v1_concept.md          |   99 -
 .../_generated_service_v1_definition.md       |   21 -
 .../_generated_serviceaccount_v1_concept.md   |   46 -
 ..._generated_serviceaccount_v1_definition.md |   21 -
 ...generated_serviceaccountlist_v1_concept.md |   33 -
 ...erated_serviceaccountlist_v1_definition.md |   19 -
 .../_generated_servicelist_v1_concept.md      |   33 -
 .../_generated_servicelist_v1_definition.md   |   19 -
 .../_generated_serviceport_v1_concept.md      |   35 -
 .../_generated_serviceport_v1_definition.md   |   21 -
 .../_generated_servicespec_v1_concept.md      |   40 -
 .../_generated_servicespec_v1_definition.md   |   26 -
 .../_generated_servicestatus_v1_concept.md    |   31 -
 .../_generated_servicestatus_v1_definition.md |   17 -
 .../_generated_statefulset_v1beta1_concept.md |   72 -
 ...enerated_statefulset_v1beta1_definition.md |   24 -
 ...nerated_statefulsetlist_v1beta1_concept.md |   33 -
 ...ated_statefulsetlist_v1beta1_definition.md |   19 -
 ...nerated_statefulsetspec_v1beta1_concept.md |   35 -
 ...ated_statefulsetspec_v1beta1_definition.md |   21 -
 ...rated_statefulsetstatus_v1beta1_concept.md |   32 -
 ...ed_statefulsetstatus_v1beta1_definition.md |   18 -
 .../_generated_status_unversioned_concept.md  |   37 -
 ...generated_status_unversioned_definition.md |   23 -
 ...nerated_statuscause_unversioned_concept.md |   33 -
 ...ated_statuscause_unversioned_definition.md |   19 -
 ...rated_statusdetails_unversioned_concept.md |   35 -
 ...ed_statusdetails_unversioned_definition.md |   21 -
 ..._generated_storageclass_v1beta1_concept.md |   48 -
 ...nerated_storageclass_v1beta1_definition.md |   23 -
 ...erated_storageclasslist_v1beta1_concept.md |   33 -
 ...ted_storageclasslist_v1beta1_definition.md |   19 -
 .../_generated_subject_v1alpha1_concept.md    |   34 -
 .../_generated_subject_v1alpha1_definition.md |   20 -
 ...ted_subjectaccessreview_v1beta1_concept.md |   58 -
 ..._subjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   35 -
 ...jectaccessreviewspec_v1beta1_definition.md |   21 -
 ...bjectaccessreviewstatus_v1beta1_concept.md |   33 -
 ...ctaccessreviewstatus_v1beta1_definition.md |   19 -
 ...ed_subresourcereference_v1beta1_concept.md |   34 -
 ...subresourcereference_v1beta1_definition.md |   20 -
 .../_generated_tcpsocketaction_v1_concept.md  |   31 -
 ...generated_tcpsocketaction_v1_definition.md |   17 -
 ...ated_thirdpartyresource_v1beta1_concept.md |   46 -
 ...d_thirdpartyresource_v1beta1_definition.md |   21 -
 ..._thirdpartyresourcelist_v1beta1_concept.md |   33 -
 ...irdpartyresourcelist_v1beta1_definition.md |   19 -
 .../_generated_time_unversioned_concept.md    |   30 -
 .../_generated_time_unversioned_definition.md |   16 -
 .../_generated_tokenreview_v1beta1_concept.md |   54 -
 ...enerated_tokenreview_v1beta1_definition.md |   20 -
 ...nerated_tokenreviewspec_v1beta1_concept.md |   31 -
 ...ated_tokenreviewspec_v1beta1_definition.md |   17 -
 ...rated_tokenreviewstatus_v1beta1_concept.md |   33 -
 ...ed_tokenreviewstatus_v1beta1_definition.md |   19 -
 .../_generated_userinfo_v1beta1_concept.md    |   34 -
 .../_generated_userinfo_v1beta1_definition.md |   20 -
 .../documents/_generated_volume_v1_concept.md |   54 -
 .../_generated_volume_v1_definition.md        |   40 -
 .../_generated_volumemount_v1_concept.md      |   34 -
 .../_generated_volumemount_v1_definition.md   |   20 -
 ...pherevirtualdiskvolumesource_v1_concept.md |   32 -
 ...revirtualdiskvolumesource_v1_definition.md |   18 -
 .../v1.5/documents/_meta.md                   |   12 -
 .../v1.5/documents/_oldversions.md            |    3 -
 .../v1.5/documents/_overview.md               |   92 -
 .../v1.5/documents/_servicediscovery.md       |   13 -
 .../v1.5/documents/_workloads.md              |   14 -
 .../v1.5/documents/deployment-original.md     |  518 ----
 .../v1.5/documents/deployment.md              |  397 ---
 docs/resources-reference/v1.5/manifest.json   |  517 ----
 docs/resources-reference/v1.5/runbrodocs.sh   |    6 -
 .../kubectl/v1.5/documents/_app_management.md |    4 -
 .../kubectl/v1.5/documents/_cluster.md        |    5 -
 .../kubectl/v1.5/documents/_config.md         |   11 -
 .../kubectl/v1.5/documents/_definitions.md    |    3 -
 .../v1.5/documents/_generated_annotate.md     |  108 -
 .../v1.5/documents/_generated_api-versions.md |   14 -
 ..._generated_apigroup_unversioned_concept.md |   42 -
 ...nerated_apigroup_unversioned_definition.md |   22 -
 ...erated_apigrouplist_unversioned_concept.md |   30 -
 ...ted_apigrouplist_unversioned_definition.md |   18 -
 ...nerated_apiresource_unversioned_concept.md |   42 -
 ...ated_apiresource_unversioned_definition.md |   21 -
 ...ted_apiresourcelist_unversioned_concept.md |   31 -
 ..._apiresourcelist_unversioned_definition.md |   19 -
 .../_generated_apiversion_v1beta1_concept.md  |   31 -
 ...generated_apiversion_v1beta1_definition.md |   19 -
 ...nerated_apiversions_unversioned_concept.md |   31 -
 ...ated_apiversions_unversioned_definition.md |   19 -
 .../v1.5/documents/_generated_apply.md        |   70 -
 .../v1.5/documents/_generated_attach.md       |   40 -
 .../_generated_attachedvolume_v1_concept.md   |   32 -
 ..._generated_attachedvolume_v1_definition.md |   20 -
 .../v1.5/documents/_generated_autoscale.md    |   51 -
 .../_generated_binding_v1_concept.md          |   93 -
 .../_generated_binding_v1_definition.md       |   19 -
 .../_generated_capabilities_v1_concept.md     |   32 -
 .../_generated_capabilities_v1_definition.md  |   20 -
 .../_generated_category_cluster_management.md |    1 -
 ...ted_category_declarative_app_management.md |    1 -
 ..._generated_category_deprecated_commands.md |    1 -
 ...ted_category_kubectl_settings_and_usage.md |    1 -
 .../v1.5/documents/_generated_certificate.md  |   68 -
 ...tificatesigningrequest_v1alpha1_concept.md |  630 -----
 ...icatesigningrequest_v1alpha1_definition.md |   21 -
 ...igningrequestcondition_v1alpha1_concept.md |   34 -
 ...ingrequestcondition_v1alpha1_definition.md |   22 -
 ...catesigningrequestlist_v1alpha1_concept.md |   31 -
 ...esigningrequestlist_v1alpha1_definition.md |   19 -
 ...catesigningrequestspec_v1alpha1_concept.md |   34 -
 ...esigningrequestspec_v1alpha1_definition.md |   22 -
 ...tesigningrequeststatus_v1alpha1_concept.md |   94 -
 ...igningrequeststatus_v1alpha1_definition.md |   20 -
 .../v1.5/documents/_generated_cluster-info.md |   70 -
 ..._generated_clusterrole_v1alpha1_concept.md |  601 -----
 ...nerated_clusterrole_v1alpha1_definition.md |   20 -
 ...ted_clusterrolebinding_v1alpha1_concept.md |  542 ----
 ..._clusterrolebinding_v1alpha1_definition.md |   21 -
 ...clusterrolebindinglist_v1alpha1_concept.md |   96 -
 ...sterrolebindinglist_v1alpha1_definition.md |   19 -
 ...erated_clusterrolelist_v1alpha1_concept.md |   31 -
 ...ted_clusterrolelist_v1alpha1_definition.md |   19 -
 .../v1.5/documents/_generated_completion.md   |   30 -
 ...generated_componentcondition_v1_concept.md |   34 -
 ...erated_componentcondition_v1_definition.md |   22 -
 .../_generated_componentstatus_v1_concept.md  |  162 --
 ...generated_componentstatus_v1_definition.md |   20 -
 ...enerated_componentstatuslist_v1_concept.md |   31 -
 ...rated_componentstatuslist_v1_definition.md |   19 -
 .../v1.5/documents/_generated_config.md       |  382 ---
 .../_generated_configmap_v1_concept.md        |  675 -----
 .../_generated_configmap_v1_definition.md     |   20 -
 ...nerated_configmapkeyselector_v1_concept.md |   31 -
 ...ated_configmapkeyselector_v1_definition.md |   19 -
 .../_generated_configmaplist_v1_concept.md    |   97 -
 .../_generated_configmaplist_v1_definition.md |   19 -
 .../_generated_container_v1_concept.md        |   84 -
 .../_generated_container_v1_definition.md     |   36 -
 .../_generated_containerimage_v1_concept.md   |   32 -
 ..._generated_containerimage_v1_definition.md |   20 -
 .../_generated_containerport_v1_concept.md    |   35 -
 .../_generated_containerport_v1_definition.md |   23 -
 .../_generated_containerstate_v1_concept.md   |   33 -
 ..._generated_containerstate_v1_definition.md |   21 -
 ...erated_containerstaterunning_v1_concept.md |   31 -
 ...ted_containerstaterunning_v1_definition.md |   19 -
 ...ted_containerstateterminated_v1_concept.md |   37 -
 ..._containerstateterminated_v1_definition.md |   25 -
 ...erated_containerstatewaiting_v1_concept.md |   32 -
 ...ted_containerstatewaiting_v1_definition.md |   20 -
 .../_generated_containerstatus_v1_concept.md  |   38 -
 ...generated_containerstatus_v1_definition.md |   26 -
 .../v1.5/documents/_generated_convert.md      |   54 -
 .../v1.5/documents/_generated_cordon.md       |   19 -
 .../kubectl/v1.5/documents/_generated_cp.md   |   44 -
 ...ed_cputargetutilization_v1beta1_concept.md |   31 -
 ...cputargetutilization_v1beta1_definition.md |   19 -
 .../v1.5/documents/_generated_create.md       |  585 ----
 ..._crossversionobjectreference_v1_concept.md |   33 -
 ...ossversionobjectreference_v1_definition.md |   21 -
 .../_generated_daemonendpoint_v1_concept.md   |   31 -
 ..._generated_daemonendpoint_v1_definition.md |   19 -
 .../_generated_daemonset_v1beta1_concept.md   | 1122 --------
 ..._generated_daemonset_v1beta1_definition.md |   21 -
 ...generated_daemonsetlist_v1beta1_concept.md |   31 -
 ...erated_daemonsetlist_v1beta1_definition.md |   19 -
 ...generated_daemonsetspec_v1beta1_concept.md |   32 -
 ...erated_daemonsetspec_v1beta1_definition.md |   20 -
 ...nerated_daemonsetstatus_v1beta1_concept.md |   34 -
 ...ated_daemonsetstatus_v1beta1_definition.md |   22 -
 .../v1.5/documents/_generated_delete.md       |   87 -
 .../_generated_deleteoptions_v1_concept.md    |   33 -
 .../_generated_deleteoptions_v1_definition.md |   21 -
 .../_generated_deployment_v1beta1_concept.md  | 1952 --------------
 ...generated_deployment_v1beta1_definition.md |   21 -
 ...ted_deploymentcondition_v1beta1_concept.md |   36 -
 ..._deploymentcondition_v1beta1_definition.md |   24 -
 ...enerated_deploymentlist_v1beta1_concept.md |   31 -
 ...rated_deploymentlist_v1beta1_definition.md |   19 -
 ...ated_deploymentrollback_v1beta1_concept.md |   32 -
 ...d_deploymentrollback_v1beta1_definition.md |   20 -
 ...enerated_deploymentspec_v1beta1_concept.md |   39 -
 ...rated_deploymentspec_v1beta1_definition.md |   27 -
 ...erated_deploymentstatus_v1beta1_concept.md |  227 --
 ...ted_deploymentstatus_v1beta1_definition.md |   24 -
 ...ated_deploymentstrategy_v1beta1_concept.md |   32 -
 ...d_deploymentstrategy_v1beta1_definition.md |   20 -
 .../v1.5/documents/_generated_describe.md     |   96 -
 .../v1.5/documents/_generated_drain.md        |   44 -
 .../kubectl/v1.5/documents/_generated_edit.md |   53 -
 .../_generated_endpointaddress_v1_concept.md  |   34 -
 ...generated_endpointaddress_v1_definition.md |   22 -
 .../_generated_endpointport_v1_concept.md     |   33 -
 .../_generated_endpointport_v1_definition.md  |   21 -
 .../_generated_endpoints_v1_concept.md        |  747 ------
 .../_generated_endpoints_v1_definition.md     |   31 -
 .../_generated_endpointslist_v1_concept.md    |   31 -
 .../_generated_endpointslist_v1_definition.md |   19 -
 .../_generated_endpointsubset_v1_concept.md   |   40 -
 ..._generated_endpointsubset_v1_definition.md |   28 -
 .../documents/_generated_envvar_v1_concept.md |   33 -
 .../_generated_envvar_v1_definition.md        |   21 -
 .../_generated_envvarsource_v1_concept.md     |   34 -
 .../_generated_envvarsource_v1_definition.md  |   22 -
 .../documents/_generated_event_v1_concept.md  |  743 ------
 .../_generated_event_v1_definition.md         |   27 -
 .../_generated_event_versioned_concept.md     |   31 -
 .../_generated_event_versioned_definition.md  |   19 -
 .../_generated_eventlist_v1_concept.md        |   31 -
 .../_generated_eventlist_v1_definition.md     |   19 -
 .../_generated_eventsource_v1_concept.md      |   32 -
 .../_generated_eventsource_v1_definition.md   |   20 -
 .../_generated_eviction_v1beta1_concept.md    |   31 -
 .../_generated_eviction_v1beta1_definition.md |   19 -
 .../kubectl/v1.5/documents/_generated_exec.md |   41 -
 .../_generated_execaction_v1_concept.md       |   31 -
 .../_generated_execaction_v1_definition.md    |   19 -
 .../v1.5/documents/_generated_explain.md      |   64 -
 .../v1.5/documents/_generated_expose.md       |   94 -
 .../kubectl/v1.5/documents/_generated_get.md  |  120 -
 ...versionfordiscovery_unversioned_concept.md |   32 -
 ...sionfordiscovery_unversioned_definition.md |   20 -
 .../_generated_handler_v1_concept.md          |   33 -
 .../_generated_handler_v1_definition.md       |   21 -
 ...ated_horizontalpodautoscaler_v1_concept.md |  948 -------
 ...d_horizontalpodautoscaler_v1_definition.md |   21 -
 ...horizontalpodautoscaler_v1beta1_concept.md |  948 -------
 ...izontalpodautoscaler_v1beta1_definition.md |   21 -
 ..._horizontalpodautoscalerlist_v1_concept.md |   31 -
 ...rizontalpodautoscalerlist_v1_definition.md |   19 -
 ...zontalpodautoscalerlist_v1beta1_concept.md |   31 -
 ...talpodautoscalerlist_v1beta1_definition.md |   19 -
 ..._horizontalpodautoscalerspec_v1_concept.md |   34 -
 ...rizontalpodautoscalerspec_v1_definition.md |   22 -
 ...zontalpodautoscalerspec_v1beta1_concept.md |   34 -
 ...talpodautoscalerspec_v1beta1_definition.md |   22 -
 ...orizontalpodautoscalerstatus_v1_concept.md |   35 -
 ...zontalpodautoscalerstatus_v1_definition.md |   23 -
 ...ntalpodautoscalerstatus_v1beta1_concept.md |   35 -
 ...lpodautoscalerstatus_v1beta1_definition.md |   23 -
 .../_generated_httpgetaction_v1_concept.md    |   35 -
 .../_generated_httpgetaction_v1_definition.md |   23 -
 .../_generated_httpheader_v1_concept.md       |   32 -
 .../_generated_httpheader_v1_definition.md    |   20 -
 .../_generated_info_version_concept.md        |   38 -
 .../_generated_info_version_definition.md     |   26 -
 .../_generated_ingress_v1beta1_concept.md     |  696 -----
 .../_generated_ingress_v1beta1_definition.md  |   21 -
 ...enerated_ingressbackend_v1beta1_concept.md |   32 -
 ...rated_ingressbackend_v1beta1_definition.md |   20 -
 .../_generated_ingresslist_v1beta1_concept.md |   97 -
 ...enerated_ingresslist_v1beta1_definition.md |   19 -
 .../_generated_ingressrule_v1beta1_concept.md |   31 -
 ...enerated_ingressrule_v1beta1_definition.md |   19 -
 .../_generated_ingressspec_v1beta1_concept.md |   33 -
 ...enerated_ingressspec_v1beta1_definition.md |   21 -
 ...generated_ingressstatus_v1beta1_concept.md |  222 --
 ...erated_ingressstatus_v1beta1_definition.md |   19 -
 .../_generated_ingresstls_v1beta1_concept.md  |   32 -
 ...generated_ingresstls_v1beta1_definition.md |   20 -
 .../_generated_intorstring_intstr_concept.md  |   30 -
 ...generated_intorstring_intstr_definition.md |   18 -
 .../documents/_generated_job_v1_concept.md    | 1210 ---------
 .../documents/_generated_job_v1_definition.md |   21 -
 .../_generated_job_v1beta1_concept.md         | 1409 ----------
 .../_generated_job_v1beta1_definition.md      |   21 -
 .../_generated_jobcondition_v1_concept.md     |   36 -
 .../_generated_jobcondition_v1_definition.md  |   24 -
 ..._generated_jobcondition_v1beta1_concept.md |   36 -
 ...nerated_jobcondition_v1beta1_definition.md |   24 -
 .../_generated_joblist_v1_concept.md          |   97 -
 .../_generated_joblist_v1_definition.md       |   19 -
 .../_generated_joblist_v1beta1_concept.md     |   31 -
 .../_generated_joblist_v1beta1_definition.md  |   19 -
 .../_generated_jobspec_v1_concept.md          |   36 -
 .../_generated_jobspec_v1_definition.md       |   24 -
 .../_generated_jobspec_v1beta1_concept.md     |   36 -
 .../_generated_jobspec_v1beta1_definition.md  |   24 -
 .../_generated_jobstatus_v1_concept.md        |  227 --
 .../_generated_jobstatus_v1_definition.md     |   24 -
 .../_generated_jobstatus_v1beta1_concept.md   |   36 -
 ..._generated_jobstatus_v1beta1_definition.md |   24 -
 .../v1.5/documents/_generated_label.md        |   76 -
 ...rated_labelselector_unversioned_concept.md |   32 -
 ...ed_labelselector_unversioned_definition.md |   20 -
 ...selectorrequirement_unversioned_concept.md |   33 -
 ...ectorrequirement_unversioned_definition.md |   21 -
 .../_generated_lifecycle_v1_concept.md        |   32 -
 .../_generated_lifecycle_v1_definition.md     |   20 -
 .../_generated_limitrange_v1_concept.md       |  745 ------
 .../_generated_limitrange_v1_definition.md    |   20 -
 .../_generated_limitrangeitem_v1_concept.md   |   36 -
 ..._generated_limitrangeitem_v1_definition.md |   24 -
 .../_generated_limitrangelist_v1_concept.md   |   31 -
 ..._generated_limitrangelist_v1_definition.md |   19 -
 .../_generated_limitrangespec_v1_concept.md   |   31 -
 ..._generated_limitrangespec_v1_definition.md |   19 -
 ..._generated_listmeta_unversioned_concept.md |   32 -
 ...nerated_listmeta_unversioned_definition.md |   20 -
 ...enerated_loadbalanceringress_v1_concept.md |   32 -
 ...rated_loadbalanceringress_v1_definition.md |   20 -
 ...generated_loadbalancerstatus_v1_concept.md |   31 -
 ...erated_loadbalancerstatus_v1_definition.md |   19 -
 ...nerated_localobjectreference_v1_concept.md |   31 -
 ...ated_localobjectreference_v1_definition.md |   19 -
 ...ocalsubjectaccessreview_v1beta1_concept.md |   94 -
 ...lsubjectaccessreview_v1beta1_definition.md |   20 -
 .../kubectl/v1.5/documents/_generated_logs.md |   59 -
 .../_generated_namespace_v1_concept.md        |  566 ----
 .../_generated_namespace_v1_definition.md     |   21 -
 .../_generated_namespacelist_v1_concept.md    |   96 -
 .../_generated_namespacelist_v1_definition.md |   19 -
 .../_generated_namespacespec_v1_concept.md    |   31 -
 .../_generated_namespacespec_v1_definition.md |   19 -
 .../_generated_namespacestatus_v1_concept.md  |  219 --
 ...generated_namespacestatus_v1_definition.md |   19 -
 ...generated_networkpolicy_v1beta1_concept.md |  685 -----
 ...erated_networkpolicy_v1beta1_definition.md |   20 -
 ...etworkpolicyingressrule_v1beta1_concept.md |   32 -
 ...orkpolicyingressrule_v1beta1_definition.md |   20 -
 ...rated_networkpolicylist_v1beta1_concept.md |   97 -
 ...ed_networkpolicylist_v1beta1_definition.md |   19 -
 ...rated_networkpolicypeer_v1beta1_concept.md |   32 -
 ...ed_networkpolicypeer_v1beta1_definition.md |   20 -
 ...rated_networkpolicyport_v1beta1_concept.md |   32 -
 ...ed_networkpolicyport_v1beta1_definition.md |   20 -
 ...rated_networkpolicyspec_v1beta1_concept.md |   32 -
 ...ed_networkpolicyspec_v1beta1_definition.md |   20 -
 .../documents/_generated_node_v1_concept.md   |  578 ----
 .../_generated_node_v1_definition.md          |   21 -
 .../_generated_nodeaddress_v1_concept.md      |   32 -
 .../_generated_nodeaddress_v1_definition.md   |   20 -
 .../_generated_nodecondition_v1_concept.md    |   36 -
 .../_generated_nodecondition_v1_definition.md |   24 -
 ...enerated_nodedaemonendpoints_v1_concept.md |   31 -
 ...rated_nodedaemonendpoints_v1_definition.md |   19 -
 .../_generated_nodelist_v1_concept.md         |   96 -
 .../_generated_nodelist_v1_definition.md      |   19 -
 .../_generated_nodespec_v1_concept.md         |   34 -
 .../_generated_nodespec_v1_definition.md      |   22 -
 .../_generated_nodestatus_v1_concept.md       |  228 --
 .../_generated_nodestatus_v1_definition.md    |   28 -
 .../_generated_nodesysteminfo_v1_concept.md   |   40 -
 ..._generated_nodesysteminfo_v1_definition.md |   28 -
 ...d_nonresourceattributes_v1beta1_concept.md |   32 -
 ...onresourceattributes_v1beta1_definition.md |   20 -
 ...enerated_objectfieldselector_v1_concept.md |   32 -
 ...rated_objectfieldselector_v1_definition.md |   20 -
 .../_generated_objectmeta_v1_concept.md       |   45 -
 .../_generated_objectmeta_v1_definition.md    |   33 -
 .../_generated_objectreference_v1_concept.md  |   37 -
 ...generated_objectreference_v1_definition.md |   25 -
 .../v1.5/documents/_generated_options.md      |   14 -
 .../_generated_ownerreference_v1_concept.md   |   35 -
 ..._generated_ownerreference_v1_definition.md |   23 -
 .../v1.5/documents/_generated_patch.md        |   61 -
 .../_generated_patch_unversioned_concept.md   |   29 -
 ..._generated_patch_unversioned_definition.md |   17 -
 .../_generated_persistentvolume_v1_concept.md |  631 -----
 ...enerated_persistentvolume_v1_definition.md |   21 -
 ...erated_persistentvolumeclaim_v1_concept.md |  946 -------
 ...ted_persistentvolumeclaim_v1_definition.md |   21 -
 ...ed_persistentvolumeclaimlist_v1_concept.md |   31 -
 ...persistentvolumeclaimlist_v1_definition.md |   19 -
 ...ed_persistentvolumeclaimspec_v1_concept.md |   34 -
 ...persistentvolumeclaimspec_v1_definition.md |   22 -
 ..._persistentvolumeclaimstatus_v1_concept.md |   33 -
 ...rsistentvolumeclaimstatus_v1_definition.md |   21 -
 ...nerated_persistentvolumelist_v1_concept.md |   31 -
 ...ated_persistentvolumelist_v1_definition.md |   19 -
 ...nerated_persistentvolumespec_v1_concept.md |   34 -
 ...ated_persistentvolumespec_v1_definition.md |   22 -
 ...rated_persistentvolumestatus_v1_concept.md |  221 --
 ...ed_persistentvolumestatus_v1_definition.md |   21 -
 .../documents/_generated_pod_v1_concept.md    | 1066 --------
 .../documents/_generated_pod_v1_definition.md |   21 -
 .../_generated_podcondition_v1_concept.md     |   36 -
 .../_generated_podcondition_v1_definition.md  |   24 -
 ...ted_poddisruptionbudget_v1beta1_concept.md |  761 ------
 ..._poddisruptionbudget_v1beta1_definition.md |   21 -
 ...poddisruptionbudgetlist_v1beta1_concept.md |   31 -
 ...disruptionbudgetlist_v1beta1_definition.md |   19 -
 ...poddisruptionbudgetspec_v1beta1_concept.md |   32 -
 ...disruptionbudgetspec_v1beta1_definition.md |   20 -
 ...ddisruptionbudgetstatus_v1beta1_concept.md |  227 --
 ...sruptionbudgetstatus_v1beta1_definition.md |   24 -
 .../_generated_podlist_v1_concept.md          |   31 -
 .../_generated_podlist_v1_definition.md       |   19 -
 ...generated_podsecuritycontext_v1_concept.md |   35 -
 ...erated_podsecuritycontext_v1_definition.md |   23 -
 .../_generated_podspec_v1_concept.md          |   47 -
 .../_generated_podspec_v1_definition.md       |   35 -
 .../_generated_podstatus_v1_concept.md        |   38 -
 .../_generated_podstatus_v1_definition.md     |   26 -
 .../_generated_podtemplate_v1_concept.md      |  685 -----
 .../_generated_podtemplate_v1_definition.md   |   20 -
 .../_generated_podtemplatelist_v1_concept.md  |   97 -
 ...generated_podtemplatelist_v1_definition.md |   19 -
 .../_generated_podtemplatespec_v1_concept.md  |   32 -
 ...generated_podtemplatespec_v1_definition.md |   20 -
 .../_generated_policyrule_v1alpha1_concept.md |   36 -
 ...enerated_policyrule_v1alpha1_definition.md |   24 -
 .../v1.5/documents/_generated_port-forward.md |   44 -
 .../_generated_preconditions_v1_concept.md    |   31 -
 .../_generated_preconditions_v1_definition.md |   19 -
 .../documents/_generated_probe_v1_concept.md  |   35 -
 .../_generated_probe_v1_definition.md         |   23 -
 .../v1.5/documents/_generated_proxy.md        |   62 -
 .../_generated_quantity_resource_concept.md   |   30 -
 ..._generated_quantity_resource_definition.md |   18 -
 ..._generated_rawextension_runtime_concept.md |   58 -
 ...nerated_rawextension_runtime_definition.md |   46 -
 .../v1.5/documents/_generated_replace.md      |   61 -
 .../_generated_replicaset_v1beta1_concept.md  | 1183 ---------
 ...generated_replicaset_v1beta1_definition.md |   21 -
 ...ted_replicasetcondition_v1beta1_concept.md |   35 -
 ..._replicasetcondition_v1beta1_definition.md |   23 -
 ...enerated_replicasetlist_v1beta1_concept.md |   31 -
 ...rated_replicasetlist_v1beta1_definition.md |   19 -
 ...enerated_replicasetspec_v1beta1_concept.md |   34 -
 ...rated_replicasetspec_v1beta1_definition.md |   22 -
 ...erated_replicasetstatus_v1beta1_concept.md |   36 -
 ...ted_replicasetstatus_v1beta1_definition.md |   24 -
 ...erated_replicationcontroller_v1_concept.md |  811 ------
 ...ted_replicationcontroller_v1_definition.md |   21 -
 ...plicationcontrollercondition_v1_concept.md |   35 -
 ...cationcontrollercondition_v1_definition.md |   23 -
 ...ed_replicationcontrollerlist_v1_concept.md |   31 -
 ...replicationcontrollerlist_v1_definition.md |   19 -
 ...ed_replicationcontrollerspec_v1_concept.md |   34 -
 ...replicationcontrollerspec_v1_definition.md |   22 -
 ..._replicationcontrollerstatus_v1_concept.md |  227 --
 ...plicationcontrollerstatus_v1_definition.md |   24 -
 ...ated_resourceattributes_v1beta1_concept.md |   37 -
 ...d_resourceattributes_v1beta1_definition.md |   25 -
 ...erated_resourcefieldselector_v1_concept.md |   33 -
 ...ted_resourcefieldselector_v1_definition.md |   21 -
 .../_generated_resourcequota_v1_concept.md    |  882 -------
 .../_generated_resourcequota_v1_definition.md |   21 -
 ..._generated_resourcequotalist_v1_concept.md |   97 -
 ...nerated_resourcequotalist_v1_definition.md |   19 -
 ..._generated_resourcequotaspec_v1_concept.md |   32 -
 ...nerated_resourcequotaspec_v1_definition.md |   20 -
 ...enerated_resourcequotastatus_v1_concept.md |   32 -
 ...rated_resourcequotastatus_v1_definition.md |   20 -
 ...nerated_resourcerequirements_v1_concept.md |   32 -
 ...ated_resourcerequirements_v1_definition.md |   20 -
 .../_generated_role_v1alpha1_concept.md       |  730 -----
 .../_generated_role_v1alpha1_definition.md    |   20 -
 ..._generated_rolebinding_v1alpha1_concept.md |  670 -----
 ...nerated_rolebinding_v1alpha1_definition.md |   21 -
 ...erated_rolebindinglist_v1alpha1_concept.md |   97 -
 ...ted_rolebindinglist_v1alpha1_definition.md |   19 -
 .../_generated_rolelist_v1alpha1_concept.md   |   31 -
 ..._generated_rolelist_v1alpha1_definition.md |   19 -
 .../_generated_roleref_v1alpha1_concept.md    |   33 -
 .../_generated_roleref_v1alpha1_definition.md |   21 -
 ...enerated_rollbackconfig_v1beta1_concept.md |   31 -
 ...rated_rollbackconfig_v1beta1_definition.md |   19 -
 .../documents/_generated_rolling-update.md    |   73 -
 ...rollingupdatedeployment_v1beta1_concept.md |   32 -
 ...lingupdatedeployment_v1beta1_definition.md |   20 -
 .../v1.5/documents/_generated_rollout.md      |  188 --
 .../kubectl/v1.5/documents/_generated_run.md  |  121 -
 .../v1.5/documents/_generated_scale.md        |   62 -
 .../documents/_generated_scale_v1_concept.md  |  237 --
 .../_generated_scale_v1_definition.md         |   20 -
 .../_generated_scale_v1beta1_concept.md       |   52 -
 .../_generated_scale_v1beta1_definition.md    |   20 -
 .../_generated_scalespec_v1_concept.md        |   31 -
 .../_generated_scalespec_v1_definition.md     |   19 -
 .../_generated_scalespec_v1beta1_concept.md   |   31 -
 ..._generated_scalespec_v1beta1_definition.md |   19 -
 .../_generated_scalestatus_v1_concept.md      |   32 -
 .../_generated_scalestatus_v1_definition.md   |   20 -
 .../_generated_scalestatus_v1beta1_concept.md |   33 -
 ...enerated_scalestatus_v1beta1_definition.md |   21 -
 .../documents/_generated_secret_v1_concept.md |  738 ------
 .../_generated_secret_v1_definition.md        |   22 -
 ..._generated_secretkeyselector_v1_concept.md |   31 -
 ...nerated_secretkeyselector_v1_definition.md |   19 -
 .../_generated_secretlist_v1_concept.md       |   31 -
 .../_generated_secretlist_v1_definition.md    |   19 -
 .../_generated_securitycontext_v1_concept.md  |   36 -
 ...generated_securitycontext_v1_definition.md |   24 -
 ...selfsubjectaccessreview_v1beta1_concept.md |  103 -
 ...fsubjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   32 -
 ...jectaccessreviewspec_v1beta1_definition.md |   20 -
 .../_generated_selinuxoptions_v1_concept.md   |   34 -
 ..._generated_selinuxoptions_v1_definition.md |   22 -
 ...addressbyclientcidr_unversioned_concept.md |   32 -
 ...ressbyclientcidr_unversioned_definition.md |   20 -
 .../_generated_service_v1_concept.md          | 1081 --------
 .../_generated_service_v1_definition.md       |   21 -
 .../_generated_serviceaccount_v1_concept.md   |  737 ------
 ..._generated_serviceaccount_v1_definition.md |   21 -
 ...generated_serviceaccountlist_v1_concept.md |   31 -
 ...erated_serviceaccountlist_v1_definition.md |   19 -
 .../_generated_servicelist_v1_concept.md      |   31 -
 .../_generated_servicelist_v1_definition.md   |   19 -
 .../_generated_serviceport_v1_concept.md      |   35 -
 .../_generated_serviceport_v1_definition.md   |   23 -
 .../_generated_servicespec_v1_concept.md      |   40 -
 .../_generated_servicespec_v1_definition.md   |   28 -
 .../_generated_servicestatus_v1_concept.md    |  222 --
 .../_generated_servicestatus_v1_definition.md |   19 -
 .../kubectl/v1.5/documents/_generated_set.md  |  142 -
 .../_generated_statefulset_v1beta1_concept.md |  949 -------
 ...enerated_statefulset_v1beta1_definition.md |   24 -
 ...nerated_statefulsetlist_v1beta1_concept.md |   31 -
 ...ated_statefulsetlist_v1beta1_definition.md |   19 -
 ...nerated_statefulsetspec_v1beta1_concept.md |   35 -
 ...ated_statefulsetspec_v1beta1_definition.md |   23 -
 ...rated_statefulsetstatus_v1beta1_concept.md |   32 -
 ...ed_statefulsetstatus_v1beta1_definition.md |   20 -
 .../_generated_status_unversioned_concept.md  |   35 -
 ...generated_status_unversioned_definition.md |   23 -
 ...nerated_statuscause_unversioned_concept.md |   33 -
 ...ated_statuscause_unversioned_definition.md |   21 -
 ...rated_statusdetails_unversioned_concept.md |   35 -
 ...ed_statusdetails_unversioned_definition.md |   23 -
 .../kubectl/v1.5/documents/_generated_stop.md |   52 -
 ..._generated_storageclass_v1beta1_concept.md |  550 ----
 ...nerated_storageclass_v1beta1_definition.md |   23 -
 ...erated_storageclasslist_v1beta1_concept.md |   96 -
 ...ted_storageclasslist_v1beta1_definition.md |   19 -
 .../_generated_subject_v1alpha1_concept.md    |   34 -
 .../_generated_subject_v1alpha1_definition.md |   22 -
 ...ted_subjectaccessreview_v1beta1_concept.md |  117 -
 ..._subjectaccessreview_v1beta1_definition.md |   20 -
 ...subjectaccessreviewspec_v1beta1_concept.md |   35 -
 ...jectaccessreviewspec_v1beta1_definition.md |   23 -
 ...bjectaccessreviewstatus_v1beta1_concept.md |   33 -
 ...ctaccessreviewstatus_v1beta1_definition.md |   21 -
 ...ed_subresourcereference_v1beta1_concept.md |   34 -
 ...subresourcereference_v1beta1_definition.md |   22 -
 .../v1.5/documents/_generated_taint.md        |   56 -
 .../_generated_tcpsocketaction_v1_concept.md  |   31 -
 ...generated_tcpsocketaction_v1_definition.md |   19 -
 ...ated_thirdpartyresource_v1beta1_concept.md |  548 ----
 ...d_thirdpartyresource_v1beta1_definition.md |   21 -
 ..._thirdpartyresourcelist_v1beta1_concept.md |   96 -
 ...irdpartyresourcelist_v1beta1_definition.md |   19 -
 .../_generated_time_unversioned_concept.md    |   30 -
 .../_generated_time_unversioned_definition.md |   18 -
 .../_generated_tokenreview_v1beta1_concept.md |  113 -
 ...enerated_tokenreview_v1beta1_definition.md |   20 -
 ...nerated_tokenreviewspec_v1beta1_concept.md |   31 -
 ...ated_tokenreviewspec_v1beta1_definition.md |   19 -
 ...rated_tokenreviewstatus_v1beta1_concept.md |   33 -
 ...ed_tokenreviewstatus_v1beta1_definition.md |   21 -
 .../kubectl/v1.5/documents/_generated_top.md  |  102 -
 .../v1.5/documents/_generated_uncordon.md     |   19 -
 .../_generated_userinfo_v1beta1_concept.md    |   34 -
 .../_generated_userinfo_v1beta1_definition.md |   22 -
 .../v1.5/documents/_generated_version.md      |   22 -
 .../documents/_generated_volume_v1_concept.md |   31 -
 .../_generated_volume_v1_definition.md        |   19 -
 .../_generated_volumemount_v1_concept.md      |   34 -
 .../_generated_volumemount_v1_definition.md   |   22 -
 .../v1.5/documents/_getting_started.md        |   11 -
 .../kubectl/v1.5/documents/_meta.md           |   12 -
 .../kubectl/v1.5/documents/_oldversions.md    |    3 -
 .../kubectl/v1.5/documents/_overview.md       |   92 -
 .../v1.5/documents/_servicediscovery.md       |   13 -
 .../v1.5/documents/_working_with_apps.md      |    8 -
 .../kubectl/v1.5/documents/_workloads.md      |   14 -
 .../v1.5/documents/deployment-original.md     |  518 ----
 .../kubectl/v1.5/documents/deployment.md      |  397 ---
 docs/user-guide/kubectl/v1.5/manifest.json    |  141 -
 docs/user-guide/kubectl/v1.5/runbrodocs.sh    |    6 -
 1561 files changed, 116607 deletions(-)
 delete mode 100644 docs/api-reference/v1.5/documents/_cluster.md
 delete mode 100644 docs/api-reference/v1.5/documents/_config.md
 delete mode 100644 docs/api-reference/v1.5/documents/_definitions.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_binding_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_binding_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_capabilities_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_capabilities_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentcondition_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentcondition_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmap_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmap_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmaplist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmaplist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_container_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_container_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerimage_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerimage_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerport_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerport_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstate_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstate_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_containerstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonset_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonset_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_daemonsetstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deleteoptions_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deleteoptions_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deployment_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deployment_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentcondition_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentcondition_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentrollback_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentrollback_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentstrategy_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_deploymentstrategy_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_downwardapivolumefile_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_downwardapivolumefile_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_downwardapivolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_downwardapivolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_emptydirvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_emptydirvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointaddress_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointaddress_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointport_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointport_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpoints_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpoints_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointslist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointslist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointsubset_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_endpointsubset_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_envvar_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_envvar_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_envvarsource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_envvarsource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_event_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_event_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_event_versioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_event_versioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eventlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eventlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eventsource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eventsource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eviction_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_eviction_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_execaction_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_execaction_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_fcvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_fcvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_flexvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_flexvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_flockervolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_flockervolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_gcepersistentdiskvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_gcepersistentdiskvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_gitrepovolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_gitrepovolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_glusterfsvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_glusterfsvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_groupversionfordiscovery_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_groupversionfordiscovery_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_handler_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_handler_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_hostpathvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_hostpathvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpgetaction_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpgetaction_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpheader_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpheader_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpingresspath_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpingresspath_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpingressrulevalue_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_httpingressrulevalue_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_info_version_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_info_version_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingress_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingress_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressbackend_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressbackend_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingresslist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingresslist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressrule_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressrule_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingressstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingresstls_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ingresstls_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_intorstring_intstr_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_intorstring_intstr_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_iscsivolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_iscsivolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_job_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobcondition_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_joblist_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobspec_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobstatus_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobtemplatespec_v2alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_jobtemplatespec_v2alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_keytopath_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_keytopath_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_labelselector_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_labelselector_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_labelselectorrequirement_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_labelselectorrequirement_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_lifecycle_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_lifecycle_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrange_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrange_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangeitem_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangeitem_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_limitrangespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_listmeta_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_listmeta_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_loadbalanceringress_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_loadbalanceringress_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_loadbalancerstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_loadbalancerstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_localobjectreference_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_localobjectreference_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespace_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespace_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacestatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_namespacestatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicy_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicy_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicylist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicylist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicypeer_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicypeer_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyport_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyport_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_networkpolicyspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nfsvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nfsvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_node_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_node_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodeaddress_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodeaddress_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodecondition_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodecondition_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodedaemonendpoints_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodedaemonendpoints_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodestatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodestatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodesysteminfo_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nodesysteminfo_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nonresourceattributes_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_nonresourceattributes_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectfieldselector_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectfieldselector_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectmeta_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectmeta_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectreference_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_objectreference_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ownerreference_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_ownerreference_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_patch_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_patch_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolume_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolume_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaim_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaim_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumeclaimvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumestatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_persistentvolumestatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_photonpersistentdiskvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_photonpersistentdiskvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_pod_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_pod_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podcondition_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podcondition_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudget_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudget_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podsecuritycontext_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podsecuritycontext_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplate_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplate_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplatelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplatelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplatespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_podtemplatespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_policyrule_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_policyrule_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_preconditions_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_preconditions_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_probe_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_probe_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_quantity_resource_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_quantity_resource_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_quobytevolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_quobytevolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rawextension_runtime_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rawextension_runtime_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rbdvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rbdvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicaset_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicaset_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetcondition_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetcondition_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicasetstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontroller_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontroller_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollercondition_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollercondition_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerstatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_replicationcontrollerstatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourceattributes_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourceattributes_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcefieldselector_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcefieldselector_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequota_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequota_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotalist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotalist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotaspec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotaspec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotastatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcequotastatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcerequirements_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_resourcerequirements_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_role_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_role_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolebinding_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolebinding_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolelist_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rolelist_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_roleref_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_roleref_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rollbackconfig_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rollbackconfig_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scale_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scale_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scale_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scale_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalespec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalespec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalestatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalestatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalestatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_scalestatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secret_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secret_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretkeyselector_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretkeyselector_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_secretvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_securitycontext_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_securitycontext_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selinuxoptions_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_selinuxoptions_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_service_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_service_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceaccount_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceaccount_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceaccountlist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceaccountlist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicelist_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicelist_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceport_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_serviceport_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicespec_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicespec_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicestatus_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_servicestatus_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulset_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulset_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetlist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetlist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statefulsetstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_status_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_status_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statuscause_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statuscause_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statusdetails_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_statusdetails_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_storageclass_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_storageclass_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_storageclasslist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_storageclasslist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subject_v1alpha1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subject_v1alpha1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subresourcereference_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_subresourcereference_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tcpsocketaction_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tcpsocketaction_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_thirdpartyresource_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_thirdpartyresource_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_time_unversioned_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_time_unversioned_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreview_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreview_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreviewspec_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreviewspec_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_tokenreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_userinfo_v1beta1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_userinfo_v1beta1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_volume_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_volume_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_volumemount_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_volumemount_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_vspherevirtualdiskvolumesource_v1_concept.md
 delete mode 100644 docs/api-reference/v1.5/documents/_generated_vspherevirtualdiskvolumesource_v1_definition.md
 delete mode 100644 docs/api-reference/v1.5/documents/_meta.md
 delete mode 100644 docs/api-reference/v1.5/documents/_oldversions.md
 delete mode 100644 docs/api-reference/v1.5/documents/_overview.md
 delete mode 100644 docs/api-reference/v1.5/documents/_servicediscovery.md
 delete mode 100644 docs/api-reference/v1.5/documents/_workloads.md
 delete mode 100644 docs/api-reference/v1.5/documents/deployment-original.md
 delete mode 100644 docs/api-reference/v1.5/documents/deployment.md
 delete mode 100644 docs/api-reference/v1.5/manifest.json
 delete mode 100755 docs/api-reference/v1.5/runbrodocs.sh
 delete mode 100644 docs/resources-reference/v1.5/documents/_cluster.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_config.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_definitions.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apigroup_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apigroup_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apigrouplist_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apigrouplist_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiresource_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiresource_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiversion_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiversion_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiversions_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_apiversions_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_attachedvolume_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_attachedvolume_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_azurediskvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_azurediskvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_azurefilevolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_azurefilevolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_binding_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_binding_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_capabilities_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_capabilities_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cephfsvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cephfsvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cindervolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cindervolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentcondition_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentcondition_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentstatuslist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_componentstatuslist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmap_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmap_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmapkeyselector_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmapkeyselector_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmaplist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmaplist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmapvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_configmapvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_container_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_container_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerimage_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerimage_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerport_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerport_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstate_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstate_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstaterunning_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstaterunning_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstateterminated_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstateterminated_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstatewaiting_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstatewaiting_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_containerstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjob_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjob_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonendpoint_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonendpoint_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonset_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonset_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_daemonsetstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deleteoptions_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deleteoptions_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deployment_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deployment_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentcondition_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentcondition_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentrollback_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentrollback_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentstrategy_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_deploymentstrategy_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_downwardapivolumefile_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_downwardapivolumefile_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_downwardapivolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_downwardapivolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_emptydirvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_emptydirvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointaddress_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointaddress_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointport_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointport_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpoints_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpoints_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointslist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointslist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointsubset_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_endpointsubset_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_envvar_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_envvar_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_envvarsource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_envvarsource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_event_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_event_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_event_versioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_event_versioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eventlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eventlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eventsource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eventsource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eviction_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_eviction_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_execaction_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_execaction_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_fcvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_fcvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_flexvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_flexvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_flockervolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_flockervolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_gcepersistentdiskvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_gcepersistentdiskvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_gitrepovolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_gitrepovolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_glusterfsvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_glusterfsvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_groupversionfordiscovery_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_groupversionfordiscovery_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_handler_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_handler_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_hostpathvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_hostpathvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpgetaction_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpgetaction_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpheader_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpheader_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpingresspath_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpingresspath_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpingressrulevalue_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_httpingressrulevalue_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_info_version_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_info_version_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingress_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingress_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressbackend_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressbackend_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingresslist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingresslist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressrule_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressrule_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingressstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingresstls_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ingresstls_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_intorstring_intstr_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_intorstring_intstr_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_iscsivolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_iscsivolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_job_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobcondition_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_joblist_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobspec_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobstatus_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobtemplatespec_v2alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_jobtemplatespec_v2alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_keytopath_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_keytopath_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_labelselector_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_labelselector_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_labelselectorrequirement_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_labelselectorrequirement_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_lifecycle_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_lifecycle_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrange_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrange_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangeitem_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangeitem_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_limitrangespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_listmeta_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_listmeta_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_loadbalanceringress_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_loadbalanceringress_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_loadbalancerstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_loadbalancerstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_localobjectreference_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_localobjectreference_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespace_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespace_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacestatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_namespacestatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicy_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicy_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicylist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicylist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicypeer_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicypeer_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyport_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyport_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_networkpolicyspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nfsvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nfsvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_node_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_node_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodeaddress_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodeaddress_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodecondition_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodecondition_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodedaemonendpoints_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodedaemonendpoints_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodestatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodestatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodesysteminfo_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nodesysteminfo_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nonresourceattributes_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_nonresourceattributes_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectfieldselector_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectfieldselector_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectmeta_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectmeta_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectreference_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_objectreference_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ownerreference_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_ownerreference_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_patch_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_patch_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolume_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolume_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaim_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaim_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumeclaimvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumestatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_persistentvolumestatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_photonpersistentdiskvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_photonpersistentdiskvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_pod_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_pod_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podcondition_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podcondition_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudget_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudget_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podsecuritycontext_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podsecuritycontext_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplate_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplate_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplatelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplatelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplatespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_podtemplatespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_policyrule_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_policyrule_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_preconditions_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_preconditions_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_probe_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_probe_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_quantity_resource_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_quantity_resource_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_quobytevolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_quobytevolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rawextension_runtime_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rawextension_runtime_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rbdvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rbdvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicaset_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicaset_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetcondition_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetcondition_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicasetstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontroller_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontroller_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollercondition_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollercondition_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerstatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_replicationcontrollerstatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourceattributes_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourceattributes_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcefieldselector_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcefieldselector_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequota_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequota_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotalist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotalist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotaspec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotaspec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotastatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcequotastatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcerequirements_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_resourcerequirements_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_role_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_role_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolebinding_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolebinding_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolelist_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rolelist_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_roleref_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_roleref_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rollbackconfig_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rollbackconfig_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scale_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scale_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scale_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scale_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalespec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalespec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalestatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalestatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalestatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_scalestatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secret_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secret_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretkeyselector_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretkeyselector_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_secretvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_securitycontext_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_securitycontext_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selinuxoptions_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_selinuxoptions_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_service_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_service_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceaccount_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceaccount_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceaccountlist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceaccountlist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicelist_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicelist_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceport_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_serviceport_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicespec_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicespec_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicestatus_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_servicestatus_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulset_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulset_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetlist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetlist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statefulsetstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_status_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_status_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statuscause_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statuscause_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statusdetails_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_statusdetails_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_storageclass_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_storageclass_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_storageclasslist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_storageclasslist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subject_v1alpha1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subject_v1alpha1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subresourcereference_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_subresourcereference_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tcpsocketaction_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tcpsocketaction_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_thirdpartyresource_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_thirdpartyresource_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_time_unversioned_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_time_unversioned_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreview_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreview_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreviewspec_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreviewspec_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_tokenreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_userinfo_v1beta1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_userinfo_v1beta1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_volume_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_volume_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_volumemount_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_volumemount_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_vspherevirtualdiskvolumesource_v1_concept.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_generated_vspherevirtualdiskvolumesource_v1_definition.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_meta.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_oldversions.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_overview.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_servicediscovery.md
 delete mode 100644 docs/resources-reference/v1.5/documents/_workloads.md
 delete mode 100644 docs/resources-reference/v1.5/documents/deployment-original.md
 delete mode 100644 docs/resources-reference/v1.5/documents/deployment.md
 delete mode 100644 docs/resources-reference/v1.5/manifest.json
 delete mode 100755 docs/resources-reference/v1.5/runbrodocs.sh
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_app_management.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_cluster.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_config.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_definitions.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_annotate.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_api-versions.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apigroup_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apigroup_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apigrouplist_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apigrouplist_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiresource_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiresource_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiversion_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiversion_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiversions_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apiversions_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_apply.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_attach.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_attachedvolume_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_attachedvolume_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_autoscale.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_binding_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_binding_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_capabilities_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_capabilities_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_category_cluster_management.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_category_declarative_app_management.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_category_deprecated_commands.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_category_kubectl_settings_and_usage.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificate.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_cluster-info.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_completion.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentcondition_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentcondition_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentstatuslist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_componentstatuslist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_config.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmap_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmap_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmapkeyselector_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmapkeyselector_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmaplist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_configmaplist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_container_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_container_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerimage_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerimage_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerport_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerport_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstate_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstate_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstaterunning_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstaterunning_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstateterminated_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstateterminated_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstatewaiting_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstatewaiting_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_containerstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_convert.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_cordon.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_cp.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_create.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonendpoint_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonendpoint_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonset_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonset_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_daemonsetstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_delete.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deleteoptions_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deleteoptions_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deployment_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deployment_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentcondition_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentcondition_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentrollback_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentrollback_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentstrategy_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_deploymentstrategy_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_describe.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_drain.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_edit.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointaddress_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointaddress_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointport_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointport_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpoints_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpoints_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointslist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointslist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointsubset_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_endpointsubset_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_envvar_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_envvar_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_envvarsource_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_envvarsource_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_event_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_event_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_event_versioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_event_versioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eventlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eventlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eventsource_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eventsource_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eviction_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_eviction_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_exec.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_execaction_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_execaction_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_explain.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_expose.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_get.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_groupversionfordiscovery_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_groupversionfordiscovery_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_handler_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_handler_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscaler_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscaler_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscaler_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_horizontalpodautoscalerstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_httpgetaction_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_httpgetaction_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_httpheader_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_httpheader_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_info_version_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_info_version_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingress_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingress_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressbackend_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressbackend_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingresslist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingresslist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressrule_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressrule_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingressstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingresstls_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ingresstls_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_intorstring_intstr_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_intorstring_intstr_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_job_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_job_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_job_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_job_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobcondition_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobcondition_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobcondition_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobcondition_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_joblist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_joblist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_joblist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_joblist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_jobstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_label.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_labelselector_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_labelselector_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_labelselectorrequirement_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_labelselectorrequirement_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_lifecycle_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_lifecycle_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrange_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrange_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangeitem_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangeitem_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_limitrangespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_listmeta_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_listmeta_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_loadbalanceringress_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_loadbalanceringress_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_loadbalancerstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_loadbalancerstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_localobjectreference_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_localobjectreference_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_localsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_logs.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespace_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespace_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacestatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_namespacestatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicy_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicy_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyingressrule_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicylist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicylist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicypeer_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicypeer_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyport_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyport_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_networkpolicyspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_node_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_node_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodeaddress_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodeaddress_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodecondition_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodecondition_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodedaemonendpoints_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodedaemonendpoints_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodestatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodestatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodesysteminfo_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nodesysteminfo_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nonresourceattributes_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_nonresourceattributes_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectfieldselector_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectfieldselector_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectmeta_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectmeta_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectreference_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_objectreference_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_options.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ownerreference_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_ownerreference_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_patch.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_patch_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_patch_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolume_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolume_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaim_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaim_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumeclaimstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumestatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_persistentvolumestatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_pod_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podcondition_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podcondition_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudget_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudget_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_poddisruptionbudgetstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podsecuritycontext_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podsecuritycontext_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplate_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplate_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplatelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplatelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplatespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_podtemplatespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_policyrule_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_policyrule_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_port-forward.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_preconditions_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_preconditions_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_probe_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_probe_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_proxy.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_quantity_resource_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_quantity_resource_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rawextension_runtime_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rawextension_runtime_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replace.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicaset_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicaset_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetcondition_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetcondition_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicasetstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontroller_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontroller_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollercondition_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollercondition_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerstatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_replicationcontrollerstatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourceattributes_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourceattributes_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcefieldselector_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcefieldselector_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequota_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequota_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotalist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotalist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotaspec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotaspec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotastatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcequotastatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcerequirements_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_resourcerequirements_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_role_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_role_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolebinding_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolebinding_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolebindinglist_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolebindinglist_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolelist_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolelist_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_roleref_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_roleref_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rollbackconfig_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rollbackconfig_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rolling-update.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rollingupdatedeployment_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_rollout.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_run.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scale.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scale_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scale_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scale_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scale_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalespec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalespec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalestatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalestatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalestatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_scalestatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secret_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secret_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secretkeyselector_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secretkeyselector_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secretlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_secretlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_securitycontext_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_securitycontext_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selfsubjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selfsubjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selinuxoptions_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_selinuxoptions_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serveraddressbyclientcidr_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_service_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_service_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceaccount_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceaccount_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceaccountlist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceaccountlist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicelist_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicelist_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceport_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_serviceport_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicespec_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicespec_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicestatus_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_servicestatus_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_set.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulset_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulset_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetlist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetlist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statefulsetstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_status_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_status_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statuscause_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statuscause_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statusdetails_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_statusdetails_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_stop.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_storageclass_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_storageclass_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_storageclasslist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_storageclasslist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subject_v1alpha1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subject_v1alpha1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreview_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreview_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreviewspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subjectaccessreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subresourcereference_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_subresourcereference_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_taint.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tcpsocketaction_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tcpsocketaction_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_thirdpartyresource_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_thirdpartyresource_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_thirdpartyresourcelist_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_time_unversioned_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_time_unversioned_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreview_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreview_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreviewspec_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreviewspec_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreviewstatus_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_tokenreviewstatus_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_top.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_uncordon.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_userinfo_v1beta1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_userinfo_v1beta1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_version.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_volume_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_volume_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_volumemount_v1_concept.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_generated_volumemount_v1_definition.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_getting_started.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_meta.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_oldversions.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_overview.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_servicediscovery.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_working_with_apps.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/_workloads.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/deployment-original.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/documents/deployment.md
 delete mode 100644 docs/user-guide/kubectl/v1.5/manifest.json
 delete mode 100755 docs/user-guide/kubectl/v1.5/runbrodocs.sh

diff --git a/docs/api-reference/v1.5/documents/_cluster.md b/docs/api-reference/v1.5/documents/_cluster.md
deleted file mode 100644
index 5c74168efb..0000000000
--- a/docs/api-reference/v1.5/documents/_cluster.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# CLUSTER
-
-Cluster resources are responsible for defining configuration of the cluster itself, and are generally only used by cluster operators.
-
-------------
diff --git a/docs/api-reference/v1.5/documents/_config.md b/docs/api-reference/v1.5/documents/_config.md
deleted file mode 100644
index 555578e2b3..0000000000
--- a/docs/api-reference/v1.5/documents/_config.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# CONFIG & STORAGE
-
-Config and Storage resources are responsible for injecting data into your applications and persisting data externally to your container.
-
-Common resource types:
-
-- [ConfigMaps](#configmap-v1) for providing text key value pairs injected into the application through environment variables, command line arguments, or files
-- [Secrets](#secret-v1) for providing binary data injected into the application through files
-- [Volumes](#volume-v1) for providing a filesystem external to the Container.  Maybe shared across Containers within the same Pod and have a lifetime persisting beyond a Container or Pod.
-
-------------
diff --git a/docs/api-reference/v1.5/documents/_definitions.md b/docs/api-reference/v1.5/documents/_definitions.md
deleted file mode 100644
index 337695b8d5..0000000000
--- a/docs/api-reference/v1.5/documents/_definitions.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# DEFINITIONS
-
-This section contains definitions for objects used in the Kubernetes APIs.
diff --git a/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_concept.md b/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_concept.md
deleted file mode 100644
index d4732c1cea..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_concept.md
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
------------
-# APIGroup unversioned
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIGroup
-
-
-
-
-
-
-
-APIGroup contains the name, the supported versions, and the preferred version of a group.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-name 
     *string*  | name is the name of the group.
-preferredVersion 
     *[GroupVersionForDiscovery](#groupversionfordiscovery-unversioned)*  | preferredVersion is the version preferred by the API server, which probably is the storage version.
-serverAddressByClientCIDRs 
     *[ServerAddressByClientCIDR](#serveraddressbyclientcidr-unversioned) array*  | a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
-versions 
     *[GroupVersionForDiscovery](#groupversionfordiscovery-unversioned) array*  | versions are the versions supported in this group.
-
-
-### APIGroupList unversioned
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groups 
     *[APIGroup](#apigroup-unversioned) array*  | groups is a list of APIGroup.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_definition.md b/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_definition.md
deleted file mode 100644
index d6d1173eb5..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apigroup_unversioned_definition.md
+++ /dev/null
@@ -1,22 +0,0 @@
-## APIGroup unversioned
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIGroup
-
-
-
-APIGroup contains the name, the supported versions, and the preferred version of a group.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-name 
     *string*  | name is the name of the group.
-preferredVersion 
     *[GroupVersionForDiscovery](#groupversionfordiscovery-unversioned)*  | preferredVersion is the version preferred by the API server, which probably is the storage version.
-serverAddressByClientCIDRs 
     *[ServerAddressByClientCIDR](#serveraddressbyclientcidr-unversioned) array*  | a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
-versions 
     *[GroupVersionForDiscovery](#groupversionfordiscovery-unversioned) array*  | versions are the versions supported in this group.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_concept.md b/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_concept.md
deleted file mode 100644
index 99c9d0d8fe..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# APIGroupList unversioned
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIGroupList
-
-
-
-
-
-
-
-APIGroupList is a list of APIGroup, to allow clients to discover the API at /apis.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groups 
     *[APIGroup](#apigroup-unversioned) array*  | groups is a list of APIGroup.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_definition.md b/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_definition.md
deleted file mode 100644
index 6267bf8f48..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apigrouplist_unversioned_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## APIGroupList unversioned
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIGroupList
-
-
-
-APIGroupList is a list of APIGroup, to allow clients to discover the API at /apis.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groups 
     *[APIGroup](#apigroup-unversioned) array*  | groups is a list of APIGroup.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_concept.md b/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_concept.md
deleted file mode 100644
index 2f87ebff79..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_concept.md
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
------------
-# APIResource unversioned
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIResource
-
-
-
-
-
-
-
-APIResource specifies the name of a resource and whether it is namespaced.
-
-
-
-Field        | Description
------------- | -----------
-kind 
     *string*  | kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')
-name 
     *string*  | name is the name of the resource.
-namespaced 
     *boolean*  | namespaced indicates if a resource is namespaced or not.
-
-
-### APIResourceList unversioned
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groupVersion 
     *string*  | groupVersion is the group and version this APIResourceList is for.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-resources 
     *[APIResource](#apiresource-unversioned) array*  | resources contains the name of the resources and if they are namespaced.
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_definition.md b/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_definition.md
deleted file mode 100644
index dd9cd0a727..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiresource_unversioned_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## APIResource unversioned
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIResource
-
-
-
-APIResource specifies the name of a resource and whether it is namespaced.
-
-
-
-Field        | Description
------------- | -----------
-kind 
     *string*  | kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')
-name 
     *string*  | name is the name of the resource.
-namespaced 
     *boolean*  | namespaced indicates if a resource is namespaced or not.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md b/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md
deleted file mode 100644
index 5bb170d54c..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# APIResourceList unversioned
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIResourceList
-
-
-
-
-
-
-
-APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groupVersion 
     *string*  | groupVersion is the group and version this APIResourceList is for.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-resources 
     *[APIResource](#apiresource-unversioned) array*  | resources contains the name of the resources and if they are namespaced.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md b/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md
deleted file mode 100644
index b5b7649e2f..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiresourcelist_unversioned_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## APIResourceList unversioned
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIResourceList
-
-
-
-APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-groupVersion 
     *string*  | groupVersion is the group and version this APIResourceList is for.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-resources 
     *[APIResource](#apiresource-unversioned) array*  | resources contains the name of the resources and if they are namespaced.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_concept.md b/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_concept.md
deleted file mode 100644
index eed2e554dc..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_concept.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
------------
-# APIVersion v1beta1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1beta1 | APIVersion
-
-
-
-
-
-
-
-An APIVersion represents a single concrete version of an object model.
-
-
-
-Field        | Description
------------- | -----------
-name 
     *string*  | Name of this version (e.g. 'v1').
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_definition.md b/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_definition.md
deleted file mode 100644
index aecfdceaf7..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiversion_v1beta1_definition.md
+++ /dev/null
@@ -1,17 +0,0 @@
-## APIVersion v1beta1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1beta1 | APIVersion
-
-
-
-An APIVersion represents a single concrete version of an object model.
-
-
-
-Field        | Description
------------- | -----------
-name 
     *string*  | Name of this version (e.g. 'v1').
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_concept.md b/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_concept.md
deleted file mode 100644
index 31aa6a658a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# APIVersions unversioned
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIVersions
-
-
-
-
-
-
-
-APIVersions lists the versions that are available, to allow clients to discover the API at /api, which is the root path of the legacy v1 API.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-serverAddressByClientCIDRs 
     *[ServerAddressByClientCIDR](#serveraddressbyclientcidr-unversioned) array*  | a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
-versions 
     *string array*  | versions are the api versions that are available.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_definition.md b/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_definition.md
deleted file mode 100644
index 3513f89da7..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_apiversions_unversioned_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## APIVersions unversioned
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | unversioned | APIVersions
-
-
-
-APIVersions lists the versions that are available, to allow clients to discover the API at /api, which is the root path of the legacy v1 API.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-serverAddressByClientCIDRs 
     *[ServerAddressByClientCIDR](#serveraddressbyclientcidr-unversioned) array*  | a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.
-versions 
     *string array*  | versions are the api versions that are available.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_concept.md
deleted file mode 100644
index 7ec6b04185..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# AttachedVolume v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AttachedVolume
-
-
-
-
-
-
-
-AttachedVolume describes a volume attached to a node
-
-
-
-Field        | Description
------------- | -----------
-devicePath 
     *string*  | DevicePath represents the device path where the volume should be available
-name 
     *string*  | Name of the attached volume
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_definition.md
deleted file mode 100644
index ae5004c11a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_attachedvolume_v1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## AttachedVolume v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AttachedVolume
-
-
-
-AttachedVolume describes a volume attached to a node
-
-
-
-Field        | Description
------------- | -----------
-devicePath 
     *string*  | DevicePath represents the device path where the volume should be available
-name 
     *string*  | Name of the attached volume
-
diff --git a/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_concept.md
deleted file mode 100644
index 9dda8fcf2a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_concept.md
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
------------
-# AWSElasticBlockStoreVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AWSElasticBlockStoreVolumeSource
-
-
-
-
-
-
-
-Represents a Persistent Disk resource in AWS.
-
-An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-fsType 
     *string*  | Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-partition 
     *integer*  | The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty).
-readOnly 
     *boolean*  | Specify "true" to force and set the ReadOnly property in VolumeMounts to "true". If omitted, the default is "false". More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-volumeID 
     *string*  | Unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_definition.md
deleted file mode 100644
index 3c4d7e2d21..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_awselasticblockstorevolumesource_v1_definition.md
+++ /dev/null
@@ -1,22 +0,0 @@
-## AWSElasticBlockStoreVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AWSElasticBlockStoreVolumeSource
-
-
-
-Represents a Persistent Disk resource in AWS.
-
-An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-fsType 
     *string*  | Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-partition 
     *integer*  | The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty).
-readOnly 
     *boolean*  | Specify "true" to force and set the ReadOnly property in VolumeMounts to "true". If omitted, the default is "false". More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-volumeID 
     *string*  | Unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: http://kubernetes.io/docs/user-guide/volumes#awselasticblockstore
-
diff --git a/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_concept.md
deleted file mode 100644
index 1043b9d9ae..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_concept.md
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
------------
-# AzureDiskVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AzureDiskVolumeSource
-
-
-
-
-
-
-
-AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.
-
-
-
-Field        | Description
------------- | -----------
-cachingMode 
     *string*  | Host Caching mode: None, Read Only, Read Write.
-diskName 
     *string*  | The Name of the data disk in the blob storage
-diskURI 
     *string*  | The URI the data disk in the blob storage
-fsType 
     *string*  | Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
-readOnly 
     *boolean*  | Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_definition.md
deleted file mode 100644
index 191a407952..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_azurediskvolumesource_v1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## AzureDiskVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AzureDiskVolumeSource
-
-
-
-AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.
-
-
-
-Field        | Description
------------- | -----------
-cachingMode 
     *string*  | Host Caching mode: None, Read Only, Read Write.
-diskName 
     *string*  | The Name of the data disk in the blob storage
-diskURI 
     *string*  | The URI the data disk in the blob storage
-fsType 
     *string*  | Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified.
-readOnly 
     *boolean*  | Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_concept.md
deleted file mode 100644
index a9dc6186b1..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# AzureFileVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AzureFileVolumeSource
-
-
-
-
-
-
-
-AzureFile represents an Azure File Service mount on the host and bind mount to the pod.
-
-
-
-Field        | Description
------------- | -----------
-readOnly 
     *boolean*  | Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
-secretName 
     *string*  | the name of secret that contains Azure Storage Account Name and Key
-shareName 
     *string*  | Share Name
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_definition.md
deleted file mode 100644
index 2382e73e4c..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_azurefilevolumesource_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## AzureFileVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | AzureFileVolumeSource
-
-
-
-AzureFile represents an Azure File Service mount on the host and bind mount to the pod.
-
-
-
-Field        | Description
------------- | -----------
-readOnly 
     *boolean*  | Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.
-secretName 
     *string*  | the name of secret that contains Azure Storage Account Name and Key
-shareName 
     *string*  | Share Name
-
diff --git a/docs/api-reference/v1.5/documents/_generated_binding_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_binding_v1_concept.md
deleted file mode 100644
index 6c7d6bf32a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_binding_v1_concept.md
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
------------
-# Binding v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Binding
-
-
-
-
-
-
-
-Binding ties one object to another. For example, a pod is bound to a node by a scheduler.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-target 
     *[ObjectReference](#objectreference-v1)*  | The target object that you want to bind to the standard object.
-
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a Binding
-
-### HTTP Request
-
-`POST /api/v1/namespaces/{namespace}/bindings`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Binding](#binding-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Binding](#binding-v1)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_binding_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_binding_v1_definition.md
deleted file mode 100644
index 32e2a31908..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_binding_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## Binding v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Binding
-
-
-
-Binding ties one object to another. For example, a pod is bound to a node by a scheduler.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-target 
     *[ObjectReference](#objectreference-v1)*  | The target object that you want to bind to the standard object.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_capabilities_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_capabilities_v1_concept.md
deleted file mode 100644
index 6c47def7ef..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_capabilities_v1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# Capabilities v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Capabilities
-
-
-
-
-
-
-
-Adds and removes POSIX capabilities from running containers.
-
-
-
-Field        | Description
------------- | -----------
-add 
     *string array*  | Added capabilities
-drop 
     *string array*  | Removed capabilities
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_capabilities_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_capabilities_v1_definition.md
deleted file mode 100644
index c18460bf9a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_capabilities_v1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## Capabilities v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Capabilities
-
-
-
-Adds and removes POSIX capabilities from running containers.
-
-
-
-Field        | Description
------------- | -----------
-add 
     *string array*  | Added capabilities
-drop 
     *string array*  | Removed capabilities
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_concept.md
deleted file mode 100644
index 1911dac73b..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_concept.md
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
------------
-# CephFSVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CephFSVolumeSource
-
-
-
-
-
-
-
-Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-monitors 
     *string array*  | Required: Monitors is a collection of Ceph monitors More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-path 
     *string*  | Optional: Used as the mounted root, rather than the full Ceph tree, default is /
-readOnly 
     *boolean*  | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-secretFile 
     *string*  | Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-secretRef 
     *[LocalObjectReference](#localobjectreference-v1)*  | Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-user 
     *string*  | Optional: User is the rados user name, default is admin More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_definition.md
deleted file mode 100644
index d672f53c08..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cephfsvolumesource_v1_definition.md
+++ /dev/null
@@ -1,22 +0,0 @@
-## CephFSVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CephFSVolumeSource
-
-
-
-Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-monitors 
     *string array*  | Required: Monitors is a collection of Ceph monitors More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-path 
     *string*  | Optional: Used as the mounted root, rather than the full Ceph tree, default is /
-readOnly 
     *boolean*  | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-secretFile 
     *string*  | Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-secretRef 
     *[LocalObjectReference](#localobjectreference-v1)*  | Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-user 
     *string*  | Optional: User is the rados user name, default is admin More info: http://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md
deleted file mode 100644
index 3906344d6e..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_concept.md
+++ /dev/null
@@ -1,590 +0,0 @@
-
-
------------
-# CertificateSigningRequest v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequest
-
-
-
-
-
-
-
-Describes a certificate signing request
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | 
-spec 
     *[CertificateSigningRequestSpec](#certificatesigningrequestspec-v1alpha1)*  | The certificate request itself and any additional information.
-status 
     *[CertificateSigningRequestStatus](#certificatesigningrequeststatus-v1alpha1)*  | Derived information about the request.
-
-
-### CertificateSigningRequestSpec v1alpha1
-
-
-
-Field        | Description
------------- | -----------
-groups 
     *string array*  | 
-request 
     *string*  | Base64-encoded PKCS#10 CSR data
-uid 
     *string*  | 
-username 
     *string*  | Information about the requesting user (if relevant) See user.Info interface for details
-
-### CertificateSigningRequestStatus v1alpha1
-
-
-
-Field        | Description
------------- | -----------
-certificate 
     *string*  | If request was approved, the controller will place the issued certificate here.
-conditions 
     *[CertificateSigningRequestCondition](#certificatesigningrequestcondition-v1alpha1) array*  | Conditions applied to the request, such as approval or denial.
-
-### CertificateSigningRequestList v1alpha1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1) array*  | 
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | 
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a CertificateSigningRequest
-
-### HTTP Request
-
-`POST /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | OK
-
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace the specified CertificateSigningRequest
-
-### HTTP Request
-
-`PUT /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | OK
-
-
-## Patch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update the specified CertificateSigningRequest
-
-### HTTP Request
-
-`PATCH /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | OK
-
-
-## Delete
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete a CertificateSigningRequest
-
-### HTTP Request
-
-`DELETE /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-gracePeriodSeconds  | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-orphanDependents  | Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[DeleteOptions](#deleteoptions-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-## Delete Collection
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete collection of CertificateSigningRequest
-
-### HTTP Request
-
-`DELETE /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified CertificateSigningRequest
-
-### HTTP Request
-
-`GET /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-exact  | Should the export be exact.  Exact export maintains cluster-specific fields like 'Namespace'
-export  | Should this value be exported.  Export strips fields that a user can not specify.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind CertificateSigningRequest
-
-### HTTP Request
-
-`GET /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequestList](#certificatesigningrequestlist-v1alpha1)*  | OK
-
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch changes to an object of kind CertificateSigningRequest
-
-### HTTP Request
-
-`GET /apis/certificates.k8s.io/v1alpha1/watch/certificatesigningrequests/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md
deleted file mode 100644
index 273683ba2f..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequest_v1alpha1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## CertificateSigningRequest v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequest
-
-
-
-Describes a certificate signing request
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | 
-spec 
     *[CertificateSigningRequestSpec](#certificatesigningrequestspec-v1alpha1)*  | The certificate request itself and any additional information.
-status 
     *[CertificateSigningRequestStatus](#certificatesigningrequeststatus-v1alpha1)*  | Derived information about the request.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md
deleted file mode 100644
index b11023903e..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_concept.md
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
------------
-# CertificateSigningRequestCondition v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | CertificateSigningRequestCondition
-
-
-
-
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-lastUpdateTime 
     *[Time](#time-unversioned)*  | timestamp for the last update to this condition
-message 
     *string*  | human readable message with details about the request state
-reason 
     *string*  | brief reason for the request state
-type 
     *string*  | request approval state, currently Approved or Denied.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md
deleted file mode 100644
index 4d6c34b60b..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestcondition_v1alpha1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## CertificateSigningRequestCondition v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | CertificateSigningRequestCondition
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-lastUpdateTime 
     *[Time](#time-unversioned)*  | timestamp for the last update to this condition
-message 
     *string*  | human readable message with details about the request state
-reason 
     *string*  | brief reason for the request state
-type 
     *string*  | request approval state, currently Approved or Denied.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md
deleted file mode 100644
index 0fadb04d10..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_concept.md
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
------------
-# CertificateSigningRequestList v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequestList
-
-
-
-
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1) array*  | 
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | 
-
-
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of CertificateSigningRequest
-
-### HTTP Request
-
-`GET /apis/certificates.k8s.io/v1alpha1/watch/certificatesigningrequests`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md
deleted file mode 100644
index d97323b2c8..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestlist_v1alpha1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## CertificateSigningRequestList v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequestList
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1) array*  | 
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | 
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md
deleted file mode 100644
index 9e7fbae674..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_concept.md
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
------------
-# CertificateSigningRequestSpec v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | CertificateSigningRequestSpec
-
-
-
-
-
-
-
-This information is immutable after the request is created. Only the Request and ExtraInfo fields can be set on creation, other fields are derived by Kubernetes and cannot be modified by users.
-
-
-
-Field        | Description
------------- | -----------
-groups 
     *string array*  | 
-request 
     *string*  | Base64-encoded PKCS#10 CSR data
-uid 
     *string*  | 
-username 
     *string*  | Information about the requesting user (if relevant) See user.Info interface for details
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md
deleted file mode 100644
index e335d818d6..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequestspec_v1alpha1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## CertificateSigningRequestSpec v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | CertificateSigningRequestSpec
-
-
-
-This information is immutable after the request is created. Only the Request and ExtraInfo fields can be set on creation, other fields are derived by Kubernetes and cannot be modified by users.
-
-
-
-Field        | Description
------------- | -----------
-groups 
     *string array*  | 
-request 
     *string*  | Base64-encoded PKCS#10 CSR data
-uid 
     *string*  | 
-username 
     *string*  | Information about the requesting user (if relevant) See user.Info interface for details
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md
deleted file mode 100644
index e69876a567..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_concept.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
------------
-# CertificateSigningRequestStatus v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequestStatus
-
-
-
-
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-certificate 
     *string*  | If request was approved, the controller will place the issued certificate here.
-conditions 
     *[CertificateSigningRequestCondition](#certificatesigningrequestcondition-v1alpha1) array*  | Conditions applied to the request, such as approval or denial.
-
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace status of the specified CertificateSigningRequest
-
-### HTTP Request
-
-`PUT /apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/{name}/status`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CertificateSigningRequest
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CertificateSigningRequest](#certificatesigningrequest-v1alpha1)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md
deleted file mode 100644
index 55a929b145..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_certificatesigningrequeststatus_v1alpha1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## CertificateSigningRequestStatus v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Certificates | v1alpha1 | CertificateSigningRequestStatus
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-certificate 
     *string*  | If request was approved, the controller will place the issued certificate here.
-conditions 
     *[CertificateSigningRequestCondition](#certificatesigningrequestcondition-v1alpha1) array*  | Conditions applied to the request, such as approval or denial.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_concept.md
deleted file mode 100644
index d31493f61a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# CinderVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CinderVolumeSource
-
-
-
-
-
-
-
-Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-fsType 
     *string*  | Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-readOnly 
     *boolean*  | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-volumeID 
     *string*  | volume id used to identify the volume in cinder More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_definition.md
deleted file mode 100644
index 670fb61930..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cindervolumesource_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## CinderVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CinderVolumeSource
-
-
-
-Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-fsType 
     *string*  | Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-readOnly 
     *boolean*  | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-volumeID 
     *string*  | volume id used to identify the volume in cinder More info: http://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md
deleted file mode 100644
index 0691f97e14..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_concept.md
+++ /dev/null
@@ -1,565 +0,0 @@
-
-
------------
-# ClusterRole v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRole
-
-
-
-
-
-
-
-ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata.
-rules 
     *[PolicyRule](#policyrule-v1alpha1) array*  | Rules holds all the PolicyRules for this ClusterRole
-
-
-### ClusterRoleList v1alpha1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRole](#clusterrole-v1alpha1) array*  | Items is a list of ClusterRoles
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a ClusterRole
-
-### HTTP Request
-
-`POST /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ClusterRole](#clusterrole-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRole](#clusterrole-v1alpha1)*  | OK
-
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace the specified ClusterRole
-
-### HTTP Request
-
-`PUT /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRole
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ClusterRole](#clusterrole-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRole](#clusterrole-v1alpha1)*  | OK
-
-
-## Patch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update the specified ClusterRole
-
-### HTTP Request
-
-`PATCH /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRole
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRole](#clusterrole-v1alpha1)*  | OK
-
-
-## Delete
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete a ClusterRole
-
-### HTTP Request
-
-`DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRole
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-gracePeriodSeconds  | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-orphanDependents  | Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[DeleteOptions](#deleteoptions-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-## Delete Collection
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete collection of ClusterRole
-
-### HTTP Request
-
-`DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified ClusterRole
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRole
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRole](#clusterrole-v1alpha1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind ClusterRole
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleList](#clusterrolelist-v1alpha1)*  | OK
-
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch changes to an object of kind ClusterRole
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRole
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md
deleted file mode 100644
index c36ca7eb77..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrole_v1alpha1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## ClusterRole v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRole
-
-
-
-ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata.
-rules 
     *[PolicyRule](#policyrule-v1alpha1) array*  | Rules holds all the PolicyRules for this ClusterRole
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md
deleted file mode 100644
index 9d249c7387..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_concept.md
+++ /dev/null
@@ -1,627 +0,0 @@
-
-
------------
-# ClusterRoleBinding v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRoleBinding
-
-
-
-
-
-
-
-ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata.
-roleRef 
     *[RoleRef](#roleref-v1alpha1)*  | RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
-subjects 
     *[Subject](#subject-v1alpha1) array*  | Subjects holds references to the objects the role applies to.
-
-
-### ClusterRoleBindingList v1alpha1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1) array*  | Items is a list of ClusterRoleBindings
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a ClusterRoleBinding
-
-### HTTP Request
-
-`POST /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | OK
-
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace the specified ClusterRoleBinding
-
-### HTTP Request
-
-`PUT /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRoleBinding
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | OK
-
-
-## Patch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update the specified ClusterRoleBinding
-
-### HTTP Request
-
-`PATCH /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRoleBinding
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | OK
-
-
-## Delete
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete a ClusterRoleBinding
-
-### HTTP Request
-
-`DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRoleBinding
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-gracePeriodSeconds  | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-orphanDependents  | Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[DeleteOptions](#deleteoptions-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-## Delete Collection
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete collection of ClusterRoleBinding
-
-### HTTP Request
-
-`DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified ClusterRoleBinding
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRoleBinding
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind ClusterRoleBinding
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ClusterRoleBindingList](#clusterrolebindinglist-v1alpha1)*  | OK
-
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch changes to an object of kind ClusterRoleBinding
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterrolebindings/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ClusterRoleBinding
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-## Watch List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of ClusterRoleBinding
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterrolebindings`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md
deleted file mode 100644
index ca190657a5..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolebinding_v1alpha1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## ClusterRoleBinding v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRoleBinding
-
-
-
-ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata.
-roleRef 
     *[RoleRef](#roleref-v1alpha1)*  | RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
-subjects 
     *[Subject](#subject-v1alpha1) array*  | Subjects holds references to the objects the role applies to.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md
deleted file mode 100644
index a43a158ede..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# ClusterRoleBindingList v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | ClusterRoleBindingList
-
-
-
-
-
-
-
-ClusterRoleBindingList is a collection of ClusterRoleBindings
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1) array*  | Items is a list of ClusterRoleBindings
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md
deleted file mode 100644
index d2c0dbcf80..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolebindinglist_v1alpha1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## ClusterRoleBindingList v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1alpha1 | ClusterRoleBindingList
-
-
-
-ClusterRoleBindingList is a collection of ClusterRoleBindings
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRoleBinding](#clusterrolebinding-v1alpha1) array*  | Items is a list of ClusterRoleBindings
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md
deleted file mode 100644
index bba333ae62..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_concept.md
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
------------
-# ClusterRoleList v1alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRoleList
-
-
-
-
-
-
-
-ClusterRoleList is a collection of ClusterRoles
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRole](#clusterrole-v1alpha1) array*  | Items is a list of ClusterRoles
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
-
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of ClusterRole
-
-### HTTP Request
-
-`GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md
deleted file mode 100644
index 416a354cab..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_clusterrolelist_v1alpha1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## ClusterRoleList v1alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-RbacAuthorization | v1alpha1 | ClusterRoleList
-
-
-
-ClusterRoleList is a collection of ClusterRoles
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ClusterRole](#clusterrole-v1alpha1) array*  | Items is a list of ClusterRoles
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard object's metadata.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_concept.md
deleted file mode 100644
index 7976a2bc40..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_concept.md
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
------------
-# ComponentCondition v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentCondition
-
-
-
-
-
-
-
-Information about the condition of a component.
-
-
-
-Field        | Description
------------- | -----------
-error 
     *string*  | Condition error code for a component. For example, a health check error code.
-message 
     *string*  | Message about the condition for a component. For example, information about a health check.
-status 
     *string*  | Status of the condition for a component. Valid values for "Healthy": "True", "False", or "Unknown".
-type 
     *string*  | Type of condition for a component. Valid value: "Healthy"
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_definition.md
deleted file mode 100644
index 6462a60913..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentcondition_v1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## ComponentCondition v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentCondition
-
-
-
-Information about the condition of a component.
-
-
-
-Field        | Description
------------- | -----------
-error 
     *string*  | Condition error code for a component. For example, a health check error code.
-message 
     *string*  | Message about the condition for a component. For example, information about a health check.
-status 
     *string*  | Status of the condition for a component. Valid values for "Healthy": "True", "False", or "Unknown".
-type 
     *string*  | Type of condition for a component. Valid value: "Healthy"
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_concept.md
deleted file mode 100644
index 7952df3b88..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_concept.md
+++ /dev/null
@@ -1,172 +0,0 @@
-
-
------------
-# ComponentStatus v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentStatus
-
-
-
-
-
-
-
-ComponentStatus (and ComponentStatusList) holds the cluster validation info.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-conditions 
     *[ComponentCondition](#componentcondition-v1) array*  | List of component conditions observed
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-### ComponentStatusList v1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ComponentStatus](#componentstatus-v1) array*  | List of ComponentStatus objects.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified ComponentStatus
-
-### HTTP Request
-
-`GET /api/v1/componentstatuses/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ComponentStatus
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ComponentStatus](#componentstatus-v1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list objects of kind ComponentStatus
-
-### HTTP Request
-
-`GET /api/v1/componentstatuses`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ComponentStatusList](#componentstatuslist-v1)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_definition.md
deleted file mode 100644
index efbd73394a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentstatus_v1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## ComponentStatus v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentStatus
-
-
-
-ComponentStatus (and ComponentStatusList) holds the cluster validation info.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-conditions 
     *[ComponentCondition](#componentcondition-v1) array*  | List of component conditions observed
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_concept.md
deleted file mode 100644
index b4445da385..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# ComponentStatusList v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentStatusList
-
-
-
-
-
-
-
-Status of all the conditions for the component as a list of ComponentStatus objects.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ComponentStatus](#componentstatus-v1) array*  | List of ComponentStatus objects.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_definition.md
deleted file mode 100644
index 02c154761e..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_componentstatuslist_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## ComponentStatusList v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ComponentStatusList
-
-
-
-Status of all the conditions for the component as a list of ComponentStatus objects.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ComponentStatus](#componentstatus-v1) array*  | List of ComponentStatus objects.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmap_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_configmap_v1_concept.md
deleted file mode 100644
index 3ef2d92fbf..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmap_v1_concept.md
+++ /dev/null
@@ -1,709 +0,0 @@
-
-
------------
-# ConfigMap v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMap
-
-
-
-
-
-
-
-ConfigMap holds configuration data for pods to consume.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-data 
     *object*  | Data contains the configuration data. Each key must be a valid DNS_SUBDOMAIN with an optional leading dot.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-### ConfigMapList v1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ConfigMap](#configmap-v1) array*  | Items is the list of ConfigMaps.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a ConfigMap
-
-### HTTP Request
-
-`POST /api/v1/namespaces/{namespace}/configmaps`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ConfigMap](#configmap-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMap](#configmap-v1)*  | OK
-
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace the specified ConfigMap
-
-### HTTP Request
-
-`PUT /api/v1/namespaces/{namespace}/configmaps/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ConfigMap
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[ConfigMap](#configmap-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMap](#configmap-v1)*  | OK
-
-
-## Patch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update the specified ConfigMap
-
-### HTTP Request
-
-`PATCH /api/v1/namespaces/{namespace}/configmaps/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ConfigMap
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMap](#configmap-v1)*  | OK
-
-
-## Delete
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete a ConfigMap
-
-### HTTP Request
-
-`DELETE /api/v1/namespaces/{namespace}/configmaps/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ConfigMap
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-gracePeriodSeconds  | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-orphanDependents  | Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[DeleteOptions](#deleteoptions-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-## Delete Collection
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete collection of ConfigMap
-
-### HTTP Request
-
-`DELETE /api/v1/namespaces/{namespace}/configmaps`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/namespaces/{namespace}/configmaps/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ConfigMap
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-exact  | Should the export be exact.  Exact export maintains cluster-specific fields like 'Namespace'
-export  | Should this value be exported.  Export strips fields that a user can not specify.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMap](#configmap-v1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/namespaces/{namespace}/configmaps`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMapList](#configmaplist-v1)*  | OK
-
-
-## List All Namespaces
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/configmaps`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[ConfigMapList](#configmaplist-v1)*  | OK
-
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch changes to an object of kind ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/watch/namespaces/{namespace}/configmaps/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the ConfigMap
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-## Watch List All Namespaces
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/watch/configmaps`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmap_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_configmap_v1_definition.md
deleted file mode 100644
index b5864ad664..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmap_v1_definition.md
+++ /dev/null
@@ -1,20 +0,0 @@
-## ConfigMap v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMap
-
-
-
-ConfigMap holds configuration data for pods to consume.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-data 
     *object*  | Data contains the configuration data. Each key must be a valid DNS_SUBDOMAIN with an optional leading dot.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_concept.md
deleted file mode 100644
index 8cb9c40d2d..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# ConfigMapKeySelector v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapKeySelector
-
-
-
-
-
-
-
-Selects a key from a ConfigMap.
-
-
-
-Field        | Description
------------- | -----------
-key 
     *string*  | The key to select.
-name 
     *string*  | Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_definition.md
deleted file mode 100644
index 00e98b82bb..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmapkeyselector_v1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## ConfigMapKeySelector v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapKeySelector
-
-
-
-Selects a key from a ConfigMap.
-
-
-
-Field        | Description
------------- | -----------
-key 
     *string*  | The key to select.
-name 
     *string*  | Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_concept.md
deleted file mode 100644
index 337e57078d..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_concept.md
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
------------
-# ConfigMapList v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapList
-
-
-
-
-
-
-
-ConfigMapList is a resource containing a list of ConfigMap objects.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ConfigMap](#configmap-v1) array*  | Items is the list of ConfigMaps.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of ConfigMap
-
-### HTTP Request
-
-`GET /api/v1/watch/namespaces/{namespace}/configmaps`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_definition.md
deleted file mode 100644
index 32e00ed55e..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmaplist_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## ConfigMapList v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapList
-
-
-
-ConfigMapList is a resource containing a list of ConfigMap objects.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[ConfigMap](#configmap-v1) array*  | Items is the list of ConfigMaps.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_concept.md
deleted file mode 100644
index 5dd5e2b183..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_concept.md
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
------------
-# ConfigMapVolumeSource v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapVolumeSource
-
-
-
-
-
-
-
-Adapts a ConfigMap into a volume.
-
-The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-defaultMode 
     *integer*  | Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
-items 
     *[KeyToPath](#keytopath-v1) array*  | If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error. Paths must be relative and may not contain the '..' path or start with '..'.
-name 
     *string*  | Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_definition.md
deleted file mode 100644
index e171a6f0d6..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_configmapvolumesource_v1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## ConfigMapVolumeSource v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ConfigMapVolumeSource
-
-
-
-Adapts a ConfigMap into a volume.
-
-The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.
-
-
-
-Field        | Description
------------- | -----------
-defaultMode 
     *integer*  | Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.
-items 
     *[KeyToPath](#keytopath-v1) array*  | If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error. Paths must be relative and may not contain the '..' path or start with '..'.
-name 
     *string*  | Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
diff --git a/docs/api-reference/v1.5/documents/_generated_container_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_container_v1_concept.md
deleted file mode 100644
index 8c33d2c477..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_container_v1_concept.md
+++ /dev/null
@@ -1,84 +0,0 @@
-
-
------------
-# Container v1
-
->bdocs-tab:kubectl Container Config to run nginx (must be embedded in a PodSpec to run).
-
-```bdocs-tab:kubectl_yaml
-
-name: nginx
-# Run the nginx:1.10 image
-image: nginx:1.10
-
-
-```
->bdocs-tab:curl Container Config to run nginx (must be embedded in a PodSpec to run).
-
-```bdocs-tab:curl_yaml
-
-name: nginx
-# Run the nginx:1.10 image
-image: nginx:1.10
-
-
-```
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Container
-
-
-
-
-
-
-
-A single application container that you want to run within a pod.
-
-
-
-Field        | Description
------------- | -----------
-args 
     *string array*  | Arguments to the entrypoint. The docker image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/containers#containers-and-commands
-command 
     *string array*  | Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/containers#containers-and-commands
-env 
     *[EnvVar](#envvar-v1) array*  | List of environment variables to set in the container. Cannot be updated.
-image 
     *string*  | Docker image name. More info: http://kubernetes.io/docs/user-guide/images
-imagePullPolicy 
     *string*  | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/images#updating-images
-lifecycle 
     *[Lifecycle](#lifecycle-v1)*  | Actions that the management system should take in response to container lifecycle events. Cannot be updated.
-livenessProbe 
     *[Probe](#probe-v1)*  | Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/pod-states#container-probes
-name 
     *string*  | Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.
-ports 
     *[ContainerPort](#containerport-v1) array*  | List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated.
-readinessProbe 
     *[Probe](#probe-v1)*  | Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/pod-states#container-probes
-resources 
     *[ResourceRequirements](#resourcerequirements-v1)*  | Compute Resources required by this container. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/persistent-volumes#resources
-securityContext 
     *[SecurityContext](#securitycontext-v1)*  | Security options the pod should run with. More info: http://releases.k8s.io/HEAD/docs/design/security_context.md
-stdin 
     *boolean*  | Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.
-stdinOnce 
     *boolean*  | Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
-terminationMessagePath 
     *string*  | Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Defaults to /dev/termination-log. Cannot be updated.
-tty 
     *boolean*  | Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.
-volumeMounts 
     *[VolumeMount](#volumemount-v1) array*  | Pod volumes to mount into the container's filesystem. Cannot be updated.
-workingDir 
     *string*  | Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.
-
-
-### ContainerStatus v1
-
-
-
-Field        | Description
------------- | -----------
-containerID 
     *string*  | Container's ID in the format 'docker://'. More info: http://kubernetes.io/docs/user-guide/container-environment#container-information
-image 
     *string*  | The image the container is running. More info: http://kubernetes.io/docs/user-guide/images
-imageID 
     *string*  | ImageID of the container's image.
-lastState 
     *[ContainerState](#containerstate-v1)*  | Details about the container's last termination condition.
-name 
     *string*  | This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-ready 
     *boolean*  | Specifies whether the container has passed its readiness probe.
-restartCount 
     *integer*  | The number of times the container has been restarted, currently based on the number of dead containers that have not yet been removed. Note that this is calculated from dead containers. But those containers are subject to garbage collection. This value will get capped at 5 by GC.
-state 
     *[ContainerState](#containerstate-v1)*  | Details about the container's current condition.
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_container_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_container_v1_definition.md
deleted file mode 100644
index a1cd1458e6..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_container_v1_definition.md
+++ /dev/null
@@ -1,34 +0,0 @@
-## Container v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | Container
-
-
-
-A single application container that you want to run within a pod.
-
-
-
-Field        | Description
------------- | -----------
-args 
     *string array*  | Arguments to the entrypoint. The docker image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/containers#containers-and-commands
-command 
     *string array*  | Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/containers#containers-and-commands
-env 
     *[EnvVar](#envvar-v1) array*  | List of environment variables to set in the container. Cannot be updated.
-image 
     *string*  | Docker image name. More info: http://kubernetes.io/docs/user-guide/images
-imagePullPolicy 
     *string*  | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/images#updating-images
-lifecycle 
     *[Lifecycle](#lifecycle-v1)*  | Actions that the management system should take in response to container lifecycle events. Cannot be updated.
-livenessProbe 
     *[Probe](#probe-v1)*  | Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/pod-states#container-probes
-name 
     *string*  | Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.
-ports 
     *[ContainerPort](#containerport-v1) array*  | List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated.
-readinessProbe 
     *[Probe](#probe-v1)*  | Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/pod-states#container-probes
-resources 
     *[ResourceRequirements](#resourcerequirements-v1)*  | Compute Resources required by this container. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/persistent-volumes#resources
-securityContext 
     *[SecurityContext](#securitycontext-v1)*  | Security options the pod should run with. More info: http://releases.k8s.io/HEAD/docs/design/security_context.md
-stdin 
     *boolean*  | Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.
-stdinOnce 
     *boolean*  | Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
-terminationMessagePath 
     *string*  | Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Defaults to /dev/termination-log. Cannot be updated.
-tty 
     *boolean*  | Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.
-volumeMounts 
     *[VolumeMount](#volumemount-v1) array*  | Pod volumes to mount into the container's filesystem. Cannot be updated.
-workingDir 
     *string*  | Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerimage_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerimage_v1_concept.md
deleted file mode 100644
index ca498c5d33..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerimage_v1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# ContainerImage v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerImage
-
-
-
-
-
-
-
-Describe a container image
-
-
-
-Field        | Description
------------- | -----------
-names 
     *string array*  | Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
-sizeBytes 
     *integer*  | The size of the image in bytes.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerimage_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerimage_v1_definition.md
deleted file mode 100644
index eee5bc1ffa..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerimage_v1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## ContainerImage v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerImage
-
-
-
-Describe a container image
-
-
-
-Field        | Description
------------- | -----------
-names 
     *string array*  | Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
-sizeBytes 
     *integer*  | The size of the image in bytes.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerport_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerport_v1_concept.md
deleted file mode 100644
index 3c003e33d8..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerport_v1_concept.md
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
------------
-# ContainerPort v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerPort
-
-
-
-
-
-
-
-ContainerPort represents a network port in a single container.
-
-
-
-Field        | Description
------------- | -----------
-containerPort 
     *integer*  | Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.
-hostIP 
     *string*  | What host IP to bind the external port to.
-hostPort 
     *integer*  | Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.
-name 
     *string*  | If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.
-protocol 
     *string*  | Protocol for port. Must be UDP or TCP. Defaults to "TCP".
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerport_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerport_v1_definition.md
deleted file mode 100644
index 1389ec92a8..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerport_v1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## ContainerPort v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerPort
-
-
-
-ContainerPort represents a network port in a single container.
-
-
-
-Field        | Description
------------- | -----------
-containerPort 
     *integer*  | Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.
-hostIP 
     *string*  | What host IP to bind the external port to.
-hostPort 
     *integer*  | Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.
-name 
     *string*  | If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.
-protocol 
     *string*  | Protocol for port. Must be UDP or TCP. Defaults to "TCP".
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstate_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerstate_v1_concept.md
deleted file mode 100644
index a0958ebb25..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstate_v1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# ContainerState v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerState
-
-
-
-
-
-
-
-ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.
-
-
-
-Field        | Description
------------- | -----------
-running 
     *[ContainerStateRunning](#containerstaterunning-v1)*  | Details about a running container
-terminated 
     *[ContainerStateTerminated](#containerstateterminated-v1)*  | Details about a terminated container
-waiting 
     *[ContainerStateWaiting](#containerstatewaiting-v1)*  | Details about a waiting container
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstate_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerstate_v1_definition.md
deleted file mode 100644
index 624e3666b5..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstate_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## ContainerState v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerState
-
-
-
-ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.
-
-
-
-Field        | Description
------------- | -----------
-running 
     *[ContainerStateRunning](#containerstaterunning-v1)*  | Details about a running container
-terminated 
     *[ContainerStateTerminated](#containerstateterminated-v1)*  | Details about a terminated container
-waiting 
     *[ContainerStateWaiting](#containerstatewaiting-v1)*  | Details about a waiting container
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_concept.md
deleted file mode 100644
index 1714dac45b..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_concept.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
------------
-# ContainerStateRunning v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateRunning
-
-
-
-
-
-
-
-ContainerStateRunning is a running state of a container.
-
-
-
-Field        | Description
------------- | -----------
-startedAt 
     *[Time](#time-unversioned)*  | Time at which the container was last (re-)started
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_definition.md
deleted file mode 100644
index 6080af649c..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstaterunning_v1_definition.md
+++ /dev/null
@@ -1,17 +0,0 @@
-## ContainerStateRunning v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateRunning
-
-
-
-ContainerStateRunning is a running state of a container.
-
-
-
-Field        | Description
------------- | -----------
-startedAt 
     *[Time](#time-unversioned)*  | Time at which the container was last (re-)started
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_concept.md
deleted file mode 100644
index e76ba6af4a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_concept.md
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
------------
-# ContainerStateTerminated v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateTerminated
-
-
-
-
-
-
-
-ContainerStateTerminated is a terminated state of a container.
-
-
-
-Field        | Description
------------- | -----------
-containerID 
     *string*  | Container's ID in the format 'docker://'
-exitCode 
     *integer*  | Exit status from the last termination of the container
-finishedAt 
     *[Time](#time-unversioned)*  | Time at which the container last terminated
-message 
     *string*  | Message regarding the last termination of the container
-reason 
     *string*  | (brief) reason from the last termination of the container
-signal 
     *integer*  | Signal from the last termination of the container
-startedAt 
     *[Time](#time-unversioned)*  | Time at which previous execution of the container started
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_definition.md
deleted file mode 100644
index 7c5fa0142a..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstateterminated_v1_definition.md
+++ /dev/null
@@ -1,23 +0,0 @@
-## ContainerStateTerminated v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateTerminated
-
-
-
-ContainerStateTerminated is a terminated state of a container.
-
-
-
-Field        | Description
------------- | -----------
-containerID 
     *string*  | Container's ID in the format 'docker://'
-exitCode 
     *integer*  | Exit status from the last termination of the container
-finishedAt 
     *[Time](#time-unversioned)*  | Time at which the container last terminated
-message 
     *string*  | Message regarding the last termination of the container
-reason 
     *string*  | (brief) reason from the last termination of the container
-signal 
     *integer*  | Signal from the last termination of the container
-startedAt 
     *[Time](#time-unversioned)*  | Time at which previous execution of the container started
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_concept.md
deleted file mode 100644
index 9a9a3eeb1f..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# ContainerStateWaiting v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateWaiting
-
-
-
-
-
-
-
-ContainerStateWaiting is a waiting state of a container.
-
-
-
-Field        | Description
------------- | -----------
-message 
     *string*  | Message regarding why the container is not yet running.
-reason 
     *string*  | (brief) reason the container is not yet running.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_definition.md
deleted file mode 100644
index a09ace9d38..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstatewaiting_v1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## ContainerStateWaiting v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStateWaiting
-
-
-
-ContainerStateWaiting is a waiting state of a container.
-
-
-
-Field        | Description
------------- | -----------
-message 
     *string*  | Message regarding why the container is not yet running.
-reason 
     *string*  | (brief) reason the container is not yet running.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_concept.md
deleted file mode 100644
index a77e8a3074..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_concept.md
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
------------
-# ContainerStatus v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStatus
-
-
-
-
-
-
-
-ContainerStatus contains details for the current status of this container.
-
-
-
-Field        | Description
------------- | -----------
-containerID 
     *string*  | Container's ID in the format 'docker://'. More info: http://kubernetes.io/docs/user-guide/container-environment#container-information
-image 
     *string*  | The image the container is running. More info: http://kubernetes.io/docs/user-guide/images
-imageID 
     *string*  | ImageID of the container's image.
-lastState 
     *[ContainerState](#containerstate-v1)*  | Details about the container's last termination condition.
-name 
     *string*  | This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-ready 
     *boolean*  | Specifies whether the container has passed its readiness probe.
-restartCount 
     *integer*  | The number of times the container has been restarted, currently based on the number of dead containers that have not yet been removed. Note that this is calculated from dead containers. But those containers are subject to garbage collection. This value will get capped at 5 by GC.
-state 
     *[ContainerState](#containerstate-v1)*  | Details about the container's current condition.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_definition.md
deleted file mode 100644
index 4154b694f7..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_containerstatus_v1_definition.md
+++ /dev/null
@@ -1,24 +0,0 @@
-## ContainerStatus v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | ContainerStatus
-
-
-
-ContainerStatus contains details for the current status of this container.
-
-
-
-Field        | Description
------------- | -----------
-containerID 
     *string*  | Container's ID in the format 'docker://'. More info: http://kubernetes.io/docs/user-guide/container-environment#container-information
-image 
     *string*  | The image the container is running. More info: http://kubernetes.io/docs/user-guide/images
-imageID 
     *string*  | ImageID of the container's image.
-lastState 
     *[ContainerState](#containerstate-v1)*  | Details about the container's last termination condition.
-name 
     *string*  | This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-ready 
     *boolean*  | Specifies whether the container has passed its readiness probe.
-restartCount 
     *integer*  | The number of times the container has been restarted, currently based on the number of dead containers that have not yet been removed. Note that this is calculated from dead containers. But those containers are subject to garbage collection. This value will get capped at 5 by GC.
-state 
     *[ContainerState](#containerstate-v1)*  | Details about the container's current condition.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md b/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md
deleted file mode 100644
index 53ce2ba364..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_concept.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
------------
-# CPUTargetUtilization v1beta1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1beta1 | CPUTargetUtilization
-
-
-
-
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-targetPercentage 
     *integer*  | fraction of the requested CPU that should be utilized/used, e.g. 70 means that 70% of the requested CPU should be in use.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md b/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md
deleted file mode 100644
index c24e29a5c4..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cputargetutilization_v1beta1_definition.md
+++ /dev/null
@@ -1,17 +0,0 @@
-## CPUTargetUtilization v1beta1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1beta1 | CPUTargetUtilization
-
-
-
-
-
-
-
-Field        | Description
------------- | -----------
-targetPercentage 
     *integer*  | fraction of the requested CPU that should be utilized/used, e.g. 70 means that 70% of the requested CPU should be in use.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_concept.md
deleted file mode 100644
index f9084661df..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_concept.md
+++ /dev/null
@@ -1,1000 +0,0 @@
-
-
------------
-# CronJob v2alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Batch | v2alpha1 | CronJob
-
-
-
-
-
-
-
-CronJob represents the configuration of a single cron job.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-spec 
     *[CronJobSpec](#cronjobspec-v2alpha1)*  | Spec is a structure defining the expected behavior of a job, including the schedule. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#spec-and-status
-status 
     *[CronJobStatus](#cronjobstatus-v2alpha1)*  | Status is a structure describing current status of a job. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#spec-and-status
-
-
-### CronJobSpec v2alpha1
-
-
-
-Field        | Description
------------- | -----------
-concurrencyPolicy 
     *string*  | ConcurrencyPolicy specifies how to treat concurrent executions of a Job.
-jobTemplate 
     *[JobTemplateSpec](#jobtemplatespec-v2alpha1)*  | JobTemplate is the object that describes the job that will be created when executing a CronJob.
-schedule 
     *string*  | Schedule contains the schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.
-startingDeadlineSeconds 
     *integer*  | Optional deadline in seconds for starting the job if it misses scheduled time for any reason.  Missed jobs executions will be counted as failed ones.
-suspend 
     *boolean*  | Suspend flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.
-
-### CronJobStatus v2alpha1
-
-
-
-Field        | Description
------------- | -----------
-active 
     *[ObjectReference](#objectreference-v1) array*  | Active holds pointers to currently running jobs.
-lastScheduleTime 
     *[Time](#time-unversioned)*  | LastScheduleTime keeps information of when was the last time the job was successfully scheduled.
-
-### CronJobList v2alpha1
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CronJob](#cronjob-v2alpha1) array*  | Items is the list of CronJob.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-
-
-## Write Operations
-
-See supported operations below...
-
-## Create
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-create a CronJob
-
-### HTTP Request
-
-`POST /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CronJob](#cronjob-v2alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## Replace
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace the specified CronJob
-
-### HTTP Request
-
-`PUT /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CronJob](#cronjob-v2alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## Patch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update the specified CronJob
-
-### HTTP Request
-
-`PATCH /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## Delete
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete a CronJob
-
-### HTTP Request
-
-`DELETE /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-gracePeriodSeconds  | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-orphanDependents  | Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[DeleteOptions](#deleteoptions-v1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-## Delete Collection
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-delete collection of CronJob
-
-### HTTP Request
-
-`DELETE /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Status](#status-unversioned)*  | OK
-
-
-
-## Read Operations
-
-See supported operations below...
-
-## Read
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read the specified CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-exact  | Should the export be exact.  Exact export maintains cluster-specific fields like 'Namespace'
-export  | Should this value be exported.  Export strips fields that a user can not specify.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJobList](#cronjoblist-v2alpha1)*  | OK
-
-
-## List All Namespaces
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-list or watch objects of kind CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/cronjobs`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJobList](#cronjoblist-v2alpha1)*  | OK
-
-
-## Watch
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch changes to an object of kind CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/watch/namespaces/{namespace}/cronjobs/{name}`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-## Watch List
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/watch/namespaces/{namespace}/cronjobs`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-## Watch List All Namespaces
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-watch individual changes to a list of CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/watch/cronjobs`
-
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-fieldSelector  | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-labelSelector  | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-pretty  | If 'true', then the output is pretty printed.
-resourceVersion  | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history.
-timeoutSeconds  | Timeout for the list/watch call.
-watch  | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[Event](#event-versioned)*  | OK
-
-
-
-## Status Operations
-
-See supported operations below...
-
-## Patch Status
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-partially update status of the specified CronJob
-
-### HTTP Request
-
-`PATCH /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[Patch](#patch-unversioned)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## Read Status
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-read status of the specified CronJob
-
-### HTTP Request
-
-`GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-## Replace Status
-
->bdocs-tab:kubectl `kubectl` Command
-
-```bdocs-tab:kubectl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:curl `curl` Command (*requires `kubectl proxy` to be running*)
-
-```bdocs-tab:curl_shell
-
-Coming Soon
-
-```
-
->bdocs-tab:kubectl Output
-
-```bdocs-tab:kubectl_json
-
-Coming Soon
-
-```
->bdocs-tab:curl Response Body
-
-```bdocs-tab:curl_json
-
-Coming Soon
-
-```
-
-
-
-replace status of the specified CronJob
-
-### HTTP Request
-
-`PUT /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status`
-
-### Path Parameters
-
-Parameter    | Description
------------- | -----------
-name  | name of the CronJob
-namespace  | object name and auth scope, such as for teams and projects
-
-### Query Parameters
-
-Parameter    | Description
------------- | -----------
-pretty  | If 'true', then the output is pretty printed.
-
-### Body Parameters
-
-Parameter    | Description
------------- | -----------
-body 
     *[CronJob](#cronjob-v2alpha1)*  | 
-
-### Response
-
-Code         | Description
------------- | -----------
-200 
     *[CronJob](#cronjob-v2alpha1)*  | OK
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_definition.md
deleted file mode 100644
index a3477fe785..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjob_v2alpha1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## CronJob v2alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Batch | v2alpha1 | CronJob
-
-
-
-CronJob represents the configuration of a single cron job.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ObjectMeta](#objectmeta-v1)*  | Standard object's metadata. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-spec 
     *[CronJobSpec](#cronjobspec-v2alpha1)*  | Spec is a structure defining the expected behavior of a job, including the schedule. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#spec-and-status
-status 
     *[CronJobStatus](#cronjobstatus-v2alpha1)*  | Status is a structure describing current status of a job. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#spec-and-status
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_concept.md
deleted file mode 100644
index f63337e893..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# CronJobList v2alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobList
-
-
-
-
-
-
-
-CronJobList is a collection of cron jobs.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CronJob](#cronjob-v2alpha1) array*  | Items is the list of CronJob.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_definition.md
deleted file mode 100644
index 9c0f2059d8..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjoblist_v2alpha1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## CronJobList v2alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobList
-
-
-
-CronJobList is a collection of cron jobs.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#resources
-items 
     *[CronJob](#cronjob-v2alpha1) array*  | Items is the list of CronJob.
-kind 
     *string*  | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds
-metadata 
     *[ListMeta](#listmeta-unversioned)*  | Standard list metadata More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#metadata
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_concept.md
deleted file mode 100644
index 2e58bf43c9..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_concept.md
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
------------
-# CronJobSpec v2alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobSpec
-
-
-
-
-
-
-
-CronJobSpec describes how the job execution will look like and when it will actually run.
-
-
-
-Field        | Description
------------- | -----------
-concurrencyPolicy 
     *string*  | ConcurrencyPolicy specifies how to treat concurrent executions of a Job.
-jobTemplate 
     *[JobTemplateSpec](#jobtemplatespec-v2alpha1)*  | JobTemplate is the object that describes the job that will be created when executing a CronJob.
-schedule 
     *string*  | Schedule contains the schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.
-startingDeadlineSeconds 
     *integer*  | Optional deadline in seconds for starting the job if it misses scheduled time for any reason.  Missed jobs executions will be counted as failed ones.
-suspend 
     *boolean*  | Suspend flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_definition.md
deleted file mode 100644
index 56dd8832c3..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjobspec_v2alpha1_definition.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## CronJobSpec v2alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobSpec
-
-
-
-CronJobSpec describes how the job execution will look like and when it will actually run.
-
-
-
-Field        | Description
------------- | -----------
-concurrencyPolicy 
     *string*  | ConcurrencyPolicy specifies how to treat concurrent executions of a Job.
-jobTemplate 
     *[JobTemplateSpec](#jobtemplatespec-v2alpha1)*  | JobTemplate is the object that describes the job that will be created when executing a CronJob.
-schedule 
     *string*  | Schedule contains the schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.
-startingDeadlineSeconds 
     *integer*  | Optional deadline in seconds for starting the job if it misses scheduled time for any reason.  Missed jobs executions will be counted as failed ones.
-suspend 
     *boolean*  | Suspend flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_concept.md b/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_concept.md
deleted file mode 100644
index 3bd2980690..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_concept.md
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
------------
-# CronJobStatus v2alpha1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobStatus
-
-
-
-
-
-
-
-CronJobStatus represents the current state of a cron job.
-
-
-
-Field        | Description
------------- | -----------
-active 
     *[ObjectReference](#objectreference-v1) array*  | Active holds pointers to currently running jobs.
-lastScheduleTime 
     *[Time](#time-unversioned)*  | LastScheduleTime keeps information of when was the last time the job was successfully scheduled.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_definition.md b/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_definition.md
deleted file mode 100644
index 021803c3e1..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_cronjobstatus_v2alpha1_definition.md
+++ /dev/null
@@ -1,18 +0,0 @@
-## CronJobStatus v2alpha1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v2alpha1 | CronJobStatus
-
-
-
-CronJobStatus represents the current state of a cron job.
-
-
-
-Field        | Description
------------- | -----------
-active 
     *[ObjectReference](#objectreference-v1) array*  | Active holds pointers to currently running jobs.
-lastScheduleTime 
     *[Time](#time-unversioned)*  | LastScheduleTime keeps information of when was the last time the job was successfully scheduled.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md
deleted file mode 100644
index e18c960c76..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_concept.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
------------
-# CrossVersionObjectReference v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CrossVersionObjectReference
-
-
-
-
-
-
-
-CrossVersionObjectReference contains enough information to let you identify the referred resource.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | API version of the referent
-kind 
     *string*  | Kind of the referent; More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds"
-name 
     *string*  | Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md
deleted file mode 100644
index 49aabee65c..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_crossversionobjectreference_v1_definition.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## CrossVersionObjectReference v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | CrossVersionObjectReference
-
-
-
-CrossVersionObjectReference contains enough information to let you identify the referred resource.
-
-
-
-Field        | Description
------------- | -----------
-apiVersion 
     *string*  | API version of the referent
-kind 
     *string*  | Kind of the referent; More info: http://releases.k8s.io/HEAD/docs/devel/api-conventions.md#types-kinds"
-name 
     *string*  | Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
-
diff --git a/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_concept.md b/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_concept.md
deleted file mode 100644
index e745761332..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_concept.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
------------
-# DaemonEndpoint v1
-
-
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | DaemonEndpoint
-
-
-
-
-
-
-
-DaemonEndpoint contains information about a single Daemon endpoint.
-
-
-
-Field        | Description
------------- | -----------
-Port 
     *integer*  | Port number of the given endpoint.
-
-
-
-
-
-
diff --git a/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_definition.md b/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_definition.md
deleted file mode 100644
index f2b131a01e..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_daemonendpoint_v1_definition.md
+++ /dev/null
@@ -1,17 +0,0 @@
-## DaemonEndpoint v1
-
-Group        | Version     | Kind
------------- | ---------- | -----------
-Core | v1 | DaemonEndpoint
-
-
-
-DaemonEndpoint contains information about a single Daemon endpoint.
-
-
-
-Field        | Description
------------- | -----------
-Port 
     *integer*  | Port number of the given endpoint.
-
diff --git a/docs/api-reference/v1.5/documents/_generated_daemonset_v1beta1_concept.md b/docs/api-reference/v1.5/documents/_generated_daemonset_v1beta1_concept.md
deleted file mode 100644
index c44c764460..0000000000
--- a/docs/api-reference/v1.5/documents/_generated_daemonset_v1beta1_concept.md
+++ /dev/null
@@ -1,1110 +0,0 @@
-
-
------------
-# DaemonSet v1beta1
-
->bdocs-tab:kubectl DaemonSet Config to print the `hostname` on each Node in the cluster every 10 seconds.
-
-```bdocs-tab:kubectl_yaml
-
-apiVersion: extensions/v1beta1
-kind: DaemonSet
-metadata:
-  # Unique key of the DaemonSet instance
-  name: daemonset-example
-spec:
-  template:
-    metadata:
-      labels:
-        app: daemonset-example
-    spec:
-      containers:
-      # This container is run once on each Node in the cluster
-      - name: daemonset-example
-        image: ubuntu:trusty
-        command:
-        - /bin/sh
-        args:
-        - -c
-        # This script is run through `sh -c