From 703f8b92f514fd6f84ff8b3e6c577e80f640dfdb Mon Sep 17 00:00:00 2001
From: Victor Palade <victor@cloudflavor.io>
Date: Thu, 5 Aug 2021 01:06:02 +0200
Subject: [PATCH 01/68] Tracking commit for v1.23 docs


From 5f192f2cb1df5b15aa1574efd565867815c3073e Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Tue, 17 Aug 2021 09:51:11 +0200
Subject: [PATCH 02/68] Add note about deprecated seccomp annotation

We now add a note to clarify that the annotations are deprecated and
will become non-functional in v1.25.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 .../docs/reference/labels-annotations-taints.md  |  8 +++++++-
 content/en/docs/tutorials/clusters/seccomp.md    | 16 ++++++++++++----
 2 files changed, 19 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md
index 07e6d19426dd8..e2fc2b317e941 100644
--- a/content/en/docs/reference/labels-annotations-taints.md
+++ b/content/en/docs/reference/labels-annotations-taints.md
@@ -425,4 +425,10 @@ policies to apply when validating a submitted Pod. Note that warnings are also d
 or updating objects that contain Pod templates, such as Deployments, Jobs, StatefulSets, etc.
 
 See [Enforcing Pod Security at the Namespace Level](/docs/concepts/security/pod-security-admission)
-for more information.
\ No newline at end of file
+for more information.
+
+## seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io/[NAME] (deprecated)
+
+The seccomp annotations have been deprecated since Kubernetes v1.19 and will
+become non-functional in v1.25. Please use the `seccompProfile` of the
+`SecurityContext` instead.
\ No newline at end of file
diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index c510f4c70768d..ce16eb524a629 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -170,12 +170,20 @@ Download the correct manifest for your Kubernetes version:
 {{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/audit-pod.yaml" >}}
 {{< /tab >}}}
-{{{< tab name="Pre-v1.19 (alpha)" >}}
+{{{< tab name="Pre-v1.19 (deprecated)" >}}
 {{< codenew file="pods/security/seccomp/alpha/audit-pod.yaml" >}}
 {{< /tab >}}
 {{< /tabs >}}
 <br>
 
+{{< note >}}
+The functional support for the already deprecated seccomp annotations
+`seccomp.security.alpha.kubernetes.io/pod` (for the whole pod) and
+`container.seccomp.security.alpha.kubernetes.io/[name]` (for a single container)
+is going to be removed with the release of Kubernetes v1.25. Please always use
+the native API fields in favor of the annotations.
+{{< /note >}}
+
 Create the Pod in the cluster:
 
 ```
@@ -270,7 +278,7 @@ Download the correct manifest for your Kubernetes version:
 {{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/violation-pod.yaml" >}}
 {{< /tab >}}}
-{{{< tab name="Pre-v1.19 (alpha)" >}}
+{{{< tab name="Pre-v1.19 (deprecated)" >}}
 {{< codenew file="pods/security/seccomp/alpha/violation-pod.yaml" >}}
 {{< /tab >}}
 {{< /tabs >}}
@@ -321,7 +329,7 @@ Download the correct manifest for your Kubernetes version:
 {{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/fine-pod.yaml" >}}
 {{< /tab >}}}
-{{{< tab name="Pre-v1.19 (alpha)" >}}
+{{{< tab name="Pre-v1.19 (deprecated)" >}}
 {{< codenew file="pods/security/seccomp/alpha/fine-pod.yaml" >}}
 {{< /tab >}}
 {{< /tabs >}}
@@ -403,7 +411,7 @@ Download the correct manifest for your Kubernetes version:
 {{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/default-pod.yaml" >}}
 {{< /tab >}}}
-{{{< tab name="Pre-v1.19 (alpha)" >}}
+{{{< tab name="Pre-v1.19 (deprecated)" >}}
 {{< codenew file="pods/security/seccomp/alpha/default-pod.yaml" >}}
 {{< /tab >}}
 {{< /tabs >}}

From 5db769d46c22d1b05b0ca73ac4af10a9ebdbb2e4 Mon Sep 17 00:00:00 2001
From: Jesse Butler <butlerjl@amazon.com>
Date: Thu, 9 Sep 2021 08:52:52 -0400
Subject: [PATCH 03/68] update config.toml for 1.23 release

---
 config.toml | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/config.toml b/config.toml
index c8953f2f7d7eb..7c7f88a4e60c9 100644
--- a/config.toml
+++ b/config.toml
@@ -138,10 +138,10 @@ time_format_default = "January 02, 2006 at 3:04 PM PST"
 description = "Production-Grade Container Orchestration"
 showedit = true
 
-latest = "v1.22"
+latest = "v1.23"
 
-fullversion = "v1.22.0"
-version = "v1.22"
+fullversion = "v1.23.0"
+version = "v1.23"
 githubbranch = "main"
 docsbranch = "main"
 deprecated = false
@@ -178,12 +178,19 @@ js = [
 ]
 
 [[params.versions]]
-fullversion = "v1.22.0"
-version = "v1.22"
-githubbranch = "v1.22.0"
+fullversion = "v1.23.0"
+version = "v1.23"
+githubbranch = "v1.23.0"
 docsbranch = "main"
 url = "https://kubernetes.io"
 
+[[params.versions]]
+fullversion = "v1.22.1"
+version = "v1.22"
+githubbranch = "v1.22.1"
+docsbranch = "release-1.22"
+url = "https://v1-22.docs.kubernetes.io"
+
 [[params.versions]]
 fullversion = "v1.21.4"
 version = "v1.21"
@@ -205,13 +212,6 @@ githubbranch = "v1.19.14"
 docsbranch = "release-1.19"
 url = "https://v1-19.docs.kubernetes.io"
 
-[[params.versions]]
-fullversion = "v1.18.20"
-version = "v1.18"
-githubbranch = "v1.18.20"
-docsbranch = "release-1.18"
-url = "https://v1-18.docs.kubernetes.io"
-
 # User interface configuration
 [params.ui]
 # Enable to show the side bar menu in its compact state.

From c189c2d162e5e283272551aca2e43130bd654054 Mon Sep 17 00:00:00 2001
From: Zovin Khanmohammed <zovinkhanmohd@hotmail.com>
Date: Sun, 12 Sep 2021 04:56:06 -0500
Subject: [PATCH 04/68] Update docs to reflect newly support shells with
 autocompletions (#29610)

* Update docs to reflect newly support shells with autocompletions

* Update Windows docs to use Powershell instead of zsh

* Adds a bit more explanation of the different lines.

* Apply suggestions from code review

Co-authored-by: Tim Bannister <tim@scalefactory.com>

* Apply PR suggestions

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../included/optional-kubectl-configs-pwsh.md | 23 +++++++++++++++++++
 .../docs/tasks/tools/install-kubectl-linux.md |  2 +-
 .../docs/tasks/tools/install-kubectl-macos.md |  2 +-
 .../tasks/tools/install-kubectl-windows.md    |  7 +++---
 4 files changed, 28 insertions(+), 6 deletions(-)
 create mode 100644 content/en/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md

diff --git a/content/en/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md b/content/en/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md
new file mode 100644
index 0000000000000..12e5d60c5d29b
--- /dev/null
+++ b/content/en/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md
@@ -0,0 +1,23 @@
+---
+title: "PowerShell auto-completion"
+description: "Some optional configuration for powershell auto-completion."
+headless: true
+---
+
+The kubectl completion script for PowerShell can be generated with the command `kubectl completion powershell`.
+
+To do so in all your shell sessions, add the following line to your `$PROFILE` file:
+
+```powershell
+kubectl completion powershell | Out-String | Invoke-Expression
+```
+
+This command will regenerate the auto-completion script on every PowerShell start up. You can also add the generated script directly to your `$PROFILE` file.
+
+To add the generated script to your `$PROFILE` file, run the following line in your powershell prompt:
+
+```powershell
+kubectl completion powershell >> $PROFILE
+```
+
+After reloading your shell, kubectl autocompletion should be working.
diff --git a/content/en/docs/tasks/tools/install-kubectl-linux.md b/content/en/docs/tasks/tools/install-kubectl-linux.md
index efb203f8b9563..3b48ce6790a59 100644
--- a/content/en/docs/tasks/tools/install-kubectl-linux.md
+++ b/content/en/docs/tasks/tools/install-kubectl-linux.md
@@ -176,7 +176,7 @@ kubectl version --client
 
 ### Enable shell autocompletion
 
-kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing.
+kubectl provides autocompletion support for Bash, Zsh, Fish, and PowerShell, which can save you a lot of typing.
 
 Below are the procedures to set up autocompletion for Bash and Zsh.
 
diff --git a/content/en/docs/tasks/tools/install-kubectl-macos.md b/content/en/docs/tasks/tools/install-kubectl-macos.md
index b46ab0364037f..f2f7cf1a9c2e3 100644
--- a/content/en/docs/tasks/tools/install-kubectl-macos.md
+++ b/content/en/docs/tasks/tools/install-kubectl-macos.md
@@ -159,7 +159,7 @@ If you are on macOS and using [Macports](https://macports.org/) package manager,
 
 ### Enable shell autocompletion
 
-kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing.
+kubectl provides autocompletion support for Bash, Zsh, Fish, and PowerShell which can save you a lot of typing.
 
 Below are the procedures to set up autocompletion for Bash and Zsh.
 
diff --git a/content/en/docs/tasks/tools/install-kubectl-windows.md b/content/en/docs/tasks/tools/install-kubectl-windows.md
index 8059fa7a3a626..2417d1a3c4bea 100644
--- a/content/en/docs/tasks/tools/install-kubectl-windows.md
+++ b/content/en/docs/tasks/tools/install-kubectl-windows.md
@@ -22,7 +22,6 @@ The following methods exist for installing kubectl on Windows:
 - [Install kubectl binary with curl on Windows](#install-kubectl-binary-with-curl-on-windows)
 - [Install on Windows using Chocolatey or Scoop](#install-on-windows-using-chocolatey-or-scoop)
 
-
 ### Install kubectl binary with curl on Windows
 
 1. Download the [latest release {{< param "fullversion" >}}](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe).
@@ -134,11 +133,11 @@ Edit the config file with a text editor of your choice, such as Notepad.
 
 ### Enable shell autocompletion
 
-kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing.
+kubectl provides autocompletion support for Bash, Zsh, Fish, and PowerShell, which can save you a lot of typing.
 
-Below are the procedures to set up autocompletion for Zsh, if you are running that on Windows.
+Below are the procedures to set up autocompletion for PowerShell.
 
-{{< include "included/optional-kubectl-configs-zsh.md" >}}
+{{< include "included/optional-kubectl-configs-pwsh.md" >}}
 
 ### Install `kubectl convert` plugin
 

From dae1b392e6377f7e8c83863df86a75bf5e3cd92f Mon Sep 17 00:00:00 2001
From: siddhantprateek <siddhantprateek@gmail.com>
Date: Mon, 11 Oct 2021 18:32:45 +0530
Subject: [PATCH 05/68] replaced link from api-beta2 to api-beta3

Signed-off-by: siddhantprateek <siddhantprateek@gmail.com>
---
 content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
index 3779ec2fdfe77..60abb96e560ee 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
@@ -127,7 +127,7 @@ If your configuration is not using the latest version it is **recommended** that
 the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command.
 
 For more information on the fields and usage of the configuration you can navigate to our
-[API reference page](/docs/reference/config-api/kubeadm-config.v1beta2/).
+[API reference page](/docs/reference/config-api/kubeadm-config.v1beta3/).
 
 ### Adding kube-proxy parameters {#kube-proxy}
 

From bb634e6db9b439258dd5ec79c3a17f73a992f88c Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sat, 16 Oct 2021 12:23:33 +0100
Subject: [PATCH 06/68] Revise seccomp tutorial

- Drop docs for Kubernetes earlier than v1.19
- Have kubectl fetch manifests using HTTP where suitable
- General tidying
---
 content/en/docs/tutorials/clusters/seccomp.md | 302 +++++++++---------
 1 file changed, 158 insertions(+), 144 deletions(-)

diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index 3a883baf5e649..af8cb9e2efbeb 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -36,16 +36,18 @@ profiles that give only the necessary privileges to your container processes.
 
 ## {{% heading "prerequisites" %}}
 
-{{< version-check >}}
-
 In order to complete all steps in this tutorial, you must install
-[kind](https://kind.sigs.k8s.io/docs/user/quick-start/) and
-[kubectl](/docs/tasks/tools/). This tutorial will show examples
-both alpha (new in v1.22) and generally available seccomp functionality. You should
-make sure that your cluster is [configured
-correctly](https://kind.sigs.k8s.io/docs/user/quick-start/#setting-kubernetes-version)
+[kind](/docs/tasks/tools/#kind) and [kubectl](/docs/tasks/tools/#kubectl).
+
+This tutorial shows some examples that are still alpha (since v1.22) and
+others that use only generally available seccomp functionality. You should
+make sure that your cluster is
+[configured correctly](https://kind.sigs.k8s.io/docs/user/quick-start/#setting-kubernetes-version)
 for the version you are using.
 
+The tutorial also uses the `curl` tool for downloading examples to your computer.
+You can adapt the steps to use a different tool if you prefer.
+
 {{< note >}}
 It is not possible to apply a seccomp profile to a container running with
 `privileged: true` set in the container's `securityContext`. Privileged containers always
@@ -54,53 +56,6 @@ run as `Unconfined`.
 
 <!-- steps -->
 
-## Enable the use of `RuntimeDefault` as the default seccomp profile for all workloads
-
-{{< feature-state state="alpha" for_k8s_version="v1.22" >}}
-
-`SeccompDefault` is an optional kubelet
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates) as
-well as corresponding `--seccomp-default`
-[command line flag](/docs/reference/command-line-tools-reference/kubelet).
-Both have to be enabled simultaneously to use the feature.
-
-If enabled, the kubelet will use the `RuntimeDefault` seccomp profile by default, which is 
-defined by the container runtime, instead of using the `Unconfined` (seccomp disabled) mode. 
-The default profiles aim to provide a strong set
-of security defaults while preserving the functionality of the workload. It is
-possible that the default profiles differ between container runtimes and their
-release versions, for example when comparing those from CRI-O and containerd.
-
-Some workloads may require a lower amount of syscall restrictions than others.
-This means that they can fail during runtime even with the `RuntimeDefault`
-profile. To mitigate such a failure, you can:
-
-- Run the workload explicitly as `Unconfined`.
-- Disable the `SeccompDefault` feature for the nodes. Also making sure that
-  workloads get scheduled on nodes where the feature is disabled.
-- Create a custom seccomp profile for the workload.
-
-If you were introducing this feature into production-like cluster, the Kubernetes project
-recommends that you enable this feature gate on a subset of your nodes and then
-test workload execution before rolling the change out cluster-wide.
-
-More detailed information about a possible upgrade and downgrade strategy can be
-found in the [related Kubernetes Enhancement Proposal (KEP)](https://github.com/kubernetes/enhancements/tree/a70cc18/keps/sig-node/2413-seccomp-by-default#upgrade--downgrade-strategy).
-
-Since the feature is in alpha state it is disabled per default. To enable it,
-pass the flags `--feature-gates=SeccompDefault=true --seccomp-default` to the
-`kubelet` CLI or enable it via the [kubelet configuration
-file](/docs/tasks/administer-cluster/kubelet-config-file/). To enable the
-feature gate in [kind](https://kind.sigs.k8s.io), ensure that `kind` provides
-the minimum required Kubernetes version and enables the `SeccompDefault` feature
-[in the kind configuration](https://kind.sigs.k8s.io/docs/user/quick-start/#enable-feature-gates-in-your-cluster):
-
-```yaml
-kind: Cluster
-apiVersion: kind.x-k8s.io/v1alpha4
-featureGates:
-  SeccompDefault: true
-```
 
 ## Create Seccomp Profiles
 
@@ -120,7 +75,24 @@ into the cluster.
 {{< /tab >}}}
 {{< /tabs >}}
 
-## Create a Local Kubernetes Cluster with Kind
+Run these commands:
+
+```shell
+mkdir ./profiles
+curl -L -o profiles/audit.json https://k8s.io/examples/pods/security/seccomp/profiles/audit.json
+curl -L -o profiles/violation.json https://k8s.io/examples/pods/security/seccomp/profiles/violation.json
+curl -L -o profiles/fine-grained.json https://k8s.io/examples/pods/security/seccomp/profiles/fine-grained.json
+ls profiles
+```
+
+You should see three profiles listed at the end of the final step:
+```
+audit.json  fine-grained.json  violation.json
+```
+
+
+## Create a Local Kubernetes Cluster with kind
+
 
 For simplicity, [kind](https://kind.sigs.k8s.io/) can be used to create a single
 node cluster with the seccomp profiles loaded. Kind runs Kubernetes in Docker,
@@ -129,35 +101,52 @@ to be mounted in the filesystem of each container similar to loading files
 onto a node.
 
 {{< codenew file="pods/security/seccomp/kind.yaml" >}}
-<br>
-
-Download the example above, and save it to a file named `kind.yaml`. Then create
-the cluster with the configuration.
 
+Download that example kind configuration, and save it to a file named `kind.yaml`:
+```shell
+curl -L -O https://k8s.io/examples/pods/security/seccomp/kind.yaml
 ```
+
+You can set a specific Kubernetes version by setting the node's container image.
+See [Nodes](https://kind.sigs.k8s.io/docs/user/configuration/#nodes) within the
+kind documentation about configuration for more details on this.
+This tutorial assumes you are using Kubernetes {{< param "version" >}}.
+
+As an alpha feature, you can configure Kubernetes to use the profile that the
+{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}
+prefers by default, rather than falling back to `Unconfined`.
+If you want to try that, see
+[enable the use of `RuntimeDefault` as the default seccomp profile for all workloads](#enable-the-use-of-runtimedefault-as-the-default-seccomp-profile-for-all-workloads)
+before you continue.
+
+Once you have a kind configuration in place, create the kind cluster with
+that configuration:
+
+```shell
 kind create cluster --config=kind.yaml
 ```
 
-Once the cluster is ready, identify the container running as the single node
-cluster:
+After the new Kubernetes cluster is ready, identify the Docker container running
+as the single node cluster:
 
-```
+```shell
 docker ps
 ```
 
 You should see output indicating that a container is running with name
-`kind-control-plane`.
+`kind-control-plane`. The output is similar to:
 
 ```
 CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                       NAMES
 6a96207fed4b        kindest/node:v1.18.2   "/usr/local/bin/entr…"   27 seconds ago      Up 24 seconds       127.0.0.1:42223->6443/tcp   kind-control-plane
 ```
 
-If observing the filesystem of that container, one should see that the
+If observing the filesystem of that container, you should see that the
 `profiles/` directory has been successfully loaded into the default seccomp path
 of the kubelet. Use `docker exec` to run a command in the Pod:
 
-```
+```shell
+# Change 6a96207fed4b to the container ID you saw from "docker ps"
 docker exec -it 6a96207fed4b ls /var/lib/kubelet/seccomp/profiles
 ```
 
@@ -165,22 +154,65 @@ docker exec -it 6a96207fed4b ls /var/lib/kubelet/seccomp/profiles
 audit.json  fine-grained.json  violation.json
 ```
 
+You have verified that these seccomp profiles are available to the kubelet
+running within kind.
+
+## Enable the use of `RuntimeDefault` as the default seccomp profile for all workloads
+
+{{< feature-state state="alpha" for_k8s_version="v1.22" >}}
+
+`SeccompDefault` is an optional kubelet
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates) as
+well as corresponding `--seccomp-default`
+[command line flag](/docs/reference/command-line-tools-reference/kubelet).
+Both have to be enabled simultaneously to use the feature.
+
+If enabled, the kubelet will use the `RuntimeDefault` seccomp profile by default, which is
+defined by the container runtime, instead of using the `Unconfined` (seccomp disabled) mode.
+The default profiles aim to provide a strong set
+of security defaults while preserving the functionality of the workload. It is
+possible that the default profiles differ between container runtimes and their
+release versions, for example when comparing those from CRI-O and containerd.
+
+Some workloads may require a lower amount of syscall restrictions than others.
+This means that they can fail during runtime even with the `RuntimeDefault`
+profile. To mitigate such a failure, you can:
+
+- Run the workload explicitly as `Unconfined`.
+- Disable the `SeccompDefault` feature for the nodes. Also making sure that
+  workloads get scheduled on nodes where the feature is disabled.
+- Create a custom seccomp profile for the workload.
+
+If you were introducing this feature into production-like cluster, the Kubernetes project
+recommends that you enable this feature gate on a subset of your nodes and then
+test workload execution before rolling the change out cluster-wide.
+
+More detailed information about a possible upgrade and downgrade strategy can be
+found in the [related Kubernetes Enhancement Proposal (KEP)](https://github.com/kubernetes/enhancements/tree/a70cc18/keps/sig-node/2413-seccomp-by-default#upgrade--downgrade-strategy).
+
+Since the feature is in alpha state it is disabled per default. To enable it,
+pass the flags `--feature-gates=SeccompDefault=true --seccomp-default` to the
+`kubelet` CLI or enable it via the [kubelet configuration
+file](/docs/tasks/administer-cluster/kubelet-config-file/). To enable the
+feature gate in [kind](https://kind.sigs.k8s.io), ensure that `kind` provides
+the minimum required Kubernetes version and enables the `SeccompDefault` feature
+[in the kind configuration](https://kind.sigs.k8s.io/docs/user/quick-start/#enable-feature-gates-in-your-cluster):
+
+```yaml
+kind: Cluster
+apiVersion: kind.x-k8s.io/v1alpha4
+featureGates:
+  SeccompDefault: true
+```
+
 ## Create a Pod with a seccomp profile for syscall auditing
 
 To start off, apply the `audit.json` profile, which will log all syscalls of the
 process, to a new Pod.
 
-Download the correct manifest for your Kubernetes version:
+Here's a manifest for that Pod:
 
-{{< tabs name="audit_pods" >}}
-{{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/audit-pod.yaml" >}}
-{{< /tab >}}}
-{{{< tab name="Pre-v1.19 (deprecated)" >}}
-{{< codenew file="pods/security/seccomp/alpha/audit-pod.yaml" >}}
-{{< /tab >}}
-{{< /tabs >}}
-<br>
 
 {{< note >}}
 The functional support for the already deprecated seccomp annotations
@@ -192,14 +224,14 @@ the native API fields in favor of the annotations.
 
 Create the Pod in the cluster:
 
-```
-kubectl apply -f audit-pod.yaml
+```shell
+kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/audit-pod.yaml
 ```
 
 This profile does not restrict any syscalls, so the Pod should start
 successfully.
 
-```
+```shell
 kubectl get pod/audit-pod
 ```
 
@@ -209,28 +241,31 @@ audit-pod   1/1     Running   0          30s
 ```
 
 In order to be able to interact with this endpoint exposed by this
-container,create a NodePort Service that allows access to the endpoint from
-inside the kind control plane container.
+container, create a NodePort {{< glossary_tooltip text="Services" term_id="service" >}}
+that allows access to the endpoint from inside the kind control plane container.
 
-```
-kubectl expose pod/audit-pod --type NodePort --port 5678
+```shell
+kubectl expose pod audit-pod --type NodePort --port 5678
 ```
 
 Check what port the Service has been assigned on the node.
 
-```
-kubectl get svc/audit-pod
+```shell
+kubectl get service audit-pod
 ```
 
+The output is similar to:
 ```
 NAME        TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
 audit-pod   NodePort   10.111.36.142   <none>        5678:32373/TCP   72s
 ```
 
-Now you can `curl` the endpoint from inside the kind control plane container at
-the port exposed by this Service. Use `docker exec` to run a command in the Pod:
+Now you can use `curl` to access that endpoint from inside the kind control plane container,
+at the port exposed by this Service. Use `docker exec` to run the `curl` command within the
+container belonging to that control plane container:
 
-```
+```shell
+# Change 6a96207fed4b to the control plane container ID you saw from "docker ps"
 docker exec -it 6a96207fed4b curl localhost:32373
 ```
 
@@ -243,13 +278,14 @@ Because this Pod is running in a local cluster, you should be able to see those
 in `/var/log/syslog`. Open up a new terminal window and `tail` the output for
 calls from `http-echo`:
 
-```
+```shell
 tail -f /var/log/syslog | grep 'http-echo'
 ```
 
 You should already see some logs of syscalls made by `http-echo`, and if you
 `curl` the endpoint in the control plane container you will see more written.
 
+For example:
 ```
 Jul  6 15:37:40 my-machine kernel: [369128.669452] audit: type=1326 audit(1594067860.484:14536): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=29064 comm="http-echo" exe="/http-echo" sig=0 arch=c000003e syscall=51 compat=0 ip=0x46fe1f code=0x7ffc0000
 Jul  6 15:37:40 my-machine kernel: [369128.669453] audit: type=1326 audit(1594067860.484:14537): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=29064 comm="http-echo" exe="/http-echo" sig=0 arch=c000003e syscall=54 compat=0 ip=0x46fdba code=0x7ffc0000
@@ -268,9 +304,9 @@ for this container.
 
 Clean up that Pod and Service before moving to the next section:
 
-```
-kubectl delete pod/audit-pod
-kubectl delete svc/audit-pod
+```shell
+kubectl delete service audit-pod --wait
+kubectl delete pod audit-pod --wait --now
 ```
 
 ## Create Pod with seccomp Profile that Causes Violation
@@ -278,27 +314,20 @@ kubectl delete svc/audit-pod
 For demonstration, apply a profile to the Pod that does not allow for any
 syscalls.
 
-Download the correct manifest for your Kubernetes version:
+The manifest for this demonstration is:
 
-{{< tabs name="violation_pods" >}}
-{{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/violation-pod.yaml" >}}
-{{< /tab >}}}
-{{{< tab name="Pre-v1.19 (deprecated)" >}}
-{{< codenew file="pods/security/seccomp/alpha/violation-pod.yaml" >}}
-{{< /tab >}}
-{{< /tabs >}}
-<br>
 
-Create the Pod in the cluster:
+Attempt to create the Pod in the cluster:
 
-```
-kubectl apply -f violation-pod.yaml
+```shell
+kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/violation-pod.yaml
 ```
 
+The Pod creates, but there is an issue.
 If you check the status of the Pod, you should see that it failed to start.
 
-```
+```shell
 kubectl get pod/violation-pod
 ```
 
@@ -316,8 +345,8 @@ only the privileges they need.
 Clean up that Pod and Service before moving to the next section:
 
 ```
-kubectl delete pod/violation-pod
-kubectl delete svc/violation-pod
+kubectl delete service violation-pod --wait
+kubectl delete pod violation-pod --wait --now
 ```
 
 ## Create Pod with seccomp Profile that Only Allows Necessary Syscalls
@@ -329,61 +358,56 @@ but explicitly allowing a set of syscalls in the `"action": "SCMP_ACT_ALLOW"`
 block. Ideally, the container will run successfully and you will see no messages
 sent to `syslog`.
 
-Download the correct manifest for your Kubernetes version:
+The manifest for this example is:
 
-{{< tabs name="fine_pods" >}}
-{{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/fine-pod.yaml" >}}
-{{< /tab >}}}
-{{{< tab name="Pre-v1.19 (deprecated)" >}}
-{{< codenew file="pods/security/seccomp/alpha/fine-pod.yaml" >}}
-{{< /tab >}}
-{{< /tabs >}}
-<br>
 
 Create the Pod in your cluster:
 
+```shell
+kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/fine-pod.yaml
 ```
-kubectl apply -f fine-pod.yaml
-```
-
-The Pod should start successfully.
 
-```
-kubectl get pod/fine-pod
+```shell
+kubectl get pod fine-pod
 ```
 
+The Pod should be showing as having started successfully:
 ```
 NAME        READY   STATUS    RESTARTS   AGE
 fine-pod   1/1     Running   0          30s
 ```
 
-Open up a new terminal window and `tail` the output for calls from `http-echo`:
+Open up a new terminal window and use `tail` to monitor for log entries that
+mention calls from `http-echo`:
 
-```
+```shell
+# The log path on your computer might be different from "/var/log/syslog"
 tail -f /var/log/syslog | grep 'http-echo'
 ```
 
-Expose the Pod with a NodePort Service:
+Next, expose the Pod with a NodePort Service:
 
-```
-kubectl expose pod/fine-pod --type NodePort --port 5678
+```shell
+kubectl expose pod fine-pod --type NodePort --port 5678
 ```
 
 Check what port the Service has been assigned on the node:
 
-```
-kubectl get svc/fine-pod
+```shell
+kubectl get service fine-pod
 ```
 
+The output is similar to:
 ```
 NAME        TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
 fine-pod    NodePort   10.111.36.142   <none>        5678:32373/TCP   72s
 ```
 
-`curl` the endpoint from inside the kind control plane container:
+Use `curl` to access that endpoint from inside the kind control plane container:
 
-```
+```shell
+# Change 6a96207fed4b to the control plane container ID you saw from "docker ps"
 docker exec -it 6a96207fed4b curl localhost:32373
 ```
 
@@ -391,7 +415,7 @@ docker exec -it 6a96207fed4b curl localhost:32373
 just made some syscalls!
 ```
 
-You should see no output in the `syslog` because the profile allowed all
+You should see no output in the `syslog`. This is because the profile allowed all
 necessary syscalls and specified that an error should occur if one outside of
 the list is invoked. This is an ideal situation from a security perspective, but
 required some effort in analyzing the program. It would be nice if there was a
@@ -399,9 +423,9 @@ simple way to get closer to this security without requiring as much effort.
 
 Clean up that Pod and Service before moving to the next section:
 
-```
-kubectl delete pod/fine-pod
-kubectl delete svc/fine-pod
+```shell
+kubectl delete service fine-pod --wait
+kubectl delete pod fine-pod --wait --now
 ```
 
 ## Create Pod that uses the Container Runtime Default seccomp Profile
@@ -411,23 +435,13 @@ or not. The defaults can easily be applied in Kubernetes by using the
 `runtime/default` annotation or setting the seccomp type in the security context
 of a pod or container to `RuntimeDefault`.
 
-Download the correct manifest for your Kubernetes version:
-
-{{< tabs name="default_pods" >}}
-{{< tab name="v1.19 or Later (GA)" >}}
 {{< codenew file="pods/security/seccomp/ga/default-pod.yaml" >}}
-{{< /tab >}}}
-{{{< tab name="Pre-v1.19 (deprecated)" >}}
-{{< codenew file="pods/security/seccomp/alpha/default-pod.yaml" >}}
-{{< /tab >}}
-{{< /tabs >}}
-<br>
 
 The default seccomp profile should provide adequate access for most workloads.
 
 ## {{% heading "whatsnext" %}}
 
-Additional resources:
+You can learn more about Linux seccomp:
 
 * [A seccomp Overview](https://lwn.net/Articles/656307/)
 * [Seccomp Security Profiles for Docker](https://docs.docker.com/engine/security/seccomp/)

From 97a7bbcea8dd72bb5babb6f8eb2446f173667e6b Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sat, 16 Oct 2021 13:01:36 +0100
Subject: [PATCH 07/68] Expand on runtime default part of seccomp tutorial

---
 content/en/docs/tutorials/clusters/seccomp.md | 36 ++++++++++++++++---
 .../pods/security/seccomp/ga/default-pod.yaml |  6 ++--
 2 files changed, 34 insertions(+), 8 deletions(-)

diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index af8cb9e2efbeb..e3705f5d38c88 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -344,7 +344,7 @@ only the privileges they need.
 
 Clean up that Pod and Service before moving to the next section:
 
-```
+```shell
 kubectl delete service violation-pod --wait
 kubectl delete pod violation-pod --wait --now
 ```
@@ -431,13 +431,39 @@ kubectl delete pod fine-pod --wait --now
 ## Create Pod that uses the Container Runtime Default seccomp Profile
 
 Most container runtimes provide a sane set of default syscalls that are allowed
-or not. The defaults can easily be applied in Kubernetes by using the
-`runtime/default` annotation or setting the seccomp type in the security context
-of a pod or container to `RuntimeDefault`.
+or not. You can adopt these defaults for your workload by setting the seccomp
+type in the security context of a pod or container to `RuntimeDefault`.
+
+{{< note >}}
+If you have the `SeccompDefault` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled, then Pods use the `RuntimeDefault` seccomp profile whenever
+no other seccomp profile is specified. Otherwise, the default is `Unconfined`.
+{{< /note >}}
+
+Here's a manifest for a Pod that requests the `RuntimeDefault` seccomp profile
+for all its containers:
 
 {{< codenew file="pods/security/seccomp/ga/default-pod.yaml" >}}
 
-The default seccomp profile should provide adequate access for most workloads.
+Create that Pod:
+```shell
+kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/default-pod.yaml
+```
+
+```shell
+kubectl get pod default-pod
+```
+
+The Pod should be showing as having started successfully:
+```
+NAME        READY   STATUS    RESTARTS   AGE
+default-pod 1/1     Running   0          20s
+```
+
+Finally, now that you saw that work OK, clean up:
+
+```shell
+kubectl delete pod default-pod --wait --now
+```
 
 ## {{% heading "whatsnext" %}}
 
diff --git a/content/en/examples/pods/security/seccomp/ga/default-pod.yaml b/content/en/examples/pods/security/seccomp/ga/default-pod.yaml
index fbeec4c1676d3..b884ec5924221 100644
--- a/content/en/examples/pods/security/seccomp/ga/default-pod.yaml
+++ b/content/en/examples/pods/security/seccomp/ga/default-pod.yaml
@@ -1,9 +1,9 @@
 apiVersion: v1
 kind: Pod
 metadata:
-  name: audit-pod
+  name: default-pod
   labels:
-    app: audit-pod
+    app: default-pod
 spec:
   securityContext:
     seccompProfile:
@@ -12,6 +12,6 @@ spec:
   - name: test-container
     image: hashicorp/http-echo:0.2.3
     args:
-    - "-text=just made some syscalls!"
+    - "-text=just made some more syscalls!"
     securityContext:
       allowPrivilegeEscalation: false
\ No newline at end of file

From ee588f6d2badb3c0ccca204c848d85bd45497d57 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sat, 16 Oct 2021 12:24:32 +0100
Subject: [PATCH 08/68] Write headings in sentence case

Other than page titles, headings should be sentence case
---
 content/en/docs/tutorials/clusters/seccomp.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index e3705f5d38c88..a160e08542fb9 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -57,7 +57,7 @@ run as `Unconfined`.
 <!-- steps -->
 
 
-## Create Seccomp Profiles
+## Download example seccomp profiles {#download-profiles}
 
 The contents of these profiles will be explored later on, but for now go ahead
 and download them into a directory named `profiles/` so that they can be loaded
@@ -91,7 +91,7 @@ audit.json  fine-grained.json  violation.json
 ```
 
 
-## Create a Local Kubernetes Cluster with kind
+## Create a local Kubernetes cluster with kind
 
 
 For simplicity, [kind](https://kind.sigs.k8s.io/) can be used to create a single
@@ -309,7 +309,7 @@ kubectl delete service audit-pod --wait
 kubectl delete pod audit-pod --wait --now
 ```
 
-## Create Pod with seccomp Profile that Causes Violation
+## Create Pod with seccomp profile that causes violation
 
 For demonstration, apply a profile to the Pod that does not allow for any
 syscalls.
@@ -349,7 +349,7 @@ kubectl delete service violation-pod --wait
 kubectl delete pod violation-pod --wait --now
 ```
 
-## Create Pod with seccomp Profile that Only Allows Necessary Syscalls
+## Create Pod with seccomp profile that only allows necessary syscalls
 
 If you take a look at the `fine-pod.json`, you will notice some of the syscalls
 seen in the first example where the profile set `"defaultAction":
@@ -428,7 +428,7 @@ kubectl delete service fine-pod --wait
 kubectl delete pod fine-pod --wait --now
 ```
 
-## Create Pod that uses the Container Runtime Default seccomp Profile
+## Create Pod that uses the container runtime default seccomp profile
 
 Most container runtimes provide a sane set of default syscalls that are allowed
 or not. You can adopt these defaults for your workload by setting the seccomp

From 5d5a2125c58c741259d37a9f1bc1dcfc22e66284 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sat, 16 Oct 2021 12:24:54 +0100
Subject: [PATCH 09/68] Use a glossary tooltip for "node"

---
 content/en/docs/tutorials/clusters/seccomp.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md
index a160e08542fb9..2d4ec69999574 100644
--- a/content/en/docs/tutorials/clusters/seccomp.md
+++ b/content/en/docs/tutorials/clusters/seccomp.md
@@ -17,7 +17,7 @@ Seccomp stands for secure computing mode and has been a feature of the Linux
 kernel since version 2.6.12. It can be used to sandbox the privileges of a
 process, restricting the calls it is able to make from userspace into the
 kernel. Kubernetes lets you automatically apply seccomp profiles loaded onto a
-Node to your Pods and containers.
+{{< glossary_tooltip text="node" term_id="node" >}} to your Pods and containers.
 
 Identifying the privileges required for your workloads can be difficult. In this
 tutorial, you will go through how to load seccomp profiles into a local

From 11117310a52a86be8b023404c2a6dd5378ec197e Mon Sep 17 00:00:00 2001
From: Sahil Vazirani <svazirani@salesforce.com>
Date: Sun, 10 Oct 2021 23:09:52 -0700
Subject: [PATCH 10/68] GA TTLAfterFinish

---
 .../workloads/controllers/cron-jobs.md        |  2 +
 .../workloads/controllers/ttlafterfinished.md | 51 ++++++++-----------
 .../feature-gates.md                          |  5 +-
 3 files changed, 27 insertions(+), 31 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md
index c6cd4d13367ff..95a58dfc83203 100644
--- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md
+++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md
@@ -142,3 +142,5 @@ documents the format of CronJob `schedule` fields.
 For instructions on creating and working with cron jobs, and for an example of CronJob
 manifest, see [Running automated tasks with cron jobs](/docs/tasks/job/automated-tasks-with-cron-jobs).
 
+For instructions to clean up failed or completed jobs automatically, see 
+[Clean up Jobs automatically](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically)
diff --git a/content/en/docs/concepts/workloads/controllers/ttlafterfinished.md b/content/en/docs/concepts/workloads/controllers/ttlafterfinished.md
index 266e72a79fd0f..a51c88602fcf6 100644
--- a/content/en/docs/concepts/workloads/controllers/ttlafterfinished.md
+++ b/content/en/docs/concepts/workloads/controllers/ttlafterfinished.md
@@ -1,75 +1,68 @@
 ---
 reviewers:
 - janetkuo
-title: TTL Controller for Finished Resources
+title: Automatic Clean-up for Finished Jobs 
 content_type: concept
 weight: 70
 ---
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.21" state="beta" >}}
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
-The TTL controller provides a TTL (time to live) mechanism to limit the lifetime of resource
-objects that have finished execution. TTL controller only handles
-{{< glossary_tooltip text="Jobs" term_id="job" >}} for now,
-and may be expanded to handle other resources that will finish execution,
-such as Pods and custom resources.
-
-This feature is currently beta and enabled by default, and can be disabled via 
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-`TTLAfterFinished` in both kube-apiserver and kube-controller-manager.
+TTL-after-finished {{<glossary_tooltip text="controller" term_id="controller">}} provides a 
+TTL (time to live) mechanism to limit the lifetime of resource objects that 
+have finished execution. TTL controller only handles 
+{{< glossary_tooltip text="Jobs" term_id="job" >}}.
 
 <!-- body -->
 
-## TTL Controller
+## TTL-after-finished Controller
 
-The TTL controller only supports Jobs for now. A cluster operator can use this feature to clean
+The TTL-after-finished controller is only supported for Jobs. A cluster operator can use this feature to clean
 up finished Jobs (either `Complete` or `Failed`) automatically by specifying the
 `.spec.ttlSecondsAfterFinished` field of a Job, as in this
 [example](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically).
-The TTL controller will assume that a resource is eligible to be cleaned up
-TTL seconds after the resource has finished, in other words, when the TTL has expired. When the
-TTL controller cleans up a resource, it will delete it cascadingly, that is to say it will delete
-its dependent objects together with it. Note that when the resource is deleted,
+The TTL-after-finished controller will assume that a job is eligible to be cleaned up
+TTL seconds after the job has finished, in other words, when the TTL has expired. When the
+TTL-after-finished controller cleans up a job, it will delete it cascadingly, that is to say it will delete
+its dependent objects together with it. Note that when the job is deleted,
 its lifecycle guarantees, such as finalizers, will be honored.
 
 The TTL seconds can be set at any time. Here are some examples for setting the
 `.spec.ttlSecondsAfterFinished` field of a Job:
 
-* Specify this field in the resource manifest, so that a Job can be cleaned up
+* Specify this field in the job manifest, so that a Job can be cleaned up
   automatically some time after it finishes.
-* Set this field of existing, already finished resources, to adopt this new
+* Set this field of existing, already finished jobs, to adopt this new
   feature.
 * Use a
   [mutating admission webhook](/docs/reference/access-authn-authz/extensible-admission-controllers/#admission-webhooks)
-  to set this field dynamically at resource creation time. Cluster administrators can
-  use this to enforce a TTL policy for finished resources.
+  to set this field dynamically at job creation time. Cluster administrators can
+  use this to enforce a TTL policy for finished jobs.
 * Use a
   [mutating admission webhook](/docs/reference/access-authn-authz/extensible-admission-controllers/#admission-webhooks)
-  to set this field dynamically after the resource has finished, and choose
-  different TTL values based on resource status, labels, etc.
+  to set this field dynamically after the job has finished, and choose
+  different TTL values based on job status, labels, etc.
 
 ## Caveat
 
 ### Updating TTL Seconds
 
 Note that the TTL period, e.g. `.spec.ttlSecondsAfterFinished` field of Jobs,
-can be modified after the resource is created or has finished. However, once the
+can be modified after the job is created or has finished. However, once the
 Job becomes eligible to be deleted (when the TTL has expired), the system won't
 guarantee that the Jobs will be kept, even if an update to extend the TTL
 returns a successful API response.
 
 ### Time Skew
 
-Because TTL controller uses timestamps stored in the Kubernetes resources to
+Because TTL-after-finished controller uses timestamps stored in the Kubernetes jobs to
 determine whether the TTL has expired or not, this feature is sensitive to time
-skew in the cluster, which may cause TTL controller to clean up resource objects
+skew in the cluster, which may cause TTL-after-finish controller to clean up job objects
 at the wrong time.
 
-In Kubernetes, it's required to run NTP on all nodes
-(see [#6159](https://github.com/kubernetes/kubernetes/issues/6159#issuecomment-93844058))
-to avoid time skew. Clocks aren't always correct, but the difference should be
+Clocks aren't always correct, but the difference should be
 very small. Please be aware of this risk when setting a non-zero TTL.
 
 
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index d6390296599a8..b3921172378c4 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -190,8 +190,6 @@ different Kubernetes components.
 | `StorageVersionHash` | `true` | Beta | 1.15 | |
 | `SuspendJob` | `false` | Alpha | 1.21 | 1.21 |
 | `SuspendJob` | `true` | Beta | 1.22 | |
-| `TTLAfterFinished` | `false` | Alpha | 1.12 | 1.20 |
-| `TTLAfterFinished` | `true` | Beta | 1.21 | |
 | `TopologyAwareHints` | `false` | Alpha | 1.21 | |
 | `TopologyManager` | `false` | Alpha | 1.16 | 1.17 |
 | `TopologyManager` | `true` | Beta | 1.18 | |
@@ -439,6 +437,9 @@ different Kubernetes components.
 | `SupportPodPidsLimit` | `true` | GA | 1.20 | - |
 | `Sysctls` | `true` | Beta | 1.11 | 1.20 |
 | `Sysctls` | `true` | GA | 1.21 | |
+| `TTLAfterFinished` | `false` | Alpha | 1.12 | 1.20 |
+| `TTLAfterFinished` | `true` | Beta | 1.21 | 1.22 |
+| `TTLAfterFinished` | `true` | GA | 1.23 | - |
 | `TaintBasedEvictions` | `false` | Alpha | 1.6 | 1.12 |
 | `TaintBasedEvictions` | `true` | Beta | 1.13 | 1.17 |
 | `TaintBasedEvictions` | `true` | GA | 1.18 | - |

From 26280ee0c1104bb475d90beed2bf4937ff72fed3 Mon Sep 17 00:00:00 2001
From: Jonathan Dobson <jdobson@redhat.com>
Date: Wed, 27 Oct 2021 12:02:08 -0600
Subject: [PATCH 11/68] Move CSIVolumeFSGroupPolicy to GA

---
 .../reference/command-line-tools-reference/feature-gates.md  | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 91aa118fa293d..fab4148736448 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -83,8 +83,6 @@ different Kubernetes components.
 | `CSIMigrationvSphere` | `false` | Beta | 1.19 | |
 | `CSIStorageCapacity` | `false` | Alpha | 1.19 | 1.20 |
 | `CSIStorageCapacity` | `true` | Beta | 1.21 | |
-| `CSIVolumeFSGroupPolicy` | `false` | Alpha | 1.19 | 1.19 |
-| `CSIVolumeFSGroupPolicy` | `true` | Beta | 1.20 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
 | `CSRDuration` | `true` | Beta | 1.22 | |
 | `ConfigurableFSGroupPolicy` | `false` | Alpha | 1.18 | 1.19 |
@@ -255,6 +253,9 @@ different Kubernetes components.
 | `CSIServiceAccountToken` | `false` | Alpha | 1.20 | 1.20 |
 | `CSIServiceAccountToken` | `true` | Beta | 1.21 | 1.21 |
 | `CSIServiceAccountToken` | `true` | GA | 1.22 | |
+| `CSIVolumeFSGroupPolicy` | `false` | Alpha | 1.19 | 1.19 |
+| `CSIVolumeFSGroupPolicy` | `true` | Beta | 1.20 | 1.22 |
+| `CSIVolumeFSGroupPolicy` | `true` | GA | 1.23 | |
 | `CronJobControllerV2` | `false` | Alpha | 1.20 | 1.20 |
 | `CronJobControllerV2` | `true` | Beta | 1.21 | 1.21 |
 | `CronJobControllerV2` | `true` | GA | 1.22 | - |

From e50ce5f26925db442559ee4d307deb01c322424f Mon Sep 17 00:00:00 2001
From: Jordan Liggitt <liggitt@google.com>
Date: Mon, 25 Oct 2021 14:13:24 -0400
Subject: [PATCH 12/68] PodSecurity: runAsUser

---
 .../security/pod-security-standards.md         | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/content/en/docs/concepts/security/pod-security-standards.md b/content/en/docs/concepts/security/pod-security-standards.md
index f3b43344bf8ab..62e8943479902 100644
--- a/content/en/docs/concepts/security/pod-security-standards.md
+++ b/content/en/docs/concepts/security/pod-security-standards.md
@@ -373,6 +373,24 @@ fail validation.
 				</small>
 			</td>
 		</tr>
+		<tr>
+			<td style="white-space: nowrap">Running as Non-root user (v1.23+)</td>
+			<td>
+				<p>Containers must not set <tt>runAsUser</tt> to 0</p>
+				<p><strong>Restricted Fields</strong></p>
+				<ul>
+					<li><code>spec.securityContext.runAsUser</code></li>
+					<li><code>spec.containers[*].securityContext.runAsUser</code></li>
+					<li><code>spec.initContainers[*].securityContext.runAsUser</code></li>
+					<li><code>spec.ephemeralContainers[*].securityContext.runAsUser</code></li>
+				</ul>
+				<p><strong>Allowed Values</strong></p>
+				<ul>
+					<li>any non-zero value</li>
+					<li><code>undefined/null</code></li>
+				</ul>
+			</td>
+		</tr>
 		<tr>
 			<td style="white-space: nowrap">Non-root groups <em>(optional)</em></td>
 			<td>

From dabf80ae5629da135758d0e742f8d032e32069e3 Mon Sep 17 00:00:00 2001
From: Ayushman <ayushvidushi01@gmail.com>
Date: Tue, 2 Nov 2021 20:07:15 +0530
Subject: [PATCH 13/68] Added Note for Deprecation of Flexvolume

flexVolume

Signed-off-by: Ayushman <ayushvidushi01@gmail.com>
---
 content/en/docs/concepts/storage/volumes.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 56694dee66c32..e8f65df8cc251 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -1381,6 +1381,10 @@ plugin path on each node and in some cases the control plane nodes as well.
 Pods interact with FlexVolume drivers through the `flexvolume` in-tree volume plugin.
 For more details, see the [FlexVolume](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md) examples.
 
+{{< note >}}
+FlexVolume is deprecated starting v1.23. Out-of-tree CSI driver is the recommended way to write volume driver in Kubernetes. Maintainers of FlexVolume driver should implement a CSI Driver and move users of FlexVolume to CSI. Users of FlexVolume should move their workloads to CSI Driver.
+{{< /note >}}
+
 ## Mount propagation
 
 Mount propagation allows for sharing volumes mounted by a container to

From 14a003cb3b42967f6c516353c6a1f36989d54925 Mon Sep 17 00:00:00 2001
From: ahg-g <40361897+ahg-g@users.noreply.github.com>
Date: Wed, 10 Nov 2021 07:43:27 -0500
Subject: [PATCH 14/68] add docs for JobMutableNodeSchedulingDirectives
 (#30390)

---
 .../concepts/workloads/controllers/job.md     | 31 ++++++++++++++++++-
 .../feature-gates.md                          |  3 ++
 2 files changed, 33 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 54a4104c5e920..7ab98f6fbadf4 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -417,7 +417,10 @@ version of Kubernetes you're using](/docs/home/supported-doc-versions/).
 When a Job is created, the Job controller will immediately begin creating Pods
 to satisfy the Job's requirements and will continue to do so until the Job is
 complete. However, you may want to temporarily suspend a Job's execution and
-resume it later. To suspend a Job, you can update the `.spec.suspend` field of
+resume it later, or start Jobs in suspended state and have a custom controller
+decide later when to start them.
+
+To suspend a Job, you can update the `.spec.suspend` field of
 the Job to true; later, when you want to resume it again, update it to false.
 Creating a Job with `.spec.suspend` set to true will create it in the suspended
 state.
@@ -503,6 +506,32 @@ directly a result of toggling the `.spec.suspend` field. In the time between
 these two events, we see that no Pods were created, but Pod creation restarted
 as soon as the Job was resumed.
 
+### Mutable Scheduling Directives
+
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
+
+{{< note >}}
+In order to use this behavior, you must enable the `JobMutableNodeSchedulingDirectives`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/).
+It is enabled by default.
+{{< /note >}}
+
+In most cases a parallel job will want the pods to run with constraints, 
+like all in the same zone, or all either on GPU model x or y but not a mix of both.
+
+The [suspend](#suspending-a-job) field is the first step towards achieving those semantics. Suspend allows a 
+custom queue controller to decide when a job should start; However, once a job is unsuspended,
+a custom queue controller has no influence on where the pods of a job will actually land.
+
+This feature allows updating a Job's scheduling directives before it starts, which gives custom queue
+controllers the ability to influence pod placement while at the same time offloading actual 
+pod-to-node assignment to kube-scheduler. This is allowed only for suspended Jobs that have never 
+been unsuspended before.
+
+The fields in a Job's pod template that can be updated are node affinity, node selector, 
+tolerations, labels and annotations.
+
 ### Specifying your own Pod selector
 
 Normally, when you create a Job object, you do not specify `.spec.selector`.
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index fab4148736448..8b2d4dd18e062 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -133,6 +133,7 @@ different Kubernetes components.
 | `InTreePluginvSphereUnregister` | `false` | Alpha | 1.21 | |
 | `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
 | `IPv6DualStack` | `true` | Beta | 1.21 | |
+| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | |
 | `KubeletCredentialProviders` | `false` | Alpha | 1.20 | |
 | `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
@@ -794,6 +795,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
   Initializers admission plugin.
 - `IPv6DualStack`: Enable [dual stack](/docs/concepts/services-networking/dual-stack/)
   support for IPv6.
+- `JobMutableNodeSchedulingDirectives`: Allows updating node scheduling directives in
+  the pod template of [Job](/docs/concepts/workloads/controllers/job).
 - `JobTrackingWithFinalizers`: Enables tracking [Job](/docs/concepts/workloads/controllers/job)
   completions without relying on Pods remaining in the cluster indefinitely.
   The Job controller uses Pod finalizers and a field in the Job status to keep

From 575b742e0a800328ed357331d56d95f133b5f857 Mon Sep 17 00:00:00 2001
From: Aldo Culquicondor <acondor@google.com>
Date: Tue, 9 Nov 2021 14:15:45 -0500
Subject: [PATCH 15/68] Graduate JobTrackingWithFinalizers to beta

---
 content/en/docs/concepts/workloads/controllers/job.md    | 9 +++++----
 .../command-line-tools-reference/feature-gates.md        | 3 ++-
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 7ab98f6fbadf4..33bb415570521 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -601,18 +601,19 @@ mismatch.
 
 ### Job tracking with finalizers
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 {{< note >}}
 In order to use this behavior, you must enable the `JobTrackingWithFinalizers`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
 on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
 and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/).
-It is disabled by default.
+It is enabled by default.
 
 When enabled, the control plane tracks new Jobs using the behavior described
-below. Existing Jobs are unaffected. As a user, the only difference you would
-see is that the control plane tracking of Job completion is more accurate.
+below. Jobs created before the feature was enabled are unaffected. As a user,
+the only difference you would see is that the control plane tracking of Job
+completion is more accurate.
 {{< /note >}}
 
 When this feature isn't enabled, the Job {{< glossary_tooltip term_id="controller" >}}
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 8b2d4dd18e062..8cc2ed9cbc6a3 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -134,7 +134,8 @@ different Kubernetes components.
 | `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
 | `IPv6DualStack` | `true` | Beta | 1.21 | |
 | `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | |
-| `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | |
+| `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
+| `JobTrackingWithFinalizers` | `true` | Beta | 1.23 | |
 | `KubeletCredentialProviders` | `false` | Alpha | 1.20 | |
 | `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
 | `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | |

From 4b7784728a24bc5c8dcb71c89fcc11e432b3e163 Mon Sep 17 00:00:00 2001
From: Jordan Liggitt <liggitt@google.com>
Date: Wed, 3 Nov 2021 17:43:43 -0400
Subject: [PATCH 16/68] PodSecurity beta updates

---
 .../security/pod-security-admission.md        | 37 +++++++++++---
 .../admission-controllers.md                  |  2 +-
 .../feature-gates.md                          |  3 +-
 .../enforce-standards-admission-controller.md | 48 ++++++++++++++++++-
 .../enforce-standards-namespace-labels.md     |  2 +-
 .../migrate-from-psp.md                       |  2 +-
 6 files changed, 82 insertions(+), 12 deletions(-)

diff --git a/content/en/docs/concepts/security/pod-security-admission.md b/content/en/docs/concepts/security/pod-security-admission.md
index a1c87767c9be9..933dc62940876 100644
--- a/content/en/docs/concepts/security/pod-security-admission.md
+++ b/content/en/docs/concepts/security/pod-security-admission.md
@@ -13,13 +13,13 @@ min-kubernetes-server-version: v1.22
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 The Kubernetes [Pod Security Standards](/docs/concepts/security/pod-security-standards/) define
 different isolation levels for Pods. These standards let you define how you want to restrict the
 behavior of pods in a clear, consistent fashion.
 
-As an Alpha feature, Kubernetes offers a built-in _Pod Security_ {{< glossary_tooltip
+As an Beta feature, Kubernetes offers a built-in _Pod Security_ {{< glossary_tooltip
 text="admission controller" term_id="admission-controller" >}}, the successor
 to [PodSecurityPolicies](/docs/concepts/policy/pod-security-policy/). Pod security restrictions
 are applied at the {{< glossary_tooltip text="namespace" term_id="namespace" >}} level when pods
@@ -32,15 +32,40 @@ The PodSecurityPolicy API is deprecated and will be
 
 <!-- body -->
 
-## Enabling the Alpha feature
+## Enabling the `PodSecurity` admission plugin
 
-Setting pod security controls by namespace is an alpha feature. You must enable the `PodSecurity`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in order to use it.
+In v1.23, the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+is a Beta feature and is enabled by default.
+
+In v1.22, the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+is an Alpha feature and must be enabled in `kube-apiserver` in order to use the built-in admission plugin.
 
 ```shell
 --feature-gates="...,PodSecurity=true"
 ```
 
+## Alternative: installing the `PodSecurity` admission webhook
+
+For environments where the built-in `PodSecurity` admission plugin cannot be used,
+either because the cluster is older than v1.22, or the `PodSecurity` feature cannot be enabled,
+the `PodSecurity` admission logic is also available as a Beta [validating admission webhook](https://git.k8s.io/pod-security-admission/webhook).
+
+A pre-built container image, certificate generation scripts, and example manifests
+are available at [https://git.k8s.io/pod-security-admission/webhook](https://git.k8s.io/pod-security-admission/webhook).
+
+To install:
+```shell
+git clone git@github.com:kubernetes/pod-security-admission.git
+cd pod-security-admission/webhook
+make certs
+kubectl apply -k .
+```
+
+{{< note >}}
+The generated certificate is valid for 2 years. Before it expires,
+regenerate the certificate or remove the webhook in favor of the built-in admission plugin.
+{{< /note >}}
+
 ## Pod Security levels
 
 Pod Security admission places requirements on a Pod's [Security
@@ -52,7 +77,7 @@ page for an in-depth look at those requirements.
 
 ## Pod Security Admission labels for namespaces
 
-Provided that you have enabled this feature, you can configure namespaces to define the admission
+Once the feature is enabled or the webhook is installed, you can configure namespaces to define the admission
 control mode you want to use for pod security in each namespace. Kubernetes defines a set of 
 {{< glossary_tooltip term_id="label" text="labels" >}} that you can set to define which of the 
 predefined Pod Security Standard levels you want to use for a namespace. The label you select
diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md
index 0461c09f53229..7957ff7a4fcfa 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -698,7 +698,7 @@ admission plugin, which allows preventing pods from running on specifically tain
 
 ### PodSecurity {#podsecurity}
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 This is the replacement for the deprecated [PodSecurityPolicy](#podsecuritypolicy) admission controller
 defined in the next section. This admission controller acts on creation and modification of the pod and
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 91aa118fa293d..dc369aee3d037 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -159,7 +159,8 @@ different Kubernetes components.
 | `PodAffinityNamespaceSelector` | `true` | Beta | 1.22 | |
 | `PodOverhead` | `false` | Alpha | 1.16 | 1.17 |
 | `PodOverhead` | `true` | Beta | 1.18 | |
-| `PodSecurity` | `false` | Alpha | 1.22 | |
+| `PodSecurity` | `false` | Alpha | 1.22 | 1.22 |
+| `PodSecurity` | `true` | Beta | 1.23 | |
 | `PreferNominatedNode` | `false` | Alpha | 1.21 | 1.21 |
 | `PreferNominatedNode` | `true` | Beta | 1.22 | |
 | `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | 1.21 |
diff --git a/content/en/docs/tasks/configure-pod-container/enforce-standards-admission-controller.md b/content/en/docs/tasks/configure-pod-container/enforce-standards-admission-controller.md
index ef8206b1b6a9b..c2f9fae3f7c1e 100644
--- a/content/en/docs/tasks/configure-pod-container/enforce-standards-admission-controller.md
+++ b/content/en/docs/tasks/configure-pod-container/enforce-standards-admission-controller.md
@@ -15,10 +15,52 @@ You can configure this admission controller to set cluster-wide defaults and [ex
 
 {{% version-check %}}
 
-- Enable the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features).
+- Ensure the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features) is enabled.
 
 ## Configure the Admission Controller
 
+{{< tabs name="PodSecurityConfiguration_example_1" >}}
+{{% tab name="pod-security.admission.config.k8s.io/v1beta1" %}}
+```yaml
+apiVersion: apiserver.config.k8s.io/v1
+kind: AdmissionConfiguration
+plugins:
+- name: PodSecurity
+  configuration:
+    apiVersion: pod-security.admission.config.k8s.io/v1beta1
+    kind: PodSecurityConfiguration
+    # Defaults applied when a mode label is not set.
+    #
+    # Level label values must be one of:
+    # - "privileged" (default)
+    # - "baseline"
+    # - "restricted"
+    #
+    # Version label values must be one of:
+    # - "latest" (default) 
+    # - specific version like "v{{< skew latestVersion >}}"
+    defaults:
+      enforce: "privileged"
+      enforce-version: "latest"
+      audit: "privileged"
+      audit-version: "latest"
+      warn: "privileged"
+      warn-version: "latest"
+    exemptions:
+      # Array of authenticated usernames to exempt.
+      usernames: []
+      # Array of runtime class names to exempt.
+      runtimeClassNames: []
+      # Array of namespaces to exempt.
+      namespaces: []
+```
+
+{{< note >}}
+v1beta1 configuration requires v1.23+. For v1.22, use v1alpha1.
+{{< /note >}}
+
+{{% /tab %}}
+{{% tab name="pod-security.admission.config.k8s.io/v1alpha1" %}}
 ```yaml
 apiVersion: apiserver.config.k8s.io/v1
 kind: AdmissionConfiguration
@@ -51,4 +93,6 @@ plugins:
       runtimeClassNames: []
       # Array of namespaces to exempt.
       namespaces: []
-```
\ No newline at end of file
+```
+{{% /tab %}}
+{{< /tabs >}}
diff --git a/content/en/docs/tasks/configure-pod-container/enforce-standards-namespace-labels.md b/content/en/docs/tasks/configure-pod-container/enforce-standards-namespace-labels.md
index 9a4c3a44ed4c9..121f9b15e7c54 100644
--- a/content/en/docs/tasks/configure-pod-container/enforce-standards-namespace-labels.md
+++ b/content/en/docs/tasks/configure-pod-container/enforce-standards-namespace-labels.md
@@ -13,7 +13,7 @@ Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts
 
 {{% version-check %}}
 
-- Enable the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features).
+- Ensure the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features) is enabled.
 
 ## Requiring the `baseline` Pod Security Standard with namespace labels
 
diff --git a/content/en/docs/tasks/configure-pod-container/migrate-from-psp.md b/content/en/docs/tasks/configure-pod-container/migrate-from-psp.md
index f0ea2d02dfb02..adc8225e23894 100644
--- a/content/en/docs/tasks/configure-pod-container/migrate-from-psp.md
+++ b/content/en/docs/tasks/configure-pod-container/migrate-from-psp.md
@@ -17,7 +17,7 @@ admission controller. This can be done effectively using a combination of dry-ru
 
 {{% version-check %}}
 
-- Enable the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features).
+- Ensure the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features) is enabled.
 
 <!-- body -->
 

From 1e0796c4e4ae671329b1a5728d1e3af05b060c89 Mon Sep 17 00:00:00 2001
From: Cheng Xing <cxing@google.com>
Date: Wed, 10 Nov 2021 16:57:29 -0800
Subject: [PATCH 17/68] Delegate FSGroup to CSI beta

---
 .../en/docs/tasks/configure-pod-container/security-context.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/configure-pod-container/security-context.md b/content/en/docs/tasks/configure-pod-container/security-context.md
index 56bcc0f3f9211..ef9cbf620086b 100644
--- a/content/en/docs/tasks/configure-pod-container/security-context.md
+++ b/content/en/docs/tasks/configure-pod-container/security-context.md
@@ -186,7 +186,7 @@ and [`emptydir`](/docs/concepts/storage/volumes/#emptydir).
 
 ## Delegating volume permission and ownership change to CSI driver
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 If you deploy a [Container Storage Interface (CSI)](https://github.com/container-storage-interface/spec/blob/master/spec.md)
 driver which supports the `VOLUME_MOUNT_GROUP` `NodeServiceCapability`, the

From 4729b75ffb04203c2f1173c97fafdd194f217c0c Mon Sep 17 00:00:00 2001
From: Harry Bagdi <harrybagdi@gmail.com>
Date: Thu, 11 Nov 2021 08:51:52 -0800
Subject: [PATCH 18/68] graduate IngressClassNamespacedParams to GA

---
 content/en/docs/concepts/services-networking/ingress.md      | 2 +-
 .../reference/command-line-tools-reference/feature-gates.md  | 5 +++--
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index 6879b998db224..fbeb5289fb27d 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -224,7 +224,7 @@ reference additional implementation-specific configuration for this class.
 
 #### Namespace-scoped parameters
 
-{{< feature-state for_k8s_version="v1.22" state="beta" >}}
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
 `Parameters` field has a `scope` and `namespace` field that can be used to
 reference a namespace-specific resource for configuration of an Ingress class.
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index fab4148736448..a3ff10133e777 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -123,8 +123,6 @@ different Kubernetes components.
 | `HPAScaleToZero` | `false` | Alpha | 1.16 | |
 | `IndexedJob` | `false` | Alpha | 1.21 | 1.21 |
 | `IndexedJob` | `true` | Beta | 1.22 | |
-| `IngressClassNamespacedParams` | `false` | Alpha | 1.21 | 1.21 |
-| `IngressClassNamespacedParams` | `true` | Beta | 1.22 | |
 | `InTreePluginAWSUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginAzureDiskUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginAzureFileUnregister` | `false` | Alpha | 1.21 | |
@@ -324,6 +322,9 @@ different Kubernetes components.
 | `ImmutableEphemeralVolumes` | `false` | Alpha | 1.18 | 1.18 |
 | `ImmutableEphemeralVolumes` | `true` | Beta | 1.19 | 1.20 |
 | `ImmutableEphemeralVolumes` | `true` | GA | 1.21 | |
+| `IngressClassNamespacedParams` | `false` | Alpha | 1.21 | 1.21 |
+| `IngressClassNamespacedParams` | `true` | Beta | 1.22 | 1.22 |
+| `IngressClassNamespacedParams` | `true` | GA | 1.23 | - |
 | `Initializers` | `false` | Alpha | 1.7 | 1.13 |
 | `Initializers` | - | Deprecated | 1.14 | - |
 | `KubeletConfigFile` | `false` | Alpha | 1.8 | 1.9 |

From 65bceb18762f0c182dbbc50d9dfbeb478fcccc03 Mon Sep 17 00:00:00 2001
From: Patrick Ohly <patrick.ohly@intel.com>
Date: Thu, 4 Nov 2021 15:01:34 +0100
Subject: [PATCH 19/68] generic ephemeral volumes: document graduation to GA

---
 content/en/docs/concepts/storage/ephemeral-volumes.md      | 7 +------
 .../command-line-tools-reference/feature-gates.md          | 5 +++--
 2 files changed, 4 insertions(+), 8 deletions(-)

diff --git a/content/en/docs/concepts/storage/ephemeral-volumes.md b/content/en/docs/concepts/storage/ephemeral-volumes.md
index 1e811fb82a40a..5c9f9b21d318c 100644
--- a/content/en/docs/concepts/storage/ephemeral-volumes.md
+++ b/content/en/docs/concepts/storage/ephemeral-volumes.md
@@ -130,10 +130,7 @@ As a cluster administrator, you can use a [PodSecurityPolicy](/docs/concepts/pol
 
 ### Generic ephemeral volumes
 
-{{< feature-state for_k8s_version="v1.21" state="beta" >}}
-
-This feature requires the `GenericEphemeralVolume` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be
-enabled. Because this is a beta feature, it is enabled by default.
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
 Generic ephemeral volumes are similar to `emptyDir` volumes in the
 sense that they provide a per-pod directory for scratch data that is
@@ -245,7 +242,6 @@ PVCs indirectly if they can create Pods, even if they do not have
 permission to create PVCs directly. Cluster administrators must be
 aware of this. If this does not fit their security model, they have
 two choices:
-- Explicitly disable the feature through the feature gate.
 - Use a [Pod Security
   Policy](/docs/concepts/policy/pod-security-policy/) where the
   `volumes` list does not contain the `ephemeral` volume type
@@ -274,4 +270,3 @@ See [local ephemeral storage](/docs/concepts/configuration/manage-resources-cont
 
 - For more information on the design, see the
 [Generic ephemeral inline volumes KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1698-generic-ephemeral-volumes/README.md).
-- For more information on further development of this feature, see the [enhancement tracking issue #1698](https://github.com/kubernetes/enhancements/issues/1698).
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 91aa118fa293d..01b2310638f49 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -117,8 +117,6 @@ different Kubernetes components.
 | `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
 | `ExpandPersistentVolumes` | `true` | Beta | 1.11 | |
 | `ExperimentalHostUserNamespaceDefaulting` | `false` | Beta | 1.5 | |
-| `GenericEphemeralVolume` | `false` | Alpha | 1.19 | 1.20 |
-| `GenericEphemeralVolume` | `true` | Beta | 1.21 | |
 | `GracefulNodeShutdown` | `false` | Alpha | 1.20 | 1.20 |
 | `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
 | `HPAContainerMetrics` | `false` | Alpha | 1.20 | |
@@ -309,6 +307,9 @@ different Kubernetes components.
 | `ExternalPolicyForExternalIP` | `true` | GA | 1.18 | - |
 | `GCERegionalPersistentDisk` | `true` | Beta | 1.10 | 1.12 |
 | `GCERegionalPersistentDisk` | `true` | GA | 1.13 | - |
+| `GenericEphemeralVolume` | `false` | Alpha | 1.19 | 1.20 |
+| `GenericEphemeralVolume` | `true` | Beta | 1.21 | 1.22 |
+| `GenericEphemeralVolume` | `true` | GA | 1.23 | - |
 | `HugePageStorageMediumSize` | `false` | Alpha | 1.18 | 1.18 |
 | `HugePageStorageMediumSize` | `true` | Beta | 1.19 | 1.21 |
 | `HugePageStorageMediumSize` | `true` | GA | 1.22 | - |

From 771ee157a9d396284f1030d6b3a5de09b86e151e Mon Sep 17 00:00:00 2001
From: Lee Verberne <verb@google.com>
Date: Thu, 30 Sep 2021 22:25:58 +0200
Subject: [PATCH 20/68] Promote EphemeralContainers to beta

---
 .../concepts/workloads/pods/ephemeral-containers.md   | 11 +----------
 .../command-line-tools-reference/feature-gates.md     |  3 ++-
 .../debug-application-cluster/debug-running-pod.md    |  8 +-------
 3 files changed, 4 insertions(+), 18 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/ephemeral-containers.md b/content/en/docs/concepts/workloads/pods/ephemeral-containers.md
index c26a63b183b32..d32511da2868e 100644
--- a/content/en/docs/concepts/workloads/pods/ephemeral-containers.md
+++ b/content/en/docs/concepts/workloads/pods/ephemeral-containers.md
@@ -9,22 +9,13 @@ weight: 80
 
 <!-- overview -->
 
-{{< feature-state state="alpha" for_k8s_version="v1.22" >}}
+{{< feature-state state="beta" for_k8s_version="v1.23" >}}
 
 This page provides an overview of ephemeral containers: a special type of container
 that runs temporarily in an existing {{< glossary_tooltip term_id="pod" >}} to
 accomplish user-initiated actions such as troubleshooting. You use ephemeral
 containers to inspect services rather than to build applications.
 
-{{< warning >}}
-Ephemeral containers are in alpha state and are not suitable for production
-clusters. In accordance with the [Kubernetes Deprecation Policy](
-/docs/reference/using-api/deprecation-policy/), this alpha feature could change
-significantly in the future or be removed entirely.
-{{< /warning >}}
-
-
-
 <!-- body -->
 
 ## Understanding ephemeral containers
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..91eb1a0f6b5ec 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -106,7 +106,8 @@ different Kubernetes components.
 | `EfficientWatchResumption` | `true` | Beta | 1.21 | |
 | `EndpointSliceTerminatingCondition` | `false` | Alpha | 1.20 | 1.21 |
 | `EndpointSliceTerminatingCondition` | `true` | Beta | 1.22 | |
-| `EphemeralContainers` | `false` | Alpha | 1.16 | |
+| `EphemeralContainers` | `false` | Alpha | 1.16 | 1.22 |
+| `EphemeralContainers` | `true` | Beta | 1.23 | |
 | `ExpandCSIVolumes` | `false` | Alpha | 1.14 | 1.15 |
 | `ExpandCSIVolumes` | `true` | Beta | 1.16 | |
 | `ExpandedDNSConfig` | `false` | Alpha | 1.22 | |
diff --git a/content/en/docs/tasks/debug-application-cluster/debug-running-pod.md b/content/en/docs/tasks/debug-application-cluster/debug-running-pod.md
index 6009a76341103..9653ff05ef1ff 100644
--- a/content/en/docs/tasks/debug-application-cluster/debug-running-pod.md
+++ b/content/en/docs/tasks/debug-application-cluster/debug-running-pod.md
@@ -73,7 +73,7 @@ For more details, see [Get a Shell to a Running Container](
 
 ## Debugging with an ephemeral debug container {#ephemeral-container}
 
-{{< feature-state state="alpha" for_k8s_version="v1.22" >}}
+{{< feature-state state="beta" for_k8s_version="v1.23" >}}
 
 {{< glossary_tooltip text="Ephemeral containers" term_id="ephemeral-container" >}}
 are useful for interactive troubleshooting when `kubectl exec` is insufficient
@@ -83,12 +83,6 @@ https://github.com/GoogleContainerTools/distroless).
 
 ### Example debugging using ephemeral containers {#ephemeral-container-example}
 
-{{< note >}}
-The examples in this section require the `EphemeralContainers` [feature gate](
-/docs/reference/command-line-tools-reference/feature-gates/) enabled in your
-cluster and `kubectl` version v1.22 or later.
-{{< /note >}}
-
 You can use the `kubectl debug` command to add ephemeral containers to a
 running Pod. First, create a pod for the example:
 

From 8d6da018576a9a50acfcdb9f451021d5c1a000dc Mon Sep 17 00:00:00 2001
From: Swati Sehgal <swsehgal@redhat.com>
Date: Fri, 21 May 2021 00:39:30 +0100
Subject: [PATCH 21/68] podresource-api: Graduate GetAllocatableResources to
 Beta

Also, explicitly clarify the behavior of GetAllocatableResources
The explanation that GetAllocatableResources can be used to obtain available resources
on the node can be misinterpretted as an API that is used to obtain free/unallocated
resources on a node.

This PR adds additional text to clarify that this API endpoint only returns
allocatable resources which are resources exposed to kubelet as defined here:
https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable.

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
---
 .../compute-storage-net/device-plugins.md     | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
index 868d8d56e8ff6..6e766a86d6ed1 100644
--- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
+++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
@@ -197,6 +197,8 @@ service PodResourcesLister {
 }
 ```
 
+### `List` gRPC endpoint {#grpc-endpoint-list}
+
 The `List` endpoint provides information on resources of running pods, with details such as the
 id of exclusively allocated CPUs, device id as it was reported by device plugins and id of
 the NUMA node where these devices are allocated. Also, for NUMA-based machines, it contains the information about memory and hugepages reserved for a container.
@@ -247,9 +249,25 @@ message ContainerDevices {
 }
 ```
 
+### `GetAllocatableResources` gRPC endpoint {#grpc-endpoint-getallocatableresources}
+
+{{< feature-state state="beta" for_k8s_version="v1.23" >}}
+
 GetAllocatableResources provides information on resources initially available on the worker node.
 It provides more information than kubelet exports to APIServer.
 
+{{< note >}}
+`GetAllocatableResources` should only be used to evaluate [allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)
+resources on a node. If the goal is to evaluate free/unallocated resources it should be used in
+conjunction with the List() endpoint. The result obtained by `GetAllocatableResources` would remain
+the same unless the underlying resources exposed to kubelet change. This happens rarely but when
+it does (for example: hotplug/hotunplug, device health changes), client is expected to call
+`GetAlloctableResources` endpoint.
+However, calling `GetAllocatableResources` endpoint is not sufficient in case of cpu and/or memory
+update and Kubelet needs to be restarted to reflect the correct resource capacity and allocatable.
+{{< /note >}}
+
+
 ```gRPC
 // AllocatableResourcesResponses contains informations about all the devices known by the kubelet
 message AllocatableResourcesResponse {
@@ -259,6 +277,13 @@ message AllocatableResourcesResponse {
 }
 
 ```
+Starting from Kubernetes v1.23, the `GetAllocatableResources` is enabled by default.
+You can disable it by turning off the
+`KubeletPodResourcesGetAllocatable` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
+
+Preceding Kubernetes v1.23, to enable this feature `kubelet` must be started with the following flag:
+
+`--feature-gates=KubeletPodResourcesGetAllocatable=true`
 
 `ContainerDevices` do expose the topology information declaring to which NUMA cells the device is affine.
 The NUMA cells are identified using a opaque integer ID, which value is consistent to what device

From c7231c8d6d0045bba24ea475f44e5daa3525df3c Mon Sep 17 00:00:00 2001
From: Swati Sehgal <swsehgal@redhat.com>
Date: Tue, 5 Oct 2021 21:08:43 +0100
Subject: [PATCH 22/68] Explicitly state that GetCpuIds returns exclusive cpus

Based on the discussion here: https://github.com/kubernetes/kubernetes/pull/97415#discussion_r722548437
we explictly state that the GetCpuIds returned for a ContainerResource in the ListPodResourcesResponse
represent only exclusively allocated CPUs.

In order to evaluate the CPUs corresponding to the shared pool, List endpoint should be used in conjunction
with GetAllocatableResources endpoint. We highlight the steps that the client needs to take evaluate this.

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
---
 .../compute-storage-net/device-plugins.md                | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
index 6e766a86d6ed1..f14f78b13b6dc 100644
--- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
+++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
@@ -248,6 +248,15 @@ message ContainerDevices {
     TopologyInfo topology = 3;
 }
 ```
+{{< note >}}
+cpu_ids in the `ContainerResources` in the `List` endpoint correspond to exclusive CPUs allocated
+to a partilar container. If the goal is to evaluate CPUs that belong to the shared pool, the `List`
+endpoint needs to be used in conjunction with the `GetAllocatableResources` endpoint as explained
+below:
+1. Call `GetAllocatableResources` to get a list of all the allocatable CPUs
+2. Call `GetCpuIds` on all `ContainerResources` in the system
+3. Subtract out all of the CPUs from the `GetCpuIds` calls from the `GetAllocatableResources` call
+{{< /note >}}
 
 ### `GetAllocatableResources` gRPC endpoint {#grpc-endpoint-getallocatableresources}
 

From 378fc570b1863c0494e1541724f21eb49d287872 Mon Sep 17 00:00:00 2001
From: Kevin Klues <kklues@nvidia.com>
Date: Sat, 13 Nov 2021 17:06:40 +0100
Subject: [PATCH 23/68] Add description of distribute-cpus-across-numa
 CPUManager policy option

Signed-off-by: Kevin Klues <kklues@nvidia.com>
---
 .../cpu-management-policies.md                | 26 ++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
index 9eb7d7febb3d7..41fbe77cb039f 100644
--- a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
+++ b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
@@ -218,8 +218,11 @@ equal to one. The `nginx` container is granted 2 exclusive CPUs.
 
 #### Static policy options
 
+The following policy options exist for the static `CPUManager` policy:
+* `full-pcpus-only` (beta, visible by default)
+* `distribute-cpus-across-numa` (alpha, hidden by default)
+
 If the `full-pcpus-only` policy option is specified, the static policy will always allocate full physical cores.
-You can enable this option by adding `full-pcups-only=true` to the CPUManager policy options.
 By default, without this option, the static policy allocates CPUs using a topology-aware best-fit allocation.
 On SMT enabled systems, the policy can allocate individual virtual cores, which correspond to hardware threads.
 This can lead to different containers sharing the same physical cores; this behaviour in turn contributes
@@ -227,3 +230,24 @@ to the [noisy neighbours problem](https://en.wikipedia.org/wiki/Cloud_computing_
 With the option enabled, the pod will be admitted by the kubelet only if the CPU request of all its containers
 can be fulfilled by allocating full physical cores.
 If the pod does not pass the admission, it will be put in Failed state with the message `SMTAlignmentError`.
+
+If the `distribute-cpus-across-numa`policy option is specified, the static
+policy will evenly distribute CPUs across NUMA nodes in cases where more than
+one NUMA node is required to satisfy the allocation.
+By default, the `CPUManager` will pack CPUs onto one NUMA node until it is
+filled, with any remaining CPUs simply spilling over to the next NUMA node.
+This can cause undesired bottlenecks in parallel code relying on barriers (and
+similar synchronization primitivies), as this type of code tends to run only as
+fast as its slowest worker (which is slowed down by the fact that fewer CPUs
+are available on at least one NUMA node).
+By distributing CPUs evenly across NUMA nodes, application developers can more
+easily ensure that no single worker suffers from NUMA effects more than any
+other, improving the overall performance of these types of applications.
+
+The `full-pcpus-only` option can be enabled by adding `full-pcups-only=true` to
+the CPUManager policy options.
+Likewise, the `distribute-cpus-across-numa` option can be enabled by adding
+`distribute-cpus-across-numa=true` to the CPUManager policy options.
+When both are set, they are "additive" in the sense that CPUs will be
+distributed across NUMA nodes in chunks of full-pcpus rather than individual
+cores.

From c3073161f7f28b401dbdea1e5a97106aa9ad28f2 Mon Sep 17 00:00:00 2001
From: Patrick Ohly <patrick.ohly@intel.com>
Date: Tue, 16 Nov 2021 16:13:35 +0100
Subject: [PATCH 24/68] logging: structured logging, klog deprecation

This is primarily the docs PR for
- alpha: https://github.com/kubernetes/enhancements/issues/2845
- beta: https://github.com/kubernetes/enhancements/issues/1602

But as it touches the file, it also updates the examples and explanations to
reflect some recent observations.
---
 .../cluster-administration/system-logs.md     | 68 +++++++++++++++++--
 1 file changed, 63 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/cluster-administration/system-logs.md b/content/en/docs/concepts/cluster-administration/system-logs.md
index 0466837356023..58f123a1c87da 100644
--- a/content/en/docs/concepts/cluster-administration/system-logs.md
+++ b/content/en/docs/concepts/cluster-administration/system-logs.md
@@ -22,14 +22,62 @@ generates log messages for the Kubernetes system components.
 
 For more information about klog configuration, see the [Command line tool reference](/docs/reference/command-line-tools-reference/).
 
-An example of the klog native format:
+Kubernetes is in the process of simplifying logging in its components. The
+following klog command line flags [are
+deprecated](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
+starting with Kubernetes 1.23 and will be removed in a future release:
+
+- `--add-dir-header`
+- `--alsologtostderr`
+- `--log-backtrace-at`
+- `--log-dir`
+- `--log-file`
+- `--log-file-max-size`
+- `--logtostderr`
+- `--one-output`
+- `--skip-headers`
+- `--skip-log-headers`
+- `--stderrthreshold`
+
+Output will always be written to stderr, regardless of the output
+format. Output redirection is expected to be handled by the component which
+invokes a Kubernetes component. This can be a POSIX shell or a tool like
+systemd.
+
+In some cases, for example a distroless container or a Windows system service,
+those options are not available. Then the
+[`kube-log-runner`](https://github.com/kubernetes/kubernetes/blob/d2a8a81639fcff8d1221b900f66d28361a170654/staging/src/k8s.io/component-base/logs/kube-log-runner/README.md)
+binary can be used as wrapper around a Kubernetes component to redirect
+output. A prebuilt binary is included in several Kubernetes base images under
+its traditional name as `/go-runner` and as `kube-log-runner` in server and
+node release archives.
+
+This table shows how `kube-log-runner` invocations correspond to shell redirection:
+
+| Usage                                    | POSIX shell (such as bash) | `kube-log-runner <options> <cmd>`                           |
+| -----------------------------------------|----------------------------|-------------------------------------------------------------|
+| Merge stderr and stdout, write to stdout | `2>&1`                     | `kube-log-runner` (default behavior)                        |
+| Redirect both into log file              | `1>>/tmp/log 2>&1`         | `kube-log-runner -log-file=/tmp/log`                        |
+| Copy into log file and to stdout         | `2>&1 \| tee -a /tmp/log`  | `kube-log-runner -log-file=/tmp/log -also-stdout`           |
+| Redirect only stdout into log file       | `>/tmp/log`                | `kube-log-runner -log-file=/tmp/log -redirect-stderr=false` |
+
+### Klog output
+
+An example of the traditional klog native format:
 ```
 I1025 00:15:15.525108       1 httplog.go:79] GET /api/v1/namespaces/kube-system/pods/metrics-server-v0.3.1-57c75779f-9p8wg: (1.512ms) 200 [pod_nanny/v0.0.0 (linux/amd64) kubernetes/$Format 10.56.1.19:51756]
 ```
 
+The message string may contain line breaks:
+```
+I1025 00:15:15.525108       1 example.go:79] This is a message
+which has a line break.
+```
+
+
 ### Structured Logging
 
-{{< feature-state for_k8s_version="v1.19" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 {{< warning >}}
 Migration to structured log messages is an ongoing process. Not all log messages are structured in this version. When parsing log files, you must also handle unstructured log messages.
@@ -38,9 +86,11 @@ Log formatting and value serialization are subject to change.
 {{< /warning>}}
 
 Structured logging introduces a uniform structure in log messages allowing for programmatic extraction of information. You can store and process structured logs with less effort and cost.
-New message format is backward compatible and enabled by default.
+The code which generates a log message determines whether it uses the traditional unstructured klog output
+or structured logging.
 
-Format of structured logs:
+The default formatting of structured log messages is as text, with a format that
+is backward compatible with traditional klog:
 
 ```ini
 <klog header> "<message>" <key1>="<value1>" <key2>="<value2>" ...
@@ -52,6 +102,13 @@ Example:
 I1025 00:15:15.525108       1 controller_utils.go:116] "Pod status updated" pod="kube-system/kubedns" status="ready"
 ```
 
+Strings are quoted. Other values are formatted with
+[`%+v`](https://pkg.go.dev/fmt#hdr-Printing), which may cause log messages to
+continue on the next line [depending on the data](https://github.com/kubernetes/kubernetes/issues/106428).
+```
+I1025 00:15:15.525108       1 example.go:116] "Example" data="This is text with a line break\nand \"quotation marks\"." someInt=1 someFloat=0.1 someStruct={StringField: First line,
+second line.}
+```
 
 ### JSON log format
 
@@ -82,7 +139,7 @@ Example of JSON log format (pretty printed):
 
 Keys with special meaning:
 * `ts` - timestamp as Unix time (required, float)
-* `v` - verbosity (required, int, default 0)
+* `v` - verbosity (only for info and not for error messages, int)
 * `err` - error string (optional, string)
 * `msg` - message (required, string)
 
@@ -139,4 +196,5 @@ The `logrotate` tool rotates logs daily, or once the log size is greater than 10
 
 * Read about the [Kubernetes Logging Architecture](/docs/concepts/cluster-administration/logging/)
 * Read about [Structured Logging](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1602-structured-logging)
+* Read about [deprecation of klog flags](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
 * Read about the [Conventions for logging severity](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md)

From 2474ff93aad946c158cec46477601963b2dcda26 Mon Sep 17 00:00:00 2001
From: Rob Scott <robertjscott@google.com>
Date: Wed, 17 Nov 2021 11:21:54 -0800
Subject: [PATCH 25/68] Updating Topology Aware Hints docs for 1.23

---
 .../service-traffic-policy.md                 |  2 +-
 .../topology-aware-hints.md                   |  6 +--
 .../feature-gates.md                          |  3 +-
 .../enabling-topology-aware-hints.md          | 40 -------------------
 4 files changed, 5 insertions(+), 46 deletions(-)
 delete mode 100644 content/en/docs/tasks/administer-cluster/enabling-topology-aware-hints.md

diff --git a/content/en/docs/concepts/services-networking/service-traffic-policy.md b/content/en/docs/concepts/services-networking/service-traffic-policy.md
index fb55a3d833e8a..0a62cb49348c7 100644
--- a/content/en/docs/concepts/services-networking/service-traffic-policy.md
+++ b/content/en/docs/concepts/services-networking/service-traffic-policy.md
@@ -68,6 +68,6 @@ When the [feature gate](/docs/reference/command-line-tools-reference/feature-gat
 
 ## {{% heading "whatsnext" %}}
 
-* Read about [enabling Topology Aware Hints](/docs/tasks/administer-cluster/enabling-topology-aware-hints)
+* Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints)
 * Read about [Service External Traffic Policy](/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip)
 * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
diff --git a/content/en/docs/concepts/services-networking/topology-aware-hints.md b/content/en/docs/concepts/services-networking/topology-aware-hints.md
index f471caff6b24d..d07a75d9234f2 100644
--- a/content/en/docs/concepts/services-networking/topology-aware-hints.md
+++ b/content/en/docs/concepts/services-networking/topology-aware-hints.md
@@ -9,7 +9,7 @@ weight: 45
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.21" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
 _Topology Aware Hints_ enable topology aware routing by including suggestions
 for how clients should consume endpoints. This approach adds metadata to enable
@@ -35,8 +35,7 @@ can then consume those hints, and use them to influence how traffic to is routed
 
 ## Using Topology Aware Hints
 
-If you have [enabled](/docs/tasks/administer-cluster/enabling-topology-aware-hints) the
-overall feature, you can activate Topology Aware Hints for a Service by setting the
+You can activate Topology Aware Hints for a Service by setting the
 `service.kubernetes.io/topology-aware-hints` annotation to `auto`. This tells
 the EndpointSlice controller to set topology hints if it is deemed safe.
 Importantly, this does not guarantee that hints will always be set.
@@ -156,5 +155,4 @@ zone.
 
 ## {{% heading "whatsnext" %}}
 
-* Read about [enabling Topology Aware Hints](/docs/tasks/administer-cluster/enabling-topology-aware-hints/)
 * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..67c1ac569c223 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -186,7 +186,8 @@ different Kubernetes components.
 | `StorageVersionHash` | `true` | Beta | 1.15 | |
 | `SuspendJob` | `false` | Alpha | 1.21 | 1.21 |
 | `SuspendJob` | `true` | Beta | 1.22 | |
-| `TopologyAwareHints` | `false` | Alpha | 1.21 | |
+| `TopologyAwareHints` | `false` | Alpha | 1.21 | 1.22 |
+| `TopologyAwareHints` | `true` | Beta | 1.23 | |
 | `TopologyManager` | `false` | Alpha | 1.16 | 1.17 |
 | `TopologyManager` | `true` | Beta | 1.18 | |
 | `VolumeCapacityPriority` | `false` | Alpha | 1.21 | - |
diff --git a/content/en/docs/tasks/administer-cluster/enabling-topology-aware-hints.md b/content/en/docs/tasks/administer-cluster/enabling-topology-aware-hints.md
deleted file mode 100644
index dadc653f4e196..0000000000000
--- a/content/en/docs/tasks/administer-cluster/enabling-topology-aware-hints.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-reviewers:
-- robscott
-title: Enabling Topology Aware Hints
-content_type: task
-min-kubernetes-server-version: 1.21
----
-
-<!-- overview -->
-{{< feature-state for_k8s_version="v1.21" state="alpha" >}}
-
-_Topology Aware Hints_ enable topology aware routing with topology hints
-included in {{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}.
-This approach tries to keep traffic close to where it originated from;
-you might do this to reduce costs, or to improve network performance.
-
-## {{% heading "prerequisites" %}}
-
-  {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-
-The following prerequisite is needed in order to enable topology aware hints:
-
-* Configure the {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to run in
-  iptables mode or IPVS mode
-* Ensure that you have not disabled EndpointSlices
-
-## Enable Topology Aware Hints
-
-To enable service topology hints, enable the `TopologyAwareHints` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) for the
-kube-apiserver, kube-controller-manager, and kube-proxy:
-
-```
---feature-gates="TopologyAwareHints=true"
-```
-
-## {{% heading "whatsnext" %}}
-
-* Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints) for Services
-* Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)

From a209e3d65eac600521b33f9091b6263703127432 Mon Sep 17 00:00:00 2001
From: Bridget Kromhout <bridget@kromhout.org>
Date: Fri, 13 Aug 2021 17:08:22 -0500
Subject: [PATCH 26/68] Dual-stack to stable in 1.23

Co-Authored-By: Tim Bannister <tim@scalefactory.com>
---
 .../cluster-administration/networking.md      |  2 +-
 .../services-networking/dual-stack.md         | 11 +++-------
 .../feature-gates.md                          |  5 +++--
 .../tools/kubeadm/dual-stack-support.md       | 22 +++++--------------
 .../docs/tasks/network/validate-dual-stack.md |  5 ++++-
 5 files changed, 16 insertions(+), 29 deletions(-)

diff --git a/content/en/docs/concepts/cluster-administration/networking.md b/content/en/docs/concepts/cluster-administration/networking.md
index da9aeed0bad01..b9759799dc05e 100644
--- a/content/en/docs/concepts/cluster-administration/networking.md
+++ b/content/en/docs/concepts/cluster-administration/networking.md
@@ -64,7 +64,7 @@ This means that containers within a `Pod` can all reach each other's ports on
 usage, but this is no different from processes in a VM.  This is called the
 "IP-per-pod" model.
 
-How this is implemented is a detail of the particular container runtime in use.
+How this is implemented is a detail of the particular container runtime in use. Likewise, the networking option you choose may support [dual-stack IPv4/IPv6 networking](/docs/concepts/services-networking/dual-stack/); implementations vary.
 
 It is possible to request ports on the `Node` itself which forward to your `Pod`
 (called host ports), but this is a very niche operation. How that forwarding is
diff --git a/content/en/docs/concepts/services-networking/dual-stack.md b/content/en/docs/concepts/services-networking/dual-stack.md
index a85226beed05c..b7ea673621c0d 100644
--- a/content/en/docs/concepts/services-networking/dual-stack.md
+++ b/content/en/docs/concepts/services-networking/dual-stack.md
@@ -16,7 +16,7 @@ weight: 70
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.21" state="beta" >}}
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
 IPv4/IPv6 dual-stack networking enables the allocation of both IPv4 and IPv6 addresses to {{< glossary_tooltip text="Pods" term_id="pod" >}} and {{< glossary_tooltip text="Services" term_id="service" >}}.
 
@@ -47,8 +47,6 @@ The following prerequisites are needed in order to utilize IPv4/IPv6 dual-stack
 
 ## Configure IPv4/IPv6 dual-stack
 
-To use IPv4/IPv6 dual-stack, ensure the `IPv6DualStack` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for the relevant components of your cluster. (Starting in 1.21, IPv4/IPv6 dual-stack defaults to enabled.)
-
 To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments:
 
    * kube-apiserver:
@@ -65,9 +63,6 @@ An example of an IPv4 CIDR: `10.244.0.0/16` (though you would supply your own ad
 
 An example of an IPv6 CIDR: `fdXY:IJKL:MNOP:15::/64` (this shows the format but is not a valid address - see [RFC 4193](https://tools.ietf.org/html/rfc4193))
 
-Starting in 1.21, IPv4/IPv6 dual-stack defaults to enabled.
-You can disable it when necessary by specifying `--feature-gates="IPv6DualStack=false"`
-on the kube-apiserver, kube-controller-manager, kubelet, and kube-proxy command line.
 {{< /note >}}
 
 ## Services
@@ -81,7 +76,7 @@ set the `.spec.ipFamilyPolicy` field to one of the following values:
 
 * `SingleStack`: Single-stack service. The control plane allocates a cluster IP for the Service, using the first configured service cluster IP range.
 * `PreferDualStack`:
-  * Allocates IPv4 and IPv6 cluster IPs for the Service. (If the cluster has `--feature-gates="IPv6DualStack=false"`, this setting follows the same behavior as `SingleStack`.)
+  * Allocates IPv4 and IPv6 cluster IPs for the Service.
 * `RequireDualStack`: Allocates Service `.spec.ClusterIPs` from both IPv4 and IPv6 address ranges.
   * Selects the `.spec.ClusterIP` from the list of `.spec.ClusterIPs` based on the address family of the first element in the `.spec.ipFamilies` array.
 
@@ -124,7 +119,7 @@ These examples demonstrate the behavior of various dual-stack Service configurat
 
 #### Dual-stack defaults on existing Services
 
-These examples demonstrate the default behavior when dual-stack is newly enabled on a cluster where Services already exist. (Upgrading an existing cluster to 1.21 will enable dual-stack unless `--feature-gates="IPv6DualStack=false"` is set.)
+These examples demonstrate the default behavior when dual-stack is newly enabled on a cluster where Services already exist. (Upgrading an existing cluster to 1.21 or beyond will enable dual-stack.)
 
 1. When dual-stack is enabled on a cluster, existing Services (whether `IPv4` or `IPv6`) are configured by the control plane to set `.spec.ipFamilyPolicy` to `SingleStack` and set `.spec.ipFamilies` to the address family of the existing Service. The existing Service cluster IP will be stored in `.spec.ClusterIPs`.
 
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..f74a78bb4c511 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -127,8 +127,6 @@ different Kubernetes components.
 | `InTreePluginGCEUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginOpenStackUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginvSphereUnregister` | `false` | Alpha | 1.21 | |
-| `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
-| `IPv6DualStack` | `true` | Beta | 1.21 | |
 | `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.23 | |
@@ -331,6 +329,9 @@ different Kubernetes components.
 | `IngressClassNamespacedParams` | `true` | GA | 1.23 | - |
 | `Initializers` | `false` | Alpha | 1.7 | 1.13 |
 | `Initializers` | - | Deprecated | 1.14 | - |
+| `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
+| `IPv6DualStack` | `true` | Beta | 1.21 | 1.22 |
+| `IPv6DualStack` | `true` | GA | 1.23 | - |
 | `KubeletConfigFile` | `false` | Alpha | 1.8 | 1.9 |
 | `KubeletConfigFile` | - | Deprecated | 1.10 | - |
 | `KubeletPluginsWatcher` | `false` | Alpha | 1.11 | 1.11 |
diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md b/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
index 283f3348749e3..f2d250c296fba 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
@@ -7,9 +7,9 @@ min-kubernetes-server-version: 1.21
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.21" state="beta" >}}
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
-Your Kubernetes cluster can run in [dual-stack](/docs/concepts/services-networking/dual-stack/) networking mode, which means that cluster networking lets you use either address family. In a dual-stack cluster, the control plane can assign both an IPv4 address and an IPv6 address to a single {{< glossary_tooltip text="Pod" term_id="pod" >}} or a {{< glossary_tooltip text="Service" term_id="service" >}}.
+Your Kubernetes cluster includes [dual-stack](/docs/concepts/services-networking/dual-stack/) networking, which means that cluster networking lets you use either address family. In a cluster, the control plane can assign both an IPv4 address and an IPv6 address to a single {{< glossary_tooltip text="Pod" term_id="pod" >}} or a {{< glossary_tooltip text="Service" term_id="service" >}}.
 
 <!-- body -->
 
@@ -28,10 +28,8 @@ The size of the IP address allocations should be suitable for the number of Pods
 Services that you are planning to run.
 
 {{< note >}}
-If you are upgrading an existing cluster then, by default, the `kubeadm upgrade` command
-changes the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-`IPv6DualStack` to `true` if that is not already enabled.
-However, `kubeadm` does not support making modifications to the pod IP address range
+If you are upgrading an existing cluster with the `kubeadm upgrade` command,
+`kubeadm` does not support making modifications to the pod IP address range
 (“cluster CIDR”) nor to the cluster's Service address range (“Service CIDR”).
 {{< /note >}}
 
@@ -51,8 +49,6 @@ To make things clearer, here is an example kubeadm [configuration file](https://
 ---
 apiVersion: kubeadm.k8s.io/v1beta3
 kind: ClusterConfiguration
-featureGates:
-  IPv6DualStack: true
 networking:
   podSubnet: 10.244.0.0/16,2001:db8:42:0::/56
   serviceSubnet: 10.96.0.0/16,2001:db8:42:1::/112
@@ -132,23 +128,15 @@ kubeadm join --config=kubeadm-config.yaml
 ### Create a single-stack cluster
 
 {{< note >}}
-Enabling the dual-stack feature doesn't mean that you need to use dual-stack addressing.
+Dual-stack support doesn't mean that you need to use dual-stack addressing.
 You can deploy a single-stack cluster that has the dual-stack networking feature enabled.
 {{< /note >}}
 
-In 1.21 the `IPv6DualStack` feature is Beta and the feature gate is defaulted to `true`. To disable the feature you must configure the feature gate to `false`. Note that once the feature is GA, the feature gate will be removed.
-
-```shell
-kubeadm init --feature-gates IPv6DualStack=false
-```
-
 To make things more clear, here is an example kubeadm [configuration file](https://pkg.go.dev/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3) `kubeadm-config.yaml` for the single-stack control plane node.
 
 ```yaml
 apiVersion: kubeadm.k8s.io/v1beta3
 kind: ClusterConfiguration
-featureGates:
-  IPv6DualStack: false
 networking:
   podSubnet: 10.244.0.0/16
   serviceSubnet: 10.96.0.0/16
diff --git a/content/en/docs/tasks/network/validate-dual-stack.md b/content/en/docs/tasks/network/validate-dual-stack.md
index 717bac27ad188..549c60b003d47 100644
--- a/content/en/docs/tasks/network/validate-dual-stack.md
+++ b/content/en/docs/tasks/network/validate-dual-stack.md
@@ -3,7 +3,7 @@ reviewers:
 - lachie83
 - khenidak
 - bridgetkromhout
-min-kubernetes-server-version: v1.20
+min-kubernetes-server-version: v1.23
 title: Validate IPv4/IPv6 dual-stack
 content_type: task
 ---
@@ -21,6 +21,9 @@ This document shares how to validate IPv4/IPv6 dual-stack enabled Kubernetes clu
 
 {{< version-check >}}
 
+{{< note >}}
+While you can validate with an earlier version, the feature is only GA and officially supported since v1.23.
+{{< /note >}}
 
 
 <!-- steps -->

From 466561c47c9421d0271db764ddf0bea461d4c877 Mon Sep 17 00:00:00 2001
From: ravisantoshgudimetla <ravisantoshgudimetla@gmail.com>
Date: Wed, 10 Nov 2021 12:56:10 -0500
Subject: [PATCH 27/68] [docs]: Promote STS minReadySeconds to beta

---
 .../workloads/controllers/statefulset.md      | 22 ++++++++++---------
 .../feature-gates.md                          |  3 ++-
 2 files changed, 14 insertions(+), 11 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index 6b65ba1f3b71c..4f12bb179608a 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -77,6 +77,7 @@ spec:
       app: nginx # has to match .spec.template.metadata.labels
   serviceName: "nginx"
   replicas: 3 # by default is 1
+  minReadySeconds: 10 # by default is 0
   template:
     metadata:
       labels:
@@ -112,6 +113,17 @@ In the above example:
 The name of a StatefulSet object must be a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 
+
+### Minimum ready seconds
+
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
+
+`.spec.minReadySeconds` is an optional field that specifies the minimum number of seconds for which a newly
+created Pod should be ready without any of its containers crashing, for it to be considered available.
+Please note that this feature is beta and enabled by default. Please opt out by unsetting the StatefulSetMinReadySeconds flag, if you don't
+want this feature to be enabled. This field defaults to 0 (the Pod will be considered 
+available as soon as it is ready). To learn more about when a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
+
 ## Pod Selector
 
 You must set the `.spec.selector` field of a StatefulSet to match the labels of its `.spec.template.metadata.labels`. Prior to Kubernetes 1.8, the `.spec.selector` field was defaulted when omitted. In 1.8 and later versions, failing to specify a matching Pod Selector will result in a validation error during StatefulSet creation.
@@ -284,16 +296,6 @@ After reverting the template, you must also delete any Pods that StatefulSet had
 already attempted to run with the bad configuration.
 StatefulSet will then begin to recreate the Pods using the reverted template.
 
-### Minimum ready seconds
-
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
-
-`.spec.minReadySeconds` is an optional field that specifies the minimum number of seconds for which a newly
-created Pod should be ready without any of its containers crashing, for it to be considered available.
-This defaults to 0 (the Pod will be considered available as soon as it is ready). To learn more about when
-a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
-
-Please note that this field only works if you enable the `StatefulSetMinReadySeconds` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
 
 ## {{% heading "whatsnext" %}}
 
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 8b2d4dd18e062..1ab8c95fdb8ce 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -182,7 +182,8 @@ different Kubernetes components.
 | `ServiceLoadBalancerClass` | `true` | Beta | 1.22 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
-| `StatefulSetMinReadySeconds` | `false` | Alpha | 1.22 | |
+| `StatefulSetMinReadySeconds` | `false` | Alpha | 1.22 | 1.22 |
+| `StatefulSetMinReadySeconds` | `true` | Beta | 1.23 | |
 | `StorageVersionAPI` | `false` | Alpha | 1.20 | |
 | `StorageVersionHash` | `false` | Alpha | 1.14 | 1.14 |
 | `StorageVersionHash` | `true` | Beta | 1.15 | |

From 40d431a42c78ff96206aba2eebbdecbe018fa85e Mon Sep 17 00:00:00 2001
From: Michelle Au <msau@google.com>
Date: Mon, 15 Nov 2021 13:51:53 -0800
Subject: [PATCH 28/68] update on-by-default for csi migration providers

---
 .../command-line-tools-reference/feature-gates.md        | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..96abe1230dc7a 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -71,13 +71,16 @@ different Kubernetes components.
 | `CSIMigration` | `false` | Alpha | 1.14 | 1.16 |
 | `CSIMigration` | `true` | Beta | 1.17 | |
 | `CSIMigrationAWS` | `false` | Alpha | 1.14 | |
-| `CSIMigrationAWS` | `false` | Beta | 1.17 | |
+| `CSIMigrationAWS` | `false` | Beta | 1.17 | 1.22 |
+| `CSIMigrationAWS` | `true` | Beta | 1.23 | |
 | `CSIMigrationAzureDisk` | `false` | Alpha | 1.15 | 1.18 |
-| `CSIMigrationAzureDisk` | `false` | Beta | 1.19 | |
+| `CSIMigrationAzureDisk` | `false` | Beta | 1.19 | 1.22 |
+| `CSIMigrationAzureDisk` | `true` | Beta | 1.23 | |
 | `CSIMigrationAzureFile` | `false` | Alpha | 1.15 | 1.19 |
 | `CSIMigrationAzureFile` | `false` | Beta | 1.21 | |
 | `CSIMigrationGCE` | `false` | Alpha | 1.14 | 1.16 |
-| `CSIMigrationGCE` | `false` | Beta | 1.17 | |
+| `CSIMigrationGCE` | `false` | Beta | 1.17 | 1.22 |
+| `CSIMigrationGCE` | `true` | Beta | 1.23 | |
 | `CSIMigrationOpenStack` | `false` | Alpha | 1.14 | 1.17 |
 | `CSIMigrationOpenStack` | `true` | Beta | 1.18 | |
 | `CSIMigrationvSphere` | `false` | Beta | 1.19 | |

From ee39fdc2ad7ee34b8893ec6b08dfd2d235d518b5 Mon Sep 17 00:00:00 2001
From: Joseph Burnett <josephburnett@google.com>
Date: Thu, 18 Nov 2021 11:22:40 +0100
Subject: [PATCH 29/68] Update docs with HPA v2 stable.

---
 .../horizontal-pod-autoscale-walkthrough.md   | 10 ++---
 .../horizontal-pod-autoscale.md               | 41 ++++++++++---------
 2 files changed, 27 insertions(+), 24 deletions(-)

diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
index 545e268a101a2..f5582b9416a0d 100644
--- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
@@ -184,9 +184,9 @@ Autoscaling the replicas may take a few minutes.
 ## Autoscaling on multiple metrics and custom metrics
 
 You can introduce additional metrics to use when autoscaling the `php-apache` Deployment
-by making use of the `autoscaling/v2beta2` API version.
+by making use of the `autoscaling/v2` API version.
 
-First, get the YAML of your HorizontalPodAutoscaler in the `autoscaling/v2beta2` form:
+First, get the YAML of your HorizontalPodAutoscaler in the `autoscaling/v2` form:
 
 ```shell
 kubectl get hpa php-apache -o yaml > /tmp/hpa-v2.yaml
@@ -195,7 +195,7 @@ kubectl get hpa php-apache -o yaml > /tmp/hpa-v2.yaml
 Open the `/tmp/hpa-v2.yaml` file in an editor, and you should see YAML which looks like this:
 
 ```yaml
-apiVersion: autoscaling/v2beta2
+apiVersion: autoscaling/v2
 kind: HorizontalPodAutoscaler
 metadata:
   name: php-apache
@@ -287,7 +287,7 @@ For example, if you had your monitoring system collecting metrics about network
 you could update the definition above using `kubectl edit` to look like this:
 
 ```yaml
-apiVersion: autoscaling/v2beta2
+apiVersion: autoscaling/v2
 kind: HorizontalPodAutoscaler
 metadata:
   name: php-apache
@@ -411,7 +411,7 @@ access to any metric, so cluster administrators should take care when exposing i
 
 ## Appendix: Horizontal Pod Autoscaler Status Conditions
 
-When using the `autoscaling/v2beta2` form of the HorizontalPodAutoscaler, you will be able to see
+When using the `autoscaling/v2` form of the HorizontalPodAutoscaler, you will be able to see
 *status conditions* set by Kubernetes on the HorizontalPodAutoscaler.  These status conditions indicate
 whether or not the HorizontalPodAutoscaler is able to scale, and whether or not it is currently restricted
 in any way.
diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
index 27165d0ca7f2f..3208035a975db 100644
--- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
+++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
@@ -62,7 +62,7 @@ or the custom metrics API (for all other metrics).
 
 * For object metrics and external metrics, a single metric is fetched, which describes
   the object in question. This metric is compared to the target
-  value, to produce a ratio as above. In the `autoscaling/v2beta2` API
+  value, to produce a ratio as above. In the `autoscaling/v2` API
   version, this value can optionally be divided by the number of Pods before the
   comparison is made.
 
@@ -161,18 +161,17 @@ fluctuating metric values.
 
 ## API Object
 
-The Horizontal Pod Autoscaler is an API resource in the Kubernetes `autoscaling` API group.
-The current stable version, which only includes support for CPU autoscaling,
-can be found in the `autoscaling/v1` API version.
-
-The beta version, which includes support for scaling on memory and custom metrics,
-can be found in `autoscaling/v2beta2`. The new fields introduced in `autoscaling/v2beta2`
-are preserved as annotations when working with `autoscaling/v1`.
+The Horizontal Pod Autoscaler is an API resource in the Kubernetes
+`autoscaling` API group.  The current stable version can be found in
+the `autoscaling/v2` API version which includes support for scaling on
+memory and custom metrics. The new fields introduced in
+`autoscaling/v2` are preserved as annotations when working with
+`autoscaling/v1`.
 
 When you create a HorizontalPodAutoscaler API object, make sure the name specified is a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 More details about the API object can be found at
-[HorizontalPodAutoscaler Object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#horizontalpodautoscaler-v1-autoscaling).
+[HorizontalPodAutoscaler Object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#horizontalpodautoscaler-v2-autoscaling).
 
 
 ## Support for Horizontal Pod Autoscaler in kubectl
@@ -299,7 +298,7 @@ the old container name from the HPA specification.
 
 ## Support for multiple metrics
 
-Kubernetes 1.6 adds support for scaling based on multiple metrics. You can use the `autoscaling/v2beta2` API
+Kubernetes 1.6 adds support for scaling based on multiple metrics. You can use the `autoscaling/v2` API
 version to specify multiple metrics for the Horizontal Pod Autoscaler to scale on. Then, the Horizontal Pod
 Autoscaler controller will evaluate each metric, and propose a new scale based on that metric. The largest of the
 proposed scales will be used as the new scale.
@@ -313,9 +312,11 @@ custom metrics is still available, these metrics will not be available for use b
 annotations for specifying which custom metrics to scale on are no longer honored by the Horizontal Pod Autoscaler controller.
 {{< /note >}}
 
-Kubernetes 1.6 adds support for making use of custom metrics in the Horizontal Pod Autoscaler.
-You can add custom metrics for the Horizontal Pod Autoscaler to use in the `autoscaling/v2beta2` API.
-Kubernetes then queries the new custom metrics API to fetch the values of the appropriate custom metrics.
+You can also use a HorizontalPodAutoscaler to change the scale of a
+workload based on custom metrics.  You can add custom metrics for the
+Horizontal Pod Autoscaler to use in the `autoscaling/v2` API.
+Kubernetes then queries the new custom metrics API to fetch the values
+of the appropriate custom metrics.
 
 See [Support for metrics APIs](#support-for-metrics-apis) for the requirements.
 
@@ -349,12 +350,14 @@ and [the walkthrough for using external metrics](/docs/tasks/run-application/hor
 
 Starting from
 [v1.18](https://github.com/kubernetes/enhancements/blob/master/keps/sig-autoscaling/853-configurable-hpa-scale-velocity/README.md)
-the `v2beta2` API allows scaling behavior to be configured through the HPA
-`behavior` field. Behaviors are specified separately for scaling up and down in
-`scaleUp` or `scaleDown` section under the `behavior` field. A stabilization
-window can be specified for both directions which prevents the flapping of the
-number of the replicas in the scaling target. Similarly specifying scaling
-policies controls the rate of change of replicas while scaling.
+the `v2beta2` API (and from v1.23 the `v2` API) allows scaling
+behavior to be configured through the HPA `behavior` field. Behaviors
+are specified separately for scaling up and down in `scaleUp` or
+`scaleDown` section under the `behavior` field. A stabilization window
+can be specified for both directions which prevents the flapping of
+the number of the replicas in the scaling target. Similarly specifying
+scaling policies controls the rate of change of replicas while
+scaling.
 
 ### Scaling Policies
 

From 7c1e61a697e268885a5cb8e248eb8fd48b59d6ac Mon Sep 17 00:00:00 2001
From: Peter Hunt <pehunt@redhat.com>
Date: Mon, 22 Nov 2021 15:19:46 -0500
Subject: [PATCH 30/68] Document PodAndContainerStatsFromCRI feature

Signed-off-by: Peter Hunt <pehunt@redhat.com>
---
 .../command-line-tools-reference/feature-gates.md        | 3 +++
 .../resource-metrics-pipeline.md                         | 9 +++++++++
 2 files changed, 12 insertions(+)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index a4eb41f3f41a3..b433a951ab91b 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -362,6 +362,7 @@ different Kubernetes components.
 | `PersistentLocalVolumes` | `false` | Alpha | 1.7 | 1.9 |
 | `PersistentLocalVolumes` | `true` | Beta | 1.10 | 1.13 |
 | `PersistentLocalVolumes` | `true` | GA | 1.14 | - |
+| `PodAndContainerStatsFromCRI` | `false` | Alpha | 1.23 | |
 | `PodDisruptionBudget` | `false` | Alpha | 1.3 | 1.4 |
 | `PodDisruptionBudget` | `true` | Beta | 1.5 | 1.20 |
 | `PodDisruptionBudget` | `true` | GA | 1.21 | - |
@@ -862,6 +863,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
    feature which allows users to influence ReplicaSet downscaling order.
 - `PersistentLocalVolumes`: Enable the usage of `local` volume type in Pods.
   Pod affinity has to be specified if requesting a `local` volume.
+- `PodAndContainerStatsFromCRI`: Configure the kubelet to gather container and pod stats from the CRI container runtime
+   rather than gathering them from cAdvisor.
 - `PodDisruptionBudget`: Enable the [PodDisruptionBudget](/docs/tasks/run-application/configure-pdb/) feature.
 - `PodAffinityNamespaceSelector`: Enable the [Pod Affinity Namespace Selector](/docs/concepts/scheduling-eviction/assign-pod-node/#namespace-selector)
   and [CrossNamespacePodAffinity](/docs/concepts/policy/resource-quotas/#cross-namespace-pod-affinity-quota) quota scope features.
diff --git a/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md b/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md
index a8c24693dcda7..b0e9ec4690c3a 100644
--- a/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md
+++ b/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md
@@ -65,3 +65,12 @@ Metrics Server collects metrics from the Summary API, exposed by
 
 Learn more about the metrics server in
 [the design doc](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/metrics-server.md).
+
+### Summary API Source
+The [Kubelet](/docs/reference/command-line-tools-reference/kubelet/) gathers stats at node, volume, pod and container level, and omits
+them in the [Summary API](https://github.com/kubernetes/kubernetes/blob/7d309e0104fedb57280b261e5677d919cb2a0e2d/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go)
+for consumers to read.
+
+Pre-1.23, these resources have been primarily gathered from [cAdvisor](https://github.com/google/cadvisor). However, in 1.23 with the
+introduction of the `PodAndContainerStatsFromCRI` FeatureGate, container and pod level stats can be gathered by the CRI implementation.
+Note: this also requires support from the CRI implementations (containerd >= 1.6.0, CRI-O >= 1.23.0).

From 7d8483e0e4ebdddd5f03dcb455ee8047eacd6b85 Mon Sep 17 00:00:00 2001
From: Francesco Romani <fromani@redhat.com>
Date: Tue, 14 Sep 2021 18:01:51 +0200
Subject: [PATCH 31/68] node: cpumanager: document the graduation process

Document the graduation process and the maturity level
of the cpumanager policy options, and the new feature gate
involved. No changes regarding the existing options.

For more details: https://github.com/kubernetes/enhancements/pull/2933
Signed-off-by: Francesco Romani <fromani@redhat.com>
---
 .../administer-cluster/cpu-management-policies.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
index 41fbe77cb039f..076cbe61497cc 100644
--- a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
+++ b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md
@@ -60,6 +60,13 @@ duration as `--node-status-update-frequency`.
 
 The behavior of the static policy can be fine-tuned using the `--cpu-manager-policy-options` flag.
 The flag takes a comma-separated list of `key=value` policy options.
+This feature can be disabled completely using the `CPUManagerPolicyOptions` feature gate.
+
+The policy options are split into two groups: alpha quality (hidden by default) and beta quality
+(visible by default). The groups are guarded respectively by the `CPUManagerPolicyAlphaOptions`
+and `CPUManagerPolicyBetaOptions` feature gates. Diverging from the Kubernetes standard, these
+feature gates guard groups of options, because it would have been too cumbersome to add a feature
+gate for each individual option.
 
 ### None policy
 
@@ -218,6 +225,12 @@ equal to one. The `nginx` container is granted 2 exclusive CPUs.
 
 #### Static policy options
 
+You can toggle groups of options on and off based upon their maturity level
+using the following feature gates:
+* `CPUManagerPolicyBetaOptions` default enabled. Disable to hide beta-level options.
+* `CPUManagerPolicyAlphaOptions` default disabled. Enable to show alpha-level options.
+You will still have to enable each option using the `CPUManagerPolicyOptions` kubelet option.
+
 The following policy options exist for the static `CPUManager` policy:
 * `full-pcpus-only` (beta, visible by default)
 * `distribute-cpus-across-numa` (alpha, hidden by default)
@@ -237,7 +250,7 @@ one NUMA node is required to satisfy the allocation.
 By default, the `CPUManager` will pack CPUs onto one NUMA node until it is
 filled, with any remaining CPUs simply spilling over to the next NUMA node.
 This can cause undesired bottlenecks in parallel code relying on barriers (and
-similar synchronization primitivies), as this type of code tends to run only as
+similar synchronization primitives), as this type of code tends to run only as
 fast as its slowest worker (which is slowed down by the fact that fewer CPUs
 are available on at least one NUMA node).
 By distributing CPUs evenly across NUMA nodes, application developers can more

From d42a12c2eb2cd43137e1c694296991f68ec410cb Mon Sep 17 00:00:00 2001
From: Aldo Culquicondor <acondor@google.com>
Date: Mon, 22 Nov 2021 09:44:38 -0500
Subject: [PATCH 32/68] Add JobReadyPods feature gate

---
 .../reference/command-line-tools-reference/feature-gates.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index a4eb41f3f41a3..d8513ad955ef2 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -129,6 +129,7 @@ different Kubernetes components.
 | `InTreePluginOpenStackUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginvSphereUnregister` | `false` | Alpha | 1.21 | |
 | `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | |
+| `JobReadyPods` | `false` | Alpha | 1.23 | |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.23 | |
 | `KubeletCredentialProviders` | `false` | Alpha | 1.20 | |
@@ -803,6 +804,11 @@ Each feature gate is designed for enabling/disabling a specific feature:
   support for IPv6.
 - `JobMutableNodeSchedulingDirectives`: Allows updating node scheduling directives in
   the pod template of [Job](/docs/concepts/workloads/controllers/job).
+- `JobReadyPods`: Enables tracking the number of Pods that have a `Ready`
+  [condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions).
+  The count of `Ready` pods is recorded in the
+  [status](/docs/reference/kubernetes-api/workload-resources/job-v1/#JobStatus)
+  of a [Job](/docs/concepts/workloads/controllers/job) status.
 - `JobTrackingWithFinalizers`: Enables tracking [Job](/docs/concepts/workloads/controllers/job)
   completions without relying on Pods remaining in the cluster indefinitely.
   The Job controller uses Pod finalizers and a field in the Job status to keep

From 159234a0a6332e1007a8700e27eec9aaa861a622 Mon Sep 17 00:00:00 2001
From: Mengjiao Liu <mengjiao.liu@daocloud.io>
Date: Tue, 23 Nov 2021 15:51:22 +0800
Subject: [PATCH 33/68] kubelet: sysctls allows slashes as a separator

---
 .../docs/tasks/administer-cluster/sysctl-cluster.md   | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/content/en/docs/tasks/administer-cluster/sysctl-cluster.md b/content/en/docs/tasks/administer-cluster/sysctl-cluster.md
index f81623982ff5d..791df4a2b4e6b 100644
--- a/content/en/docs/tasks/administer-cluster/sysctl-cluster.md
+++ b/content/en/docs/tasks/administer-cluster/sysctl-cluster.md
@@ -13,6 +13,17 @@ This document describes how to configure and use kernel parameters within a
 Kubernetes cluster using the {{< glossary_tooltip term_id="sysctl" >}}
 interface.
 
+{{< note >}}
+Starting from Kubernetes version 1.23, the kubelet supports the use of either `/` or `.`
+as separators for sysctl names. 
+For example, you can represent the same sysctl name as `kernel.shm_rmid_forced` using a
+period as the separator, or as `kernel/shm_rmid_forced` using a slash as a separator.
+For more sysctl parameter conversion method details, please refer to
+the page [sysctl.d(5)](https://man7.org/linux/man-pages/man5/sysctl.d.5.html) from
+the Linux man-pages project.
+Setting Sysctls for a Pod and PodSecurityPolicy features do not yet support 
+setting sysctls with slashes.
+{{< /note >}}
 ## {{% heading "prerequisites" %}}
 
 

From 74dcb53cc5abf8a4680d9b4f7a6ce8e112cce0f1 Mon Sep 17 00:00:00 2001
From: kerthcet <kerthcet@gmail.com>
Date: Thu, 25 Nov 2021 11:26:25 +0800
Subject: [PATCH 34/68] add migration docs for scheduler component config api
 from v1beta2 to v1beta3

Signed-off-by: kerthcet <kerthcet@gmail.com>
---
 .../en/docs/reference/scheduling/config.md    | 33 ++-----
 .../en/docs/reference/scheduling/policies.md  | 96 +------------------
 2 files changed, 10 insertions(+), 119 deletions(-)

diff --git a/content/en/docs/reference/scheduling/config.md b/content/en/docs/reference/scheduling/config.md
index bce8d36b5c7f0..dd883d3bac9fe 100644
--- a/content/en/docs/reference/scheduling/config.md
+++ b/content/en/docs/reference/scheduling/config.md
@@ -20,8 +20,7 @@ by implementing one or more of these extension points.
 
 You can specify scheduling profiles by running `kube-scheduler --config <filename>`,
 using the
-KubeSchedulerConfiguration ([v1beta1](/docs/reference/config-api/kube-scheduler-config.v1beta1/)
-or [v1beta2](/docs/reference/config-api/kube-scheduler-config.v1beta2/))
+KubeSchedulerConfiguration ([v1beta2](/docs/reference/config-api/kube-scheduler-config.v1beta2/))
 struct.
 
 A minimal configuration looks as follows:
@@ -179,30 +178,6 @@ that are not enabled by default:
   volume limits can be satisfied for the node.
   Extension points: `filter`.
 
-The following plugins are deprecated and can only be enabled in a `v1beta1`
-configuration:
-
-- `NodeResourcesLeastAllocated`: Favors nodes that have a low allocation of
-  resources.
-  Extension points: `score`.
-- `NodeResourcesMostAllocated`: Favors nodes that have a high allocation of
-  resources.
-  Extension points: `score`.
-- `RequestedToCapacityRatio`: Favor nodes according to a configured function of
-  the allocated resources.
-  Extension points: `score`.
-- `NodeLabel`: Filters and / or scores a node according to configured
-  {{< glossary_tooltip text="label(s)" term_id="label" >}}.
-  Extension points: `filter`, `score`.
-- `ServiceAffinity`: Checks that Pods that belong to a
-  {{< glossary_tooltip term_id="service" >}} fit in a set of nodes defined by
-  configured labels. This plugin also favors spreading the Pods belonging to a
-  Service across nodes.
-  Extension points: `preFilter`, `filter`, `score`.
-- `NodePreferAvoidPods`: Prioritizes nodes according to the node annotation
-  `scheduler.alpha.kubernetes.io/preferAvoidPods`.
-  Extension points: `score`.
-
 ### Multiple profiles
 
 You can configure `kube-scheduler` to run more than one profile.
@@ -285,7 +260,13 @@ only has one pending pods queue.
 * A plugin enabled in a v1beta2 configuration file takes precedence over the default configuration for that plugin.
 
 * Invalid `host` or `port` configured for scheduler healthz and metrics bind address will cause validation failure.
+{{% /tab %}}
 
+{{% tab name="v1beta2 → v1beta3" %}}
+* Three plugins' weight are increased by default:
+  * `InterPodAffinity` from 1 to 2
+  * `NodeAffinity` from 1 to 2
+  * `TaintToleration` from 1 to 3
 {{% /tab %}}
 {{< /tabs >}}
 
diff --git a/content/en/docs/reference/scheduling/policies.md b/content/en/docs/reference/scheduling/policies.md
index 99291c2b373e7..d9a6d92cfe89a 100644
--- a/content/en/docs/reference/scheduling/policies.md
+++ b/content/en/docs/reference/scheduling/policies.md
@@ -6,99 +6,10 @@ weight: 10
 
 <!-- overview -->
 
-A scheduling Policy can be used to specify the *predicates* and *priorities*
-that the {{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}}
-runs to [filter and score nodes](/docs/concepts/scheduling-eviction/kube-scheduler/#kube-scheduler-implementation),
-respectively.
+In Kubernetes versions before v1.23, a scheduling policy can be used to specify the *predicates* and *priorities* process. For example, you can set a scheduling policy by
+running `kube-scheduler --policy-config-file <filename>` or `kube-scheduler --policy-configmap <ConfigMap>`.
 
-You can set a scheduling policy by running
-`kube-scheduler --policy-config-file <filename>` or
-`kube-scheduler --policy-configmap <ConfigMap>`
-and using the [Policy type](/docs/reference/config-api/kube-scheduler-policy-config.v1/).
-
-<!-- body -->
-
-## Predicates
-
-The following *predicates* implement filtering:
-
-- `PodFitsHostPorts`: Checks if a Node has free ports (the network protocol kind)
-  for the Pod ports the Pod is requesting.
-
-- `PodFitsHost`: Checks if a Pod specifies a specific Node by its hostname.
-
-- `PodFitsResources`: Checks if the Node has free resources (eg, CPU and Memory)
-  to meet the requirement of the Pod.
-
-- `MatchNodeSelector`: Checks if a Pod's Node {{< glossary_tooltip term_id="selector" >}}
-   matches the Node's {{< glossary_tooltip text="label(s)" term_id="label" >}}.
-
-- `NoVolumeZoneConflict`: Evaluate if the {{< glossary_tooltip text="Volumes" term_id="volume" >}}
-  that a Pod requests are available on the Node, given the failure zone restrictions for
-  that storage.
-
-- `NoDiskConflict`: Evaluates if a Pod can fit on a Node due to the volumes it requests,
-   and those that are already mounted.
-
-- `MaxCSIVolumeCount`: Decides how many {{< glossary_tooltip text="CSI" term_id="csi" >}}
-  volumes should be attached, and whether that's over a configured limit.
-
-- `PodToleratesNodeTaints`: checks if a Pod's {{< glossary_tooltip text="tolerations" term_id="toleration" >}}
-  can tolerate the Node's {{< glossary_tooltip text="taints" term_id="taint" >}}.
-
-- `CheckVolumeBinding`: Evaluates if a Pod can fit due to the volumes it requests.
-  This applies for both bound and unbound
-  {{< glossary_tooltip text="PVCs" term_id="persistent-volume-claim" >}}.
-
-## Priorities
-
-The following *priorities* implement scoring:
-
-- `SelectorSpreadPriority`: Spreads Pods across hosts, considering Pods that
-   belong to the same {{< glossary_tooltip text="Service" term_id="service" >}},
-   {{< glossary_tooltip term_id="statefulset" >}} or
-   {{< glossary_tooltip term_id="replica-set" >}}.
-
-- `InterPodAffinityPriority`: Implements preferred
-  [inter pod affininity and antiaffinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity).
-
-- `LeastRequestedPriority`: Favors nodes with fewer requested resources. In other
-  words, the more Pods that are placed on a Node, and the more resources those
-  Pods use, the lower the ranking this policy will give.
-
-- `MostRequestedPriority`: Favors nodes with most requested resources. This policy
-  will fit the scheduled Pods onto the smallest number of Nodes needed to run your
-  overall set of workloads.
-
-- `RequestedToCapacityRatioPriority`: Creates a requestedToCapacity based ResourceAllocationPriority using default resource scoring function shape.
-
-- `BalancedResourceAllocation`: Favors nodes with balanced resource usage.
-
-- `NodePreferAvoidPodsPriority`: Prioritizes nodes according to the node annotation
-  `scheduler.alpha.kubernetes.io/preferAvoidPods`. You can use this to hint that
-  two different Pods shouldn't run on the same Node.
-
-- `NodeAffinityPriority`: Prioritizes nodes according to node affinity scheduling
-   preferences indicated in PreferredDuringSchedulingIgnoredDuringExecution.
-   You can read more about this in [Assigning Pods to Nodes](/docs/concepts/scheduling-eviction/assign-pod-node/).
-
-- `TaintTolerationPriority`: Prepares the priority list for all the nodes, based on
-  the number of intolerable taints on the node. This policy adjusts a node's rank
-  taking that list into account.
-
-- `ImageLocalityPriority`: Favors nodes that already have the
-  {{< glossary_tooltip text="container images" term_id="image" >}} for that
-  Pod cached locally.
-
-- `ServiceSpreadingPriority`: For a given Service, this policy aims to make sure that
-  the Pods for the Service run on different nodes. It favours scheduling onto nodes
-  that don't have Pods for the service already assigned there. The overall outcome is
-  that the Service becomes more resilient to a single Node failure.
-
-- `EqualPriority`: Gives an equal weight of one to all nodes.
-
-- `EvenPodsSpreadPriority`: Implements preferred
-  [pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/).
+This scheduling policy is not supported since Kubernetes v1.23. Associated flags `policy-config-file`, `policy-configmap`, `policy-configmap-namespace` and `use-legacy-policy-config` are also not supported. Instead, use the [Scheduler Configuration](/docs/reference/scheduling/config/) to achieve similar behavior.
 
 ## {{% heading "whatsnext" %}}
 
@@ -106,4 +17,3 @@ The following *priorities* implement scoring:
 * Learn about [kube-scheduler Configuration](/docs/reference/scheduling/config/)
 * Read the [kube-scheduler configuration reference (v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2)
 * Read the [kube-scheduler Policy reference (v1)](/docs/reference/config-api/kube-scheduler-policy-config.v1/)
-

From 280229b0ec15a362411694dc3ba1b96dd8380cf4 Mon Sep 17 00:00:00 2001
From: Humble Chirammal <hchiramm@redhat.com>
Date: Wed, 17 Nov 2021 23:35:44 +0530
Subject: [PATCH 35/68] Add RBD CSI migration section to the storage volumes
 guide

Kubernetes adds the RBD CSI migration functionality via CSI
migration translation lib.

Ref# kubernetes/kubernetes#95361

This commit add the migration details to volumes.md and
feature-gates.md

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
---
 content/en/docs/concepts/storage/volumes.md   | 42 ++++++++++++++++---
 .../feature-gates.md                          |  8 ++++
 2 files changed, 45 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 56694dee66c32..f0d005722f636 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -956,11 +956,11 @@ GitHub project has [instructions](https://github.com/quobyte/quobyte-csi#quobyte
 ### rbd
 
 An `rbd` volume allows a
-[Rados Block Device](https://docs.ceph.com/en/latest/rbd/) (RBD) volume to mount into your
-Pod. Unlike `emptyDir`, which is erased when a pod is removed, the contents of
-an `rbd` volume are preserved and the volume is unmounted. This
-means that a RBD volume can be pre-populated with data, and that data can
-be shared between pods.
+[Rados Block Device](https://docs.ceph.com/en/latest/rbd/) (RBD) volume to mount
+into your Pod. Unlike `emptyDir`, which is erased when a pod is removed, the
+contents of an `rbd` volume are preserved and the volume is unmounted. This
+means that a RBD volume can be pre-populated with data, and that data can be
+shared between pods.
 
 {{< note >}}
 You must have a Ceph installation running before you can use RBD.
@@ -975,6 +975,38 @@ Simultaneous writers are not allowed.
 See the [RBD example](https://github.com/kubernetes/examples/tree/master/volumes/rbd)
 for more details.
 
+#### RBD CSI migration {#rbd-csi-migration}
+
+{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+
+The `CSIMigration` feature for `RBD`, when enabled, redirects all plugin
+operations from the existing in-tree plugin to the `rbd.csi.ceph.com` {{<
+glossary_tooltip text="CSI" term_id="csi" >}} driver. In order to use this
+feature, the
+[Ceph CSI driver](https://github.com/ceph/ceph-csi)
+must be installed on the cluster and the `CSIMigration` and `CSIMigrationRBD`
+[feature gates](/docs/reference/command-line-tools-reference/feature-gates/)
+must be enabled.
+
+{{< note >}}
+
+As a Kubernetes cluster operator that administers storage, here are the
+prerequisites that you must complete before you attempt migration to the
+RBD CSI driver:
+
+* You must install the Ceph CSI driver (`rbd.csi.ceph.com`), v3.5.0 or above,
+  into your Kubernetes cluster.
+* considering the `clusterID` field is a required parameter for CSI driver for
+  its operations, but in-tree StorageClass has `monitors` field as a required
+  parameter, a Kubernetes storage admin has to create a clusterID based on the
+  monitors hash ( ex:`#echo -n
+  '<monitors_string>' | md5sum`) in the CSI config map and keep the monitors
+  under this clusterID configuration.
+* Also, if the value of `adminId` in the in-tree Storageclass is different from
+ `admin`, the `adminSecretName` mentioned in the in-tree Storageclass has to be
+  patched with the base64 value of the `adminId` parameter value, otherwise this
+  step can be skipped. {{< /note >}}
+
 ### secret
 
 A `secret` volume is used to pass sensitive information, such as passwords, to
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..e9befb359c924 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -81,6 +81,7 @@ different Kubernetes components.
 | `CSIMigrationOpenStack` | `false` | Alpha | 1.14 | 1.17 |
 | `CSIMigrationOpenStack` | `true` | Beta | 1.18 | |
 | `CSIMigrationvSphere` | `false` | Beta | 1.19 | |
+| `CSIMigrationRBD` | `false` | Alpha | 1.23 | |
 | `CSIStorageCapacity` | `false` | Alpha | 1.19 | 1.20 |
 | `CSIStorageCapacity` | `true` | Beta | 1.21 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
@@ -622,6 +623,13 @@ Each feature gate is designed for enabling/disabling a specific feature:
   operations from the GCE-PD in-tree plugin to PD CSI plugin. Supports falling
   back to in-tree GCE plugin if a node does not have PD CSI plugin installed and
   configured. Requires CSIMigration feature flag enabled.
+- `CSIMigrationRBD`: Enables shims and translation logic to route volume
+  operations from the RBD in-tree plugin to Ceph RBD CSI plugin. Requires
+  CSIMigration and CSIMigrationRBD feature flags enabled and Ceph CSI plugin
+  installed and configured in the cluster. This flag has been deprecated in
+  favor of the
+  `InTreePluginRBDUnregister` feature flag which prevents the registration of
+  in-tree RBD plugin.
 - `CSIMigrationGCEComplete`: Stops registering the GCE-PD in-tree plugin in
   kubelet and volume controllers and enables shims and translation logic to
   route volume operations from the GCE-PD in-tree plugin to PD CSI plugin.

From b8a9baeb89fde4b9670cf8c3c664afc9f5cf6fbd Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sun, 28 Nov 2021 19:05:16 +0000
Subject: [PATCH 36/68] De-emphasize scheduling priorities

Scheduling priorities are deprecated, so:
- move the page later in the parent topic
- hint that it's not a priority in the sitemap for the live docs
---
 content/en/docs/reference/scheduling/policies.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/scheduling/policies.md b/content/en/docs/reference/scheduling/policies.md
index d9a6d92cfe89a..3e2e554fc9686 100644
--- a/content/en/docs/reference/scheduling/policies.md
+++ b/content/en/docs/reference/scheduling/policies.md
@@ -1,7 +1,8 @@
 ---
 title: Scheduling Policies
 content_type: concept
-weight: 10
+sitemap:
+  priority: 0.2 # Scheduling priorities are deprecated
 ---
 
 <!-- overview -->

From 9ea79fa719f12510178898af5835ad46485ae3fe Mon Sep 17 00:00:00 2001
From: ravisantoshgudimetla <ravisantoshgudimetla@gmail.com>
Date: Mon, 29 Nov 2021 09:06:51 -0500
Subject: [PATCH 37/68] [docs]: Update existing fields in STS spec

---
 .../concepts/workloads/controllers/statefulset.md    | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index 4f12bb179608a..5197fe4f20d25 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -113,6 +113,14 @@ In the above example:
 The name of a StatefulSet object must be a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 
+### Pod Selector
+
+You must set the `.spec.selector` field of a StatefulSet to match the labels of its `.spec.template.metadata.labels`. In 1.8 and later versions, failing to specify a matching Pod Selector will result in a validation error during StatefulSet creation.
+
+### Volume Claim Templates
+
+You can set the  `.spec.volumeClaimTemplates` which can provide stable storage using [PersistentVolumes](/docs/concepts/storage/persistent-volumes/) provisioned by a PersistentVolume Provisioner.
+
 
 ### Minimum ready seconds
 
@@ -124,10 +132,6 @@ Please note that this feature is beta and enabled by default. Please opt out by
 want this feature to be enabled. This field defaults to 0 (the Pod will be considered 
 available as soon as it is ready). To learn more about when a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
 
-## Pod Selector
-
-You must set the `.spec.selector` field of a StatefulSet to match the labels of its `.spec.template.metadata.labels`. Prior to Kubernetes 1.8, the `.spec.selector` field was defaulted when omitted. In 1.8 and later versions, failing to specify a matching Pod Selector will result in a validation error during StatefulSet creation.
-
 ## Pod Identity
 
 StatefulSet Pods have a unique identity that is comprised of an ordinal, a

From e6a9fd269e762c4b1ca638b207cfb7704ad37d60 Mon Sep 17 00:00:00 2001
From: Jordan Liggitt <liggitt@google.com>
Date: Mon, 29 Nov 2021 09:46:22 -0500
Subject: [PATCH 38/68] Update webhook anchor

---
 content/en/docs/concepts/security/pod-security-admission.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/security/pod-security-admission.md b/content/en/docs/concepts/security/pod-security-admission.md
index 933dc62940876..5969d2bb5d7ed 100644
--- a/content/en/docs/concepts/security/pod-security-admission.md
+++ b/content/en/docs/concepts/security/pod-security-admission.md
@@ -44,7 +44,7 @@ is an Alpha feature and must be enabled in `kube-apiserver` in order to use the
 --feature-gates="...,PodSecurity=true"
 ```
 
-## Alternative: installing the `PodSecurity` admission webhook
+## Alternative: installing the `PodSecurity` admission webhook {#webhook}
 
 For environments where the built-in `PodSecurity` admission plugin cannot be used,
 either because the cluster is older than v1.22, or the `PodSecurity` feature cannot be enabled,

From a9641b6ccd33f8899eb628326324d97f3dfd2951 Mon Sep 17 00:00:00 2001
From: Joe Betz <jpbetz@google.com>
Date: Mon, 15 Nov 2021 15:44:54 -0500
Subject: [PATCH 39/68] Add stub for validatiton rule documentation

---
 .../custom-resource-definitions.md            | 83 ++++++++++++++++++-
 1 file changed, 81 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
index cd2d0fb1038e6..538bc608211ad 100644
--- a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
+++ b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
@@ -556,8 +556,9 @@ deleted by Kubernetes.
 ### Validation
 
 Custom resources are validated via
-[OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject)
-and you can add additional validation using
+[OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject),
+by x-kubernetes-validation-rules when the [Validation Rules feature](#validation-rules) is enabled, and you
+can add additional validation using
 [admission webhooks](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook).
 
 Additionally, the following restrictions are applied to the schema:
@@ -577,6 +578,11 @@ Additionally, the following restrictions are applied to the schema:
 - The field `additionalProperties` cannot be set to `false`.
 - The field `additionalProperties` is mutually exclusive with `properties`.
 
+The `x-kubernetes-validation-rules` extension can be use to validate custom resources using [Common
+Expression Language (CEL)](https://github.com/google/cel-spec) expressions when the [Validation
+Rules feature](#validation-rules) feature is enabled and the CustomResourceDefinition schema is a
+[structural schema](#specifying-a-structural-schema).
+
 The `default` field can be set when the [Defaulting feature](#defaulting) is enabled,
 which is the case with `apiextensions.k8s.io/v1` CustomResourceDefinitions.
 Defaulting is in GA since 1.17 (beta since 1.16 with the `CustomResourceDefaulting`
@@ -693,6 +699,79 @@ kubectl apply -f my-crontab.yaml
 crontab "my-new-cron-object" created
 ```
 
+## Validation rules
+
+{{< feature-state state="alpha" for_k8s_version="v1.23" >}}
+
+Validation rules are in alpha since 1.23 and validate custom resources when the
+`CustomResourceValidationExpressions` [feature
+gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled and the schema is a
+[structural schema](#specifying-a-structural-schema).
+
+Validation rules use the [Common Expression Language (CEL)](https://github.com/google/cel-spec)
+expression language to validate custom resource values. Validation rules are included in
+CustomResourceDefinition schemas using the `x-kubernetes-validation-rules` extension.
+
+For example:
+
+```yaml
+    ...
+    openAPIV3Schema:
+      type: object
+      properties:
+        spec:
+          type: object
+            x-kubernetes-validation-rules:
+              - rule: "self.minReplicas <= self.replicas"
+              - rule: "self.replicas <= self.maxReplicas"
+          properties:
+            ...
+            minReplicas:
+              type: integer
+            replicas:
+              type: integer
+            maxReplicas:
+              type: integer
+```
+
+will reject an request to create this custom resource:
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  minReplicas: 0
+  replicas: 20
+  maxReplicas: 10
+```
+
+with the response:
+
+```
+The CronTab "my-new-cron-object" is invalid:
+* spec: Invalid value: map[string]interface {}{"minReplicas": 0, "replicas":20, "maxReplicas": 10}: failed rule: self.minReplicas <= self.replicas && self.replicas <= self.maxReplicas
+```
+
+TODO: (using text from types_jsonprops.go and KEP were applicable, but using "full" multi-line examples that include both the schema and the custom resource data)
+- Explain that rules are compiled when CRDs are created/updated. Show full example including compilation error output examples.
+- Explain scope, self, and how objects, maps and arrays are accessed. Show full examples.
+  - Must show: 'self.field' selection, has() field presence checking, 'self[key]' map access and
+    'key in self' map containment, 'self[i]' list access, all/exists/filter and how they apply to
+    maps and lists. Show more of the functions than covered in types_jsonprops.go. Provide links to
+    functions and macros in spec.  Provide link to strings extension library in cel-go that we have
+    enabled. Explain that this is an extension library.
+- Include examples table from KEP? Probably just past it in and add context.
+- Explain access to type and object meta.
+- Explain openapiv3 -> CEL declarations type mapping and include the table from the KEP. Link to OpenAPIv3 and CEL documentation about types.
+- Explain int-or-string, preserve-unknown, nullable, embedded. Provide some short examples.
+- Explain escaping using a table. Provide some short examples. Provide guidance on how to name
+  properties (both in this section of this document and elsewhere in this document where property
+  names are introduced/discussed).
+- Explain + and == for list maps and list sets (table? whatever looks better)
+- DO NOT: provide all the motivation and design rationale from the KEP.
+
 ### Defaulting
 
 {{< note >}}

From 9d69f673999a171a5660b0177792808c4e3ee6f1 Mon Sep 17 00:00:00 2001
From: cici37 <cicih@google.com>
Date: Thu, 18 Nov 2021 13:27:39 -0800
Subject: [PATCH 40/68] Add feature gate `CustomResourceValidationExpressions`
 into /command-line-tools-reference/feature-gates.md

---
 .../reference/command-line-tools-reference/feature-gates.md     | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index d369723ec889f..000fac1e82418 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -93,6 +93,7 @@ different Kubernetes components.
 | `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 |
 | `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | |
 | `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | |
+| `CustomResourceValidationExpressions` | `false` | Alpha | 1.23 | |
 | `DaemonSetUpdateSurge` | `false` | Alpha | 1.21 | 1.21 |
 | `DaemonSetUpdateSurge` | `true` | Beta | 1.22 | |
 | `DefaultPodTopologySpread` | `false` | Alpha | 1.19 | 1.19 |
@@ -684,6 +685,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
   version 1 of the same controller is selected.
 - `CustomCPUCFSQuotaPeriod`: Enable nodes to change `cpuCFSQuotaPeriod` in
   [kubelet config](/docs/tasks/administer-cluster/kubelet-config-file/).
+- `CustomResourceValidationExpressions`: Enable expression language validation in CRD which will validate customer resource based on validation rules written in `x-kubernetes-validations` extension.
 - `CustomPodDNS`: Enable customizing the DNS settings for a Pod using its `dnsConfig` property.
   Check [Pod's DNS Config](/docs/concepts/services-networking/dns-pod-service/#pods-dns-config)
   for more details.

From cd1726aa1091d53c7fe7f6f59c0469761b0986a1 Mon Sep 17 00:00:00 2001
From: cici37 <cicih@google.com>
Date: Wed, 17 Nov 2021 19:49:08 -0800
Subject: [PATCH 41/68] Adding details on CEL validation for CRD.

---
 .../custom-resource-definitions.md            | 284 ++++++++++++++++--
 1 file changed, 254 insertions(+), 30 deletions(-)

diff --git a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
index 538bc608211ad..e4c5e3991555a 100644
--- a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
+++ b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
@@ -557,7 +557,7 @@ deleted by Kubernetes.
 
 Custom resources are validated via
 [OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject),
-by x-kubernetes-validation-rules when the [Validation Rules feature](#validation-rules) is enabled, and you
+by x-kubernetes-validations when the [Validation Rules feature](#validation-rules) is enabled, and you
 can add additional validation using
 [admission webhooks](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook).
 
@@ -578,9 +578,9 @@ Additionally, the following restrictions are applied to the schema:
 - The field `additionalProperties` cannot be set to `false`.
 - The field `additionalProperties` is mutually exclusive with `properties`.
 
-The `x-kubernetes-validation-rules` extension can be use to validate custom resources using [Common
+The `x-kubernetes-validations` extension can be used to validate custom resources using [Common
 Expression Language (CEL)](https://github.com/google/cel-spec) expressions when the [Validation
-Rules feature](#validation-rules) feature is enabled and the CustomResourceDefinition schema is a
+rules](#validation-rules) feature is enabled and the CustomResourceDefinition schema is a
 [structural schema](#specifying-a-structural-schema).
 
 The `default` field can be set when the [Defaulting feature](#defaulting) is enabled,
@@ -705,12 +705,16 @@ crontab "my-new-cron-object" created
 
 Validation rules are in alpha since 1.23 and validate custom resources when the
 `CustomResourceValidationExpressions` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled and the schema is a
+gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled.
+This feature is only available if the schema is a
 [structural schema](#specifying-a-structural-schema).
 
 Validation rules use the [Common Expression Language (CEL)](https://github.com/google/cel-spec)
-expression language to validate custom resource values. Validation rules are included in
-CustomResourceDefinition schemas using the `x-kubernetes-validation-rules` extension.
+to validate custom resource values. Validation rules are included in
+CustomResourceDefinition schemas using the `x-kubernetes-validations` extension.
+
+The Rule is scoped to the location of the `x-kubernetes-validations` extension in the schema.
+And `self` variable in the CEL expression is bound to the scoped value.
 
 For example:
 
@@ -721,9 +725,11 @@ For example:
       properties:
         spec:
           type: object
-            x-kubernetes-validation-rules:
-              - rule: "self.minReplicas <= self.replicas"
-              - rule: "self.replicas <= self.maxReplicas"
+          x-kubernetes-validation-rules:
+            - rule: "self.minReplicas <= self.replicas"
+              message: "replicas should be greater than or equal to minReplicas."
+            - rule: "self.replicas <= self.maxReplicas"
+              message: "replicas should be smaller than or equal to maxReplicas."
           properties:
             ...
             minReplicas:
@@ -732,9 +738,13 @@ For example:
               type: integer
             maxReplicas:
               type: integer
+          required:
+            - minReplicas
+            - replicas
+            - maxReplicas 
 ```
 
-will reject an request to create this custom resource:
+will reject a request to create this custom resource:
 
 ```yaml
 apiVersion: "stable.example.com/v1"
@@ -751,26 +761,240 @@ with the response:
 
 ```
 The CronTab "my-new-cron-object" is invalid:
-* spec: Invalid value: map[string]interface {}{"minReplicas": 0, "replicas":20, "maxReplicas": 10}: failed rule: self.minReplicas <= self.replicas && self.replicas <= self.maxReplicas
-```
-
-TODO: (using text from types_jsonprops.go and KEP were applicable, but using "full" multi-line examples that include both the schema and the custom resource data)
-- Explain that rules are compiled when CRDs are created/updated. Show full example including compilation error output examples.
-- Explain scope, self, and how objects, maps and arrays are accessed. Show full examples.
-  - Must show: 'self.field' selection, has() field presence checking, 'self[key]' map access and
-    'key in self' map containment, 'self[i]' list access, all/exists/filter and how they apply to
-    maps and lists. Show more of the functions than covered in types_jsonprops.go. Provide links to
-    functions and macros in spec.  Provide link to strings extension library in cel-go that we have
-    enabled. Explain that this is an extension library.
-- Include examples table from KEP? Probably just past it in and add context.
-- Explain access to type and object meta.
-- Explain openapiv3 -> CEL declarations type mapping and include the table from the KEP. Link to OpenAPIv3 and CEL documentation about types.
-- Explain int-or-string, preserve-unknown, nullable, embedded. Provide some short examples.
-- Explain escaping using a table. Provide some short examples. Provide guidance on how to name
-  properties (both in this section of this document and elsewhere in this document where property
-  names are introduced/discussed).
-- Explain + and == for list maps and list sets (table? whatever looks better)
-- DO NOT: provide all the motivation and design rationale from the KEP.
+* spec: Invalid value: map[string]interface {}{"maxReplicas":10, "minReplicas":0, "replicas":20}: replicas should be smaller than or equal to maxReplicas.
+```
+
+`x-kubernetes-validations` could have multiple rules. 
+
+The `rule` under `x-kubernetes-validations` represents the expression which will be evaluated by CEL.
+
+The `message` represents the message displayed when validation fails. If message is unset, the above response would be:
+```
+The CronTab "my-new-cron-object" is invalid:
+* spec: Invalid value: map[string]interface {}{"maxReplicas":10, "minReplicas":0, "replicas":20}: failed rule: self.replicas <= self.maxReplicas
+```
+
+Validation rules are compiled when CRDs are created/updated. 
+The request of CRDs create/update will fail if compilation of validation rules fail. 
+Compilation process includes type checking as well.
+
+The compilation failure:
+- `no_matching_overload`: this function has no overload for the types of the arguments.
+ 
+   e.g. Rule like `self == true` against a field of integer type will get error:
+  ```
+  Invalid value: apiextensions.ValidationRule{Rule:"self == true", Message:""}: compilation failed: ERROR: \<input>:1:6: found no matching overload for '_==_' applied to '(int, bool)'
+  ```
+  
+- `no_such_field`: does not contain the desired field.
+  
+   e.g. Rule like `self.nonExistingField > 0` against a non-existing field will return the error:
+  ```
+  Invalid value: apiextensions.ValidationRule{Rule:"self.nonExistingField > 0", Message:""}: compilation failed: ERROR: \<input>:1:5: undefined field 'nonExistingField'
+  ```
+
+- `invalid argument`: invalid argument to macros.
+ 
+  e.g. Rule like `has(self)` will return error:
+  ```
+  Invalid value: apiextensions.ValidationRule{Rule:"has(self)", Message:""}: compilation failed: ERROR: <input>:1:4: invalid argument to has() macro
+  ```
+
+
+Validation Rules Examples:
+
+| Rule                                                                             | Purpose                                                                           |
+| ----------------                                                                 | ------------                                                                      |
+| `self.minReplicas <= self.replicas && self.replicas <= self.maxReplicas`         | Validate that the three fields defining replicas are ordered appropriately        |
+| `'Available' in self.stateCounts`                                                | Validate that an entry with the 'Available' key exists in a map                   |
+| `(size(self.list1) == 0) != (size(self.list2) == 0)`                             | Validate that one of two lists is non-empty, but not both                         |
+| <code>!('MY_KEY' in self.map1) &#124;&#124; self['MY_KEY'].matches('^[a-zA-Z]*$')</code>               | Validate the value of a map for a specific key, if it is in the map               |
+| `self.envars.filter(e, e.name = 'MY_ENV').all(e, e.value.matches('^[a-zA-Z]*$')` | Validate the 'value' field of a listMap entry where key field 'name' is 'MY_ENV'  |
+| `has(self.expired) && self.created + self.ttl < self.expired`                    | Validate that 'expired' date is after a 'create' date plus a 'ttl' duration       |
+| `self.health.startsWith('ok')`                                                   | Validate a 'health' string field has the prefix 'ok'                              |
+| `self.widgets.exists(w, w.key == 'x' && w.foo < 10)`                             | Validate that the 'foo' property of a listMap item with a key 'x' is less than 10 |
+| `type(self) == string ? self == '100%' : self == 1000`                           | Validate an int-or-string field for both the the int and string cases             |
+| `self.metadata.name.startsWith(self.prefix)`                                     | Validate that an object's name has the prefix of another field value              |
+| `self.set1.all(e, !(e in self.set2))`                                            | Validate that two listSets are disjoint                                           |
+| `size(self.names) == size(self.details) && self.names.all(n, n in self.details)` | Validate the 'details' map is keyed by the items in the 'names' listSet           |
+
+Xref: [Supported evaluation on CEL](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#evaluation)
+
+
+- If the Rule is scoped to the root of a resource, it may make field selection into any fields
+  declared in the OpenAPIv3 schema of the CRD as well as `apiVersion`, `kind`, `metadata.name` and
+  `metadata.generateName`. This includes selection of fields in both the `spec` and `status` in the
+  same expression:
+  ```yaml
+      ...
+      openAPIV3Schema:
+        type: object
+        x-kubernetes-validation-rules:
+          - rule: "self.status.availableReplicas >= self.spec.minReplicas"
+        properties:
+            spec:
+              type: object
+              properties:
+                minReplicas:
+                  type: integer
+                ...
+            status:
+              type: object
+              properties:
+                availableReplicas:
+                  type: integer
+  ```
+
+- If the Rule is scoped to an object with properties, the accessible properties of the object are field selectable
+  via `self.field` and field presence can be checked via `has(self.field)`. Null valued fields are treated as
+  absent fields in CEL expressions.
+
+  ```yaml
+      ...
+      openAPIV3Schema:
+        type: object
+        properties:
+          spec:
+            type: object
+            x-kubernetes-validation-rules:
+              - rule: "has(self.foo)"
+            properties:
+              ...
+              foo:
+                type: integer
+  ```
+
+- If the Rule is scoped to an object with additionalProperties (i.e. a map) the value of the map
+  are accessible via `self[mapKey]`, map containment can be checked via `mapKey in self` and all entries of the map
+  are accessible via CEL macros and functions such as `self.all(...)`.
+  ```yaml
+      ...
+      openAPIV3Schema:
+        type: object
+        properties:
+          spec:
+            type: object
+            x-kubernetes-validation-rules:
+              - rule: "self['xyz'].foo > 0"
+            additionalProperties:
+              ...
+              type: object
+              properties:
+                foo:
+                  type: integer
+  ```
+
+- If the Rule is scoped to an array, the elements of the array are accessible via `self[i]` and also by macros and
+  functions.
+  ```yaml
+      ...
+      openAPIV3Schema:
+        type: object
+        properties:
+          ...
+          foo:
+            type: array
+            x-kubernetes-validation-rules:
+              - rule: "size(self) == 1"
+            items:
+              type: string
+  ```
+
+- If the Rule is scoped to a scalar, `self` is bound to the scalar value.
+  ```yaml
+      ...
+      openAPIV3Schema:
+        type: object
+        properties:
+          spec:
+            type: object
+            properties:
+              ...
+              foo:
+                type: integer
+                x-kubernetes-validation-rules:
+                - rule: "self > 0"
+  ```
+Examples:
+
+|type of the field rule scoped to    | Rule example             |
+| -----------------------| -----------------------|
+| root object            | `self.status.actual <= self.spec.maxDesired`|
+| map of objects         | `self.components['Widget'].priority < 10`|
+| list of integers       | `self.values.all(value, value >= 0 && value < 100)`|
+| string                 | `self.startsWith('kube')`|
+
+
+The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the 
+object and from any x-kubernetes-embedded-resource annotated objects. No other metadata properties are accessible.
+	
+Unknown data preserved in custom resources via `x-kubernetes-preserve-unknown-fields` is not accessible in CEL
+  expressions. This includes:
+  - Unknown field values that are preserved by object schemas with x-kubernetes-preserve-unknown-fields.
+  - Object properties where the property schema is of an "unknown type". An "unknown type" is recursively defined as:
+    - A schema with no type and x-kubernetes-preserve-unknown-fields set to true
+    - An array where the items schema is of an "unknown type"
+    - An object where the additionalProperties schema is of an "unknown type"
+
+
+Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible.
+Accessible property names are escaped according to the following rules when accessed in the expression:
+
+| escape sequence         | property name equivalent  |
+| ----------------------- | -----------------------|
+| `__underscores__`       | `__`                  |
+| `__dot__`               | `.`                   |
+|`__dash__`               | `-`                   |
+| `__slash__`             | `/`                   |
+| `__{keyword}__`         | [CEL RESERVED keyword](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#syntax)       |
+
+Note: CEL RESERVED keyword needs to match the exact property name to be escaped (e.g. int in the word sprint would not be escaped).
+
+Examples on escaping:
+
+|property name    | rule with escaped property name     |
+| ----------------| -----------------------             |
+| namespace       | `self.__namespace__ > 0`            |
+| x-prop          | `self.x__dash__prop > 0`            |
+| redact__d       | `self.redact__underscores__d > 0`   |
+| string          | `self.startsWith('kube')`           |
+
+  
+Equality on arrays with `x-kubernetes-list-type` of `set` or `map` ignores element order, i.e. [1, 2] == [2, 1].
+Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type:
+ - `set`: `X + Y` performs a union where the array positions of all elements in `X` are preserved and
+      non-intersecting elements in `Y` are appended, retaining their partial order.
+ - `map`: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values
+   are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with
+   non-intersecting keys are appended, retaining their partial order.
+ 
+
+Here is the declarations type mapping between OpenAPIv3 and CEL type:
+
+| OpenAPIv3 type                                     | CEL type                                                                                                                     |
+| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| 'object' with Properties                           | object / "message type"                                                                                                      |
+| 'object' with AdditionalProperties                 | map                                                                                                                          |
+| 'object' with x-kubernetes-embedded-type           | object / "message type", 'apiVersion', 'kind', 'metadata.name' and 'metadata.generateName' are implicitly included in schema |
+| 'object' with x-kubernetes-preserve-unknown-fields | object / "message type", unknown fields are NOT accessible in CEL expression                                                 |
+| x-kubernetes-int-or-string                         | dynamic object that is either an int or a string, `type(value)` can be used to check the type                                |
+| 'array                                             | list                                                                                                                         |
+| 'array' with x-kubernetes-list-type=map            | list with map based Equality & unique key guarantees                                                                         |
+| 'array' with x-kubernetes-list-type=set            | list with set based Equality & unique entry guarantees                                                                       |
+| 'boolean'                                          | boolean                                                                                                                      |
+| 'number' (all formats)                             | double                                                                                                                       |
+| 'integer' (all formats)                            | int (64)                                                                                                                     |
+| 'null'                                             | null_type                                                                                                                    |
+| 'string'                                           | string                                                                                                                       |
+| 'string' with format=byte (base64 encoded)         | bytes                                                                                                                        |
+| 'string' with format=date                          | timestamp (google.protobuf.Timestamp)                                                                                        |
+| 'string' with format=datetime                      | timestamp (google.protobuf.Timestamp)                                                                                        |
+| 'string' with format=duration                      | duration (google.protobuf.Duration)                                                                                          |
+
+xref: [CEL types](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#values), [OpenAPI
+types](https://swagger.io/specification/#data-types), [Kubernetes Structural Schemas](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema).
+
+
 
 ### Defaulting
 

From 02f63b966140f1d8ba37a17679351190049dd65d Mon Sep 17 00:00:00 2001
From: Oksana Naumov <trierra.dev@gmail.com>
Date: Thu, 11 Nov 2021 12:01:08 -0800
Subject: [PATCH 42/68] CSI migration of Portworx is in alpha

---
 content/en/docs/concepts/storage/volumes.md            | 10 ++++++++++
 .../command-line-tools-reference/feature-gates.md      |  4 ++++
 2 files changed, 14 insertions(+)

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index eb15504cde5ae..792ceae69bd34 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -1050,6 +1050,16 @@ but new volumes created by the vSphere CSI driver will not be honoring these par
 
 To turn off the `vsphereVolume` plugin from being loaded by the controller manager and the kubelet, you need to set `InTreePluginvSphereUnregister` feature flag to `true`. You must install a `csi.vsphere.vmware.com` {{< glossary_tooltip text="CSI" term_id="csi" >}} driver on all worker nodes.
 
+#### Portworx CSI migration
+{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+
+The `CSIMigration` feature for Portworx has been added but disabled by default in Kubernetes 1.23 since it's in alpha state.
+It redirects all plugin operations from the existing in-tree plugin to the
+`pxd.portworx.com` Container Storage Interface (CSI) Driver.
+[Portworx CSI Driver](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/csi/)
+must be installed on the cluster.
+To enable the feature, set `CSIMigrationPortworx=true` in kube-controller-manager and kubelet.
+
 ## Using subPath {#using-subpath}
 
 Sometimes, it is useful to share one volume for multiple uses in a single pod.
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index ef806fdb6ac87..55b4316b08d4f 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -84,6 +84,7 @@ different Kubernetes components.
 | `CSIMigrationOpenStack` | `false` | Alpha | 1.14 | 1.17 |
 | `CSIMigrationOpenStack` | `true` | Beta | 1.18 | |
 | `CSIMigrationvSphere` | `false` | Beta | 1.19 | |
+| `CSIMigrationPortworx` | `false` | Alpha | 1.23 | |
 | `CSIMigrationRBD` | `false` | Alpha | 1.23 | |
 | `CSIStorageCapacity` | `false` | Alpha | 1.19 | 1.20 |
 | `CSIStorageCapacity` | `true` | Beta | 1.21 | |
@@ -664,6 +665,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
   CSIMigrationvSphere feature flags enabled and vSphere CSI plugin installed and
   configured on all nodes in the cluster. This flag has been deprecated in favor
   of the `InTreePluginvSphereUnregister` feature flag which prevents the registration of in-tree vsphere plugin.
+- `CSIMigrationPortworx`: Enables shims and translation logic to route volume operations
+  from the Portworx in-tree plugin to Portworx CSI plugin.
+  Requires Portworx CSI driver to be installed and configured in the cluster, and feature gate set `CSIMigrationPortworx=true` in kube-controller-manager and kubelet configs.
 - `CSINodeInfo`: Enable all logic related to the CSINodeInfo API object in csi.storage.k8s.io.
 - `CSIPersistentVolume`: Enable discovering and mounting volumes provisioned through a
   [CSI (Container Storage Interface)](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md)

From 2ebfcfea1a96f6dec581caaa6affc534eb5c0bd8 Mon Sep 17 00:00:00 2001
From: Hemant Kumar <hekumar@redhat.com>
Date: Thu, 18 Nov 2021 12:14:44 -0500
Subject: [PATCH 43/68] Update docs for ConfigurableFSGroupPolicy

---
 .../reference/command-line-tools-reference/feature-gates.md     | 1 +
 .../en/docs/tasks/configure-pod-container/security-context.md   | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..9926e67e59cf5 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -222,6 +222,7 @@ different Kubernetes components.
 | `BoundServiceAccountTokenVolume` | `false` | Alpha | 1.13 | 1.20 |
 | `BoundServiceAccountTokenVolume` | `true` | Beta | 1.21 | 1.21 |
 | `BoundServiceAccountTokenVolume` | `true` | GA | 1.22 | - |
+| `ConfigurableFSGroupPolicy` | `true` | GA | 1.23 | |
 | `CRIContainerLogRotation` | `false` | Alpha | 1.10 | 1.10 |
 | `CRIContainerLogRotation` | `true` | Beta | 1.11 | 1.20 |
 | `CRIContainerLogRotation` | `true` | GA | 1.21 | - |
diff --git a/content/en/docs/tasks/configure-pod-container/security-context.md b/content/en/docs/tasks/configure-pod-container/security-context.md
index 56bcc0f3f9211..ef78e39b6a74a 100644
--- a/content/en/docs/tasks/configure-pod-container/security-context.md
+++ b/content/en/docs/tasks/configure-pod-container/security-context.md
@@ -149,7 +149,7 @@ exit
 
 ## Configure volume permission and ownership change policy for Pods
 
-{{< feature-state for_k8s_version="v1.20" state="beta" >}}
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
 By default, Kubernetes recursively changes ownership and permissions for the contents of each
 volume to match the `fsGroup` specified in a Pod's `securityContext` when that volume is

From 37532e231acc1d89a1e39de25a2684d655637efb Mon Sep 17 00:00:00 2001
From: Hemant Kumar <hekumar@redhat.com>
Date: Thu, 18 Nov 2021 12:11:21 -0500
Subject: [PATCH 44/68] Add docs for RecoverVolumeExpansionFailure feature

---
 .../concepts/storage/persistent-volumes.md    | 29 +++++++++++++++++++
 .../admission-controllers.md                  |  3 +-
 .../feature-gates.md                          |  3 ++
 3 files changed, 34 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index f2093073df54a..7fae64251fc37 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -299,6 +299,11 @@ Expanding EBS volumes is a time-consuming operation. Also, there is a per-volume
 
 #### Recovering from Failure when Expanding Volumes
 
+If a user specifies a new size that is too big to be satisfied by underlying storage system, expansion of PVC will be continuously retried until user or cluster administrator takes some action. This can be undesirable and hence Kubernetes provides following methods of recovering from such failures.
+
+{{< tabs name="recovery_methods" >}}
+{{% tab name="Manually with Cluster Administrator access" %}}
+
 If expanding underlying storage fails, the cluster administrator can manually recover the Persistent Volume Claim (PVC) state and cancel the resize requests. Otherwise, the resize requests are continuously retried by the controller without administrator intervention.
 
 1. Mark the PersistentVolume(PV) that is bound to the PersistentVolumeClaim(PVC) with `Retain` reclaim policy.
@@ -307,6 +312,30 @@ If expanding underlying storage fails, the cluster administrator can manually re
 4. Re-create the PVC with smaller size than PV and set `volumeName` field of the PVC to the name of the PV. This should bind new PVC to existing PV.
 5. Don't forget to restore the reclaim policy of the PV.
 
+{{% /tab %}}
+{{% tab name="By requesting expansion to smaller size" %}}
+{{% feature-state for_k8s_version="v1.23" state="alpha" %}}
+
+{{< note >}}
+Recovery from failing PVC expansion by users is available as an alpha feature since Kubernetes 1.23. The `RecoverVolumeExpansionFailure` feature must be enabled for this feature to work. Refer to the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) documentation for more information.
+{{< /note >}}
+
+If the feature gates `ExpandPersistentVolumes` and `RecoverVolumeExpansionFailure` are both
+enabled in your cluster, and expansion has failed for a PVC, you can retry expansion with a
+smaller size than the previously requested value. To request a new expansion attempt with a
+smaller proposed size, edit `.spec.resources` for that PVC and choose a value that is less than the
+value you previously tried.
+This is useful if expansion to a higher value did not succeed because of capacity constraint.
+If that has happened, or you suspect that it might have, you can retry expansion by specifying a
+size that is within the capacity limits of underlying storage provider. You can monitor status of resize operation by watching `.status.resizeStatus` and events on the PVC.
+
+Note that,
+although you can a specify a lower amount of storage than what was requested previously,
+the new value must still be higher than `.status.capacity`.
+Kubernetes does not support shrinking a PVC to less than its current size.
+{{% /tab %}}
+{{% /tabs %}}
+
 
 ## Types of Persistent Volumes
 
diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md
index 7957ff7a4fcfa..5e5d143ccff92 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -583,7 +583,8 @@ subresource of the referenced *owner* can change it.
 This admission controller implements additional validations for checking incoming `PersistentVolumeClaim` resize requests.
 
 {{< note >}}
-Support for volume resizing is available as an alpha feature. Admins must set the feature gate `ExpandPersistentVolumes`
+Support for volume resizing is available as a beta feature. As a cluster administrator,
+you must ensure that the feature gate `ExpandPersistentVolumes` is set
 to `true` to enable resizing.
 {{< /note >}}
 
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 63eba752de109..05e55ab486146 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -165,6 +165,7 @@ different Kubernetes components.
 | `ProxyTerminatingEndpoints` | `false` | Alpha | 1.22 | |
 | `QOSReserved` | `false` | Alpha | 1.11 | |
 | `ReadWriteOncePod` | `false` | Alpha | 1.22 | |
+| `RecoverVolumeExpansionFailure` | `false` | Alpha | 1.23 | |
 | `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 |
 | `RemainingItemCount` | `true` | Beta | 1.16 | |
 | `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 |
@@ -889,6 +890,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
   (memory only for now).
 - `ReadWriteOncePod`: Enables the usage of `ReadWriteOncePod` PersistentVolume
   access mode.
+- `RecoverVolumeExpansionFailure`: Enables users to edit their PVCs to smaller sizes so as they can recover from previously issued
+  volume expansion failures. See [enhancement proposal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1790-recover-resize-failure/README.md) for more details.
 - `RemainingItemCount`: Allow the API servers to show a count of remaining
   items in the response to a
   [chunking list request](/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks).

From 014f73f326689c433b34660be914913e67306556 Mon Sep 17 00:00:00 2001
From: Bridget Kromhout <bridget@kromhout.org>
Date: Mon, 29 Nov 2021 15:41:43 -0600
Subject: [PATCH 45/68] Clarifications for dual-stack going GA in 1.23.

Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
---
 .../tools/kubeadm/dual-stack-support.md                       | 2 +-
 .../windows/intro-windows-in-kubernetes.md                    | 4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md b/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
index f2d250c296fba..ffd5839c23e44 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
@@ -71,7 +71,7 @@ Run kubeadm to initiate the dual-stack control plane node:
 kubeadm init --config=kubeadm-config.yaml
 ```
 
-Currently, the kube-controller-manager flags `--node-cidr-mask-size-ipv4|--node-cidr-mask-size-ipv6` are being left with default values. See [enable IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack#enable-ipv4ipv6-dual-stack).
+The kube-controller-manager flags `--node-cidr-mask-size-ipv4|--node-cidr-mask-size-ipv6` are set with default values. See [configure IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack#configure-ipv4-ipv6-dual-stack).
 
 {{< note >}}
 The `--apiserver-advertise-address` flag does not support dual-stack.
diff --git a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
index c2160e330fae0..68ea3ee146c4e 100644
--- a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
+++ b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
@@ -340,9 +340,7 @@ Kubernetes on Windows does not support single-stack "IPv6-only" networking. Howe
 dual-stack IPv4/IPv6 networking for pods and nodes with single-family services
 is supported.
 
-You can enable IPv4/IPv6 dual-stack networking for `l2bridge` networks using the
-`IPv6DualStack` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
-See [enable IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack#enable-ipv4ipv6-dual-stack) for more details.
+You can use IPv4/IPv6 dual-stack networking with `l2bridge` networks. See [configure IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack#configure-ipv4-ipv6-dual-stack) for more details.
 
 {{< note >}}
 Overlay (VXLAN) networks on Windows do not support dual-stack networking.

From 22475d9cf190c9cf641e192c0e8ad7cd0397012d Mon Sep 17 00:00:00 2001
From: Hemant Kumar <gnufied@users.noreply.github.com>
Date: Mon, 29 Nov 2021 21:29:57 -0500
Subject: [PATCH 46/68] Update
 content/en/docs/reference/command-line-tools-reference/feature-gates.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../reference/command-line-tools-reference/feature-gates.md   | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 05e55ab486146..ebed2123e5a0f 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -891,7 +891,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `ReadWriteOncePod`: Enables the usage of `ReadWriteOncePod` PersistentVolume
   access mode.
 - `RecoverVolumeExpansionFailure`: Enables users to edit their PVCs to smaller sizes so as they can recover from previously issued
-  volume expansion failures. See [enhancement proposal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1790-recover-resize-failure/README.md) for more details.
+  volume expansion failures. See
+  [Recovering from Failure when Expanding Volumes](/docs/concepts/storage/persistent-volumes/#recovering-from-failure-when-expanding-volumes)
+  for more details.
 - `RemainingItemCount`: Allow the API servers to show a count of remaining
   items in the response to a
   [chunking list request](/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks).

From 9bef88f0084e2d3c1e43741f70a916f88635c85d Mon Sep 17 00:00:00 2001
From: Ayushman Mishra <ayushvidushi01@gmail.com>
Date: Tue, 30 Nov 2021 09:18:11 +0530
Subject: [PATCH 47/68] Edited FlexVolume deprecated

Signed-off-by: Ayushman Mishra <ayushvidushi01@gmail.com>
---
 content/en/docs/concepts/extend-kubernetes/_index.md          | 4 +++-
 content/en/docs/concepts/storage/persistent-volumes.md        | 3 ++-
 content/en/docs/reference/glossary/flexvolume.md              | 4 ++--
 .../tools/kubeadm/troubleshooting-kubeadm.md                  | 1 +
 4 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/extend-kubernetes/_index.md b/content/en/docs/concepts/extend-kubernetes/_index.md
index 825484f50d9d9..edb550bbeda4b 100644
--- a/content/en/docs/concepts/extend-kubernetes/_index.md
+++ b/content/en/docs/concepts/extend-kubernetes/_index.md
@@ -77,7 +77,7 @@ failure.
 In the webhook model, Kubernetes makes a network request to a remote service.
 In the *Binary Plugin* model, Kubernetes executes a binary (program).
 Binary plugins are used by the kubelet (e.g.
-[Flex Volume Plugins](/docs/concepts/storage/volumes/#flexVolume)
+[Flex Volume Plugins](/docs/concepts/storage/volumes/#flexvolume)
 and [Network Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/))
 and by kubectl.
 
@@ -163,6 +163,8 @@ After a request is authorized, if it is a write operation, it also goes through
 ) allow users to mount volume types without built-in support by having the
 Kubelet call a Binary Plugin to mount the volume.
 
+FlexVolume is deprecated in v1.23. Out-of-tree CSI driver is the recommended way to write volume drivers in Kubernetes. See this doc [here](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md#kubernetes-volume-plugin-faq-for-storage-vendors) for more information.
+
 
 ### Device Plugins
 
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index f2093073df54a..8e8a6241ca867 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -318,7 +318,8 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
 * [`cephfs`](/docs/concepts/storage/volumes/#cephfs) - CephFS volume
 * [`csi`](/docs/concepts/storage/volumes/#csi) - Container Storage Interface (CSI)
 * [`fc`](/docs/concepts/storage/volumes/#fc) - Fibre Channel (FC) storage
-* [`flexVolume`](/docs/concepts/storage/volumes/#flexVolume) - FlexVolume
+* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume
+  (**deprecated** in v1.23)
 * [`gcePersistentDisk`](/docs/concepts/storage/volumes/#gcepersistentdisk) - GCE Persistent Disk
 * [`glusterfs`](/docs/concepts/storage/volumes/#glusterfs) - Glusterfs volume
 * [`hostPath`](/docs/concepts/storage/volumes/#hostpath) - HostPath volume
diff --git a/content/en/docs/reference/glossary/flexvolume.md b/content/en/docs/reference/glossary/flexvolume.md
index 91478fd1f071b..aa885000c8626 100644
--- a/content/en/docs/reference/glossary/flexvolume.md
+++ b/content/en/docs/reference/glossary/flexvolume.md
@@ -4,14 +4,14 @@ id: flexvolume
 date: 2018-06-25
 full_link: /docs/concepts/storage/volumes/#flexvolume
 short_description: >
-    FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
+    FlexVolume is an interface for creating out-of-tree volume plugins. It is deprecated in v1.23. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
 
 
 aka: 
 tags:
 - storage 
 ---
- FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
+ FlexVolume is an interface for creating out-of-tree volume plugins. It is deprecated in v1.23. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
 
 <!--more--> 
 
diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
index d0498b0c0d792..25a2e648155d2 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
@@ -375,6 +375,7 @@ For [flex-volume support](https://github.com/kubernetes/community/blob/ab55d85/c
 Kubernetes components like the kubelet and kube-controller-manager use the default path of
 `/usr/libexec/kubernetes/kubelet-plugins/volume/exec/`, yet the flex-volume directory _must be writeable_
 for the feature to work.
+(**Note** FlexVolume is deprecated in v1.23)
 
 To workaround this issue you can configure the flex-volume directory using the kubeadm
 [configuration file](/docs/reference/config-api/kubeadm-config.v1beta3/).

From 26aa51a940923b7718f04891bb53532490960769 Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Tue, 23 Nov 2021 09:58:06 +0100
Subject: [PATCH 48/68] Add CRI architecture to cluster concepts

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 content/en/docs/concepts/architecture/cri.md  | 51 +++++++++++++++++++
 .../glossary/container-runtime-interface.md   | 22 ++++++++
 2 files changed, 73 insertions(+)
 create mode 100644 content/en/docs/concepts/architecture/cri.md
 create mode 100644 content/en/docs/reference/glossary/container-runtime-interface.md

diff --git a/content/en/docs/concepts/architecture/cri.md b/content/en/docs/concepts/architecture/cri.md
new file mode 100644
index 0000000000000..e8391ca34b025
--- /dev/null
+++ b/content/en/docs/concepts/architecture/cri.md
@@ -0,0 +1,51 @@
+---
+title: Container Runtime Interface (CRI)
+content_type: concept
+weight: 50
+---
+
+<!-- overview -->
+
+The CRI is a plugin interface which enables the kubelet to use a wide variety of
+container runtimes, without having a need to recompile the cluster components.
+
+You need a working
+{{<glossary_tooltip text="container runtime" term_id="container-runtime">}} on
+each Node in your cluster, so that the
+{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} can launch
+{{< glossary_tooltip text="Pods" term_id="pod" >}} and their containers.
+
+{{< glossary_definition term_id="container-runtime-interface" length="all" >}}
+
+<!-- body -->
+
+## The API {#api}
+
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
+
+The kubelet acts as a client when connecting to the container runtime via gRPC.
+The runtime and image service endpoints have to be available in the container
+runtime, which can be configured separately within the kubelet by using the
+`--image-service-endpoint` and `--container-runtime-endpoint` [command line
+flags](/docs/reference/command-line-tools-reference/kubelet)
+
+For Kubernetes v{{< skew currentVersion >}}, the kubelet prefers to use CRI `v1`.
+If a container runtime does not support `v1` of the CRI, then the kubelet tries to
+negotiate any older supported version.
+The v{{< skew currentVersion >}} kubelet can also negotiate CRI `v1alpha2`, but
+this version is considered as deprecated.
+If the kubelet cannot negotiate a supported CRI version, the kubelet gives up
+and doesn't register as a node.
+
+## Upgrading
+
+When upgrading Kubernetes, then the kubelet tries to automatically select the
+latest CRI version on restart of the component. If that fails, then the fallback
+will take place as mentioned above. If a gRPC re-dial was required because the
+container runtime has been upgraded, then the container runtime must also
+support the initially selected version or the redial is expected to fail. This
+requires a restart of the kubelet.
+
+## {{% heading "whatsnext" %}}
+
+- Learn more about the CRI [protocol definition](https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto)
diff --git a/content/en/docs/reference/glossary/container-runtime-interface.md b/content/en/docs/reference/glossary/container-runtime-interface.md
new file mode 100644
index 0000000000000..11f7bc50f4cfc
--- /dev/null
+++ b/content/en/docs/reference/glossary/container-runtime-interface.md
@@ -0,0 +1,22 @@
+---
+title: Container Runtime Interface
+id: container-runtime-interface
+date: 2021-11-24
+full_link: /docs/concepts/architecture/cri
+short_description: >
+  The main protocol for the communication between the kubelet and Container Runtime.
+
+aka:
+tags:
+  - cri
+---
+
+The main protocol for the communication between the kubelet and Container Runtime.
+
+<!--more-->
+
+The Kubernetes Container Runtime Interface (CRI) defines the main
+[gRPC](https://grpc.io) protocol for the communication between the
+[cluster components](/docs/concepts/overview/components/#node-components)
+{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and
+{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.

From f7f336cf14fc47806c90178fe92c8b833e44fe04 Mon Sep 17 00:00:00 2001
From: Mike Dame <mdame@redhat.com>
Date: Thu, 11 Nov 2021 09:48:52 -0500
Subject: [PATCH 49/68] Add docs on scheduler MultiPoint config

---
 .../en/docs/reference/scheduling/config.md    | 182 ++++++++++++++++++
 1 file changed, 182 insertions(+)

diff --git a/content/en/docs/reference/scheduling/config.md b/content/en/docs/reference/scheduling/config.md
index bce8d36b5c7f0..204d4124ee8de 100644
--- a/content/en/docs/reference/scheduling/config.md
+++ b/content/en/docs/reference/scheduling/config.md
@@ -78,6 +78,8 @@ extension points:
    least one bind plugin is required.
 1. `postBind`: This is an informational extension point that is called after
    a Pod has been bound.
+1. `multiPoint`: This is a config-only field that allows plugins to be enabled 
+   or disabled for all of their applicable extension points simultaneously.
 
 For each extension point, you could disable specific [default plugins](#scheduling-plugins)
 or enable your own. For example:
@@ -251,6 +253,186 @@ the same configuration parameters (if applicable). This is because the scheduler
 only has one pending pods queue.
 {{< /note >}}
 
+### Plugins that apply to multiple extension points {#multipoint}
+
+Starting from `kubescheduler.config.k8s.io/v1beta3`, there is an additional field in the 
+profile config, `multiPoint`, which allows for easily enabling or disabling a plugin 
+across several extension points. The intent of `multiPoint` config is to simplify the 
+configuration needed for users and administrators when using custom profiles.
+
+Consider a plugin, `MyPlugin`, which implements the `preScore`, `score`, `preFilter`, 
+and `filter` extension points. To enable `MyPlugin` for all its available extension 
+points, the profile config looks like:
+
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta3
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: multipoint-scheduler
+    plugins:
+      multiPoint:
+        enabled:
+        - name: MyPlugin
+```
+
+This would equate to manually enabling `MyPlugin` for all of its extension 
+points, like so:
+
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta3
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: non-multipoint-scheduler
+    plugins:
+      preScore:
+        enabled:
+        - name: MyPlugin
+      score:
+        enabled:
+        - name: MyPlugin
+      preFilter:
+        enabled:
+        - name: MyPlugin
+      filter:
+        enabled:
+        - name: MyPlugin
+```
+
+One benefit of using `multiPoint` here is that if `MyPlugin` implements another 
+extension point in the future, the `multiPoint` config will automatically enable it 
+for the new extension.
+
+Specific extension points can be excluded from `MultiPoint` expansion using 
+the `disabled` field for that extension point. This works with disabling default 
+plugins, non-default plugins, or with the wildcard (`'*'`) to disable all plugins. 
+An example of this, disabling `Score` and `PreScore`, would be:
+
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta3
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: non-multipoint-scheduler
+    plugins:
+      multiPoint:
+        enabled:
+        - name: 'MyPlugin'
+      preScore:
+        disabled:
+        - name: '*'
+      score:
+        disabled:
+        - name: '*'
+```
+
+In `v1beta3`, all [default plugins](#scheduling-plugins) are enabled internally through `MultiPoint`. 
+However, individual extension points are still available to allow flexible 
+reconfiguration of the default values (such as ordering and Score weights). For 
+example, consider two Score plugins `DefaultScore1` and `DefaultScore2`, each with 
+a weight of `1`. They can be reordered with different weights like so:
+
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta3
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: multipoint-scheduler
+    plugins:
+      score:
+        enabled:
+        - name: 'DefaultScore2'
+          weight: 5
+```
+
+In this example, it's unnecessary to specify the plugins in `MultiPoint` explicitly 
+because they are default plugins. And the only plugin specified in `Score` is `DefaultScore2`.
+This is because plugins set through specific extension points will always take precedence 
+over `MultiPoint` plugins. So, this snippet essentially re-orders the two plugins 
+without needing to specify both of them.
+
+The general hierarchy for precedence when configuring `MultiPoint` plugins is as follows:
+1. Specific extension points run first, and their settings override whatever is set elsewhere
+2. Plugins manually configured through `MultiPoint` and their settings
+3. Default plugins and their default settings
+
+To demonstrate the above hierarchy, the following example is based on these plugins:
+|Plugin|Extension Points|
+|---|---|
+|`DefaultQueueSort`|`QueueSort`|
+|`CustomQueueSort`|`QueueSort`|
+|`DefaultPlugin1`|`Score`, `Filter`|
+|`DefaultPlugin2`|`Score`|
+|`CustomPlugin1`|`Score`, `Filter`|
+|`CustomPlugin2`|`Score`, `Filter`|
+
+A valid sample configuration for these plugins would be:
+
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta3
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: multipoint-scheduler
+    plugins:
+      multiPoint:
+        enabled:
+        - name: 'CustomQueueSort'
+        - name: 'CustomPlugin1'
+          weight: 3
+        - name: 'CustomPlugin2'
+        disabled:
+        - name: 'DefaultQueueSort'
+      filter:
+        disabled:
+        - name: 'DefaultPlugin1'
+      score:
+        enabled:
+        - name: 'DefaultPlugin2'
+```
+
+Note that there is no error for re-declaring a `MultiPoint` plugin in a specific 
+extension point. The re-declaration is ignored (and logged), as specific extension points 
+take precedence.
+
+Besides keeping most of the config in one spot, this sample does a few things:
+* Enables the custom `queueSort` plugin and disables the default one
+* Enables `CustomPlugin1` and `CustomPlugin2`, which will run first for all of their extension points
+* Disables `DefaultPlugin1`, but only for `filter`
+* Reorders `DefaultPlugin2` to run first in `score` (even before the custom plugins)
+
+In versions of the config before `v1beta3`, without `multiPoint`, the above snippet would equate to this:
+```yaml
+apiVersion: kubescheduler.config.k8s.io/v1beta2
+kind: KubeSchedulerConfiguration
+profiles:
+  - schedulerName: multipoint-scheduler
+    plugins:
+    
+      # Disable the default QueueSort plugin
+      queueSort:
+        enabled:
+        - name: 'CustomQueueSort'
+        disabled:
+        - name: 'DefaultQueueSort'
+        
+      # Enable custom Filter plugins
+      filter:
+        enabled:
+        - name: 'CustomPlugin1'
+        - name: 'CustomPlugin2'
+        - name: 'DefaultPlugin2'
+        disabled:
+        - name: 'DefaultPlugin1'
+        
+      # Enable and reorder custom score plugins
+      score:
+        enabled:
+        - name: 'DefaultPlugin2'
+          weight: 1
+        - name: 'DefaultPlugin1'
+          weight: 3
+```
+
+While this is a complicated example, it demonstrates the flexibility of `MultiPoint` config 
+as well as its seamless integration with the existing methods for configuring extension points.
+
 ## Scheduler configuration migrations
 
 {{< tabs name="tab_with_md" >}}

From 41547099c4a76d558bdbf07507ec192913590007 Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Tue, 23 Nov 2021 14:14:36 -0800
Subject: [PATCH 50/68] Add section for OpenAPI v3

---
 .../docs/concepts/overview/kubernetes-api.md  | 56 ++++++++++++++++++-
 1 file changed, 54 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/concepts/overview/kubernetes-api.md b/content/en/docs/concepts/overview/kubernetes-api.md
index 07b5d559d7294..e1ddda4267f0c 100644
--- a/content/en/docs/concepts/overview/kubernetes-api.md
+++ b/content/en/docs/concepts/overview/kubernetes-api.md
@@ -37,8 +37,11 @@ if you are writing an application using the Kubernetes API.
 
 Complete API details are documented using [OpenAPI](https://www.openapis.org/).
 
-The Kubernetes API server serves an OpenAPI spec via the `/openapi/v2` endpoint.
-You can request the response format using request headers as follows:
+### OpenAPI V2
+
+The Kubernetes API server serves an aggregated OpenAPI v2 spec via the
+`/openapi/v2` endpoint. You can request the response format using
+request headers as follows:
 
 <table>
   <caption style="display:none">Valid request header values for OpenAPI v2 queries</caption>
@@ -77,6 +80,55 @@ about this format, see the [Kubernetes Protobuf serialization](https://github.co
 Interface Definition Language (IDL) files for each schema located in the Go
 packages that define the API objects.
 
+### OpenAPI V3
+
+{{< feature-state state="alpha"  for_k8s_version="v1.23" >}}
+
+Kubernetes v1.23 offers initial support for publishing its APIs as OpenAPI v3; this is an
+alpha feature that is disabled by default.
+You can enable the alpha feature by turning on the
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `OpenAPIV3`
+for the kube-apiserver component.
+
+With the feature enabled, the Kubernetes API server serves an
+aggregated OpenAPI v3 spec per Kubernetes group version at the
+`/openapi/v3/apis/<group>/<version>` endpoint. Please refer to the
+table below for accepted request headers.
+
+<table>
+  <caption style="display:none">Valid request header values for OpenAPI v3 queries</caption>
+  <thead>
+     <tr>
+        <th>Header</th>
+        <th style="min-width: 50%;">Possible values</th>
+        <th>Notes</th>
+     </tr>
+  </thead>
+  <tbody>
+     <tr>
+        <td><code>Accept-Encoding</code></td>
+        <td><code>gzip</code></td>
+        <td><em>not supplying this header is also acceptable</em></td>
+     </tr>
+     <tr>
+        <td rowspan="3"><code>Accept</code></td>
+        <td><code>application/com.github.proto-openapi.spec.v3@v1.0+protobuf</code></td>
+        <td><em>mainly for intra-cluster use</em></td>
+     </tr>
+     <tr>
+        <td><code>application/json</code></td>
+        <td><em>default</em></td>
+     </tr>
+     <tr>
+        <td><code>*</code></td>
+        <td><em>serves </em><code>application/json</code></td>
+     </tr>
+  </tbody>
+</table>
+
+A discovery endpoint `/openapi/v3` is provided to see a list of all
+group/versions available. This endpoint only returns JSON.
+
 ## Persistence
 
 Kubernetes stores the serialized state of objects by writing them into

From 89e744666c9e2062ac39691d2855d7b962feca23 Mon Sep 17 00:00:00 2001
From: ravisantoshgudimetla <ravisantoshgudimetla@gmail.com>
Date: Tue, 23 Nov 2021 08:13:06 -0500
Subject: [PATCH 51/68] [docs][windows]: Pod OS field update

Co-authored-by: James Sturtevant <jsturtevant@gmail.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../feature-gates.md                          |  3 ++
 .../windows/intro-windows-in-kubernetes.md    | 31 +++++++++++++++++++
 .../windows/user-guide-windows-containers.md  | 16 +++++++++-
 3 files changed, 49 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 81e53092cb88f..9c582b1472033 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -120,6 +120,7 @@ different Kubernetes components.
 | `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
 | `HPAContainerMetrics` | `false` | Alpha | 1.20 | |
 | `HPAScaleToZero` | `false` | Alpha | 1.16 | |
+| `IdentifyPodOS` | `false` | Alpha | 1.23 | |
 | `IndexedJob` | `false` | Alpha | 1.21 | 1.21 |
 | `IndexedJob` | `true` | Beta | 1.22 | |
 | `InTreePluginAWSUnregister` | `false` | Alpha | 1.21 | |
@@ -779,6 +780,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `HyperVContainer`: Enable
   [Hyper-V isolation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container)
   for Windows containers.
+- `IdentifyPodOS`: Allows the Pod OS field to be specified. This helps in identifying the OS of the pod
+  authoritatively during the API server admission time. In Kubernetes {{< skew currentVersion >}}, the allowed values for the `pod.spec.os.name` are `windows` and `linux`.
 - `ImmutableEphemeralVolumes`: Allows for marking individual Secrets and ConfigMaps as
   immutable for better safety and performance.
 - `InTreePluginAWSUnregister`: Stops registering the aws-ebs in-tree plugin in kubelet
diff --git a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
index c2160e330fae0..1140403fd73d9 100644
--- a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
+++ b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
@@ -153,6 +153,37 @@ section refers to several key workload enablers and how they map to Windows.
   * `emptyDir` volumes
   * Named pipe host mounts
   * Resource limits
+  * OS field: 
+              {{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+               `.spec.os.name` should be set to `windows` to indicate that the current Pod uses Windows containers.
+               `IdentifyPodOS` feature gate needs to be enabled for this field to be recognized and used by control plane
+               components and kubelet.
+               {{< note >}}
+              If the `IdentifyPodOS` feature gate is enabled and you set the `.spec.os.name` field to `windows`, you must not set the following fields in the `.spec` of that Pod:
+               * `spec.hostPID`
+               * `spec.hostIPC`
+               * `spec.securityContext.seLinuxOptions`
+               * `spec.securityContext.seccompProfile`
+               * `spec.securityContext.fsGroup`
+               * `spec.securityContext.fsGroupChangePolicy`
+               * `spec.securityContext.sysctls`
+               * `spec.shareProcessNamespace`
+               * `spec.securityContext.runAsUser`
+               * `spec.securityContext.runAsGroup`
+               * `spec.securityContext.supplementalGroups`
+               * `spec.containers[*].securityContext.seLinuxOptions`
+               * `spec.containers[*].securityContext.seccompProfile`
+               * `spec.containers[*].securityContext.capabilities`
+               * `spec.containers[*].securityContext.readOnlyRootFilesystem`
+               * `spec.containers[*].securityContext.privileged`
+               * `spec.containers[*].securityContext.allowPrivilegeEscalation`
+               * `spec.containers[*].securityContext.procMount`
+               * `spec.containers[*].securityContext.runAsUser`
+               * `spec.containers[*].securityContext.runAsGroup`
+
+            Note: In this table, wildcards (*) indicate all elements in a list. For example, spec.containers[*].securityContext refers to the Security Context object for all defined containers. If not, Pod API validation would fail causing admission failures.
+            {{< /note >}}
+
 * [Workload resources](/docs/concepts/workloads/controllers/) including:
   * ReplicaSet
   * Deployments
diff --git a/content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md b/content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md
index ec47f5637a791..177f7623f6488 100644
--- a/content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md
+++ b/content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md
@@ -160,7 +160,21 @@ Users today need to use some combination of taints and node selectors in order t
 keep Linux and Windows workloads on their respective OS-specific nodes. 
 This likely imposes a burden only on Windows users. The recommended approach is outlined below, 
 with one of its main goals being that this approach should not break compatibility for existing Linux workloads.
-
+ {{< note >}}
+If the `IdentifyPodOS` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is
+enabled, you can (and should) set `.spec.os.name` for a Pod to indicate the operating system
+that the containers in that Pod are designed for. For Pods that run Linux containers, set
+`.spec.os.name` to `linux`. For Pods that run Windows containers, set `.spec.os.name`
+to Windows.
+
+The scheduler does not use the value of `.spec.os.name` when assigning Pods to nodes. You should
+use normal Kubernetes mechanisms for
+[assigning pods to nodes](/docs/concepts/scheduling-eviction/assign-pod-node/)
+to ensure that the control plane for your cluster places pods onto nodes that are running the
+appropriate operating system.
+ no effect on the scheduling of the Windows pods, so taints and tolerations and node selectors are still required
+ to ensure that the Windows pods land onto appropriate Windows nodes.
+ {{< /note >}}
 ### Ensuring OS-specific workloads land on the appropriate container host
 
 Users can ensure Windows containers can be scheduled on the appropriate host using Taints and Tolerations. 

From ef6668539c37efab4338ff05728fcdd3d97c2bc1 Mon Sep 17 00:00:00 2001
From: Sergey Kanzhelev <S.Kanzhelev@live.com>
Date: Tue, 30 Nov 2021 19:37:31 +0000
Subject: [PATCH 52/68] gRPC probes

---
 .../_posts/2018-10-01-health-checking-grpc.md |  2 +
 .../feature-gates.md                          | 10 ++--
 ...igure-liveness-readiness-startup-probes.md | 50 ++++++++++++++++++-
 .../en/examples/pods/probe/grpc-liveness.yaml | 15 ++++++
 4 files changed, 71 insertions(+), 6 deletions(-)
 create mode 100644 content/en/examples/pods/probe/grpc-liveness.yaml

diff --git a/content/en/blog/_posts/2018-10-01-health-checking-grpc.md b/content/en/blog/_posts/2018-10-01-health-checking-grpc.md
index 21eb668dc23a9..e6e584b27479f 100644
--- a/content/en/blog/_posts/2018-10-01-health-checking-grpc.md
+++ b/content/en/blog/_posts/2018-10-01-health-checking-grpc.md
@@ -4,6 +4,8 @@ title:  'Health checking gRPC servers on Kubernetes'
 date: 2018-10-01
 ---
 
+_Built-in gRPC probes were introduced in Kubernetes 1.23. To learn more, see [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe)._
+
 **Author**: [Ahmet Alp Balkan](https://twitter.com/ahmetb) (Google)
 
 [gRPC](https://grpc.io) is on its way to becoming the lingua franca for
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 73bf143a43009..63088e2cc26e3 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -122,6 +122,7 @@ different Kubernetes components.
 | `ExperimentalHostUserNamespaceDefaulting` | `false` | Beta | 1.5 | |
 | `GracefulNodeShutdown` | `false` | Alpha | 1.20 | 1.20 |
 | `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
+| `GRPCContainerProbe` | `false` | Alpha | 1.23 | |
 | `HPAContainerMetrics` | `false` | Alpha | 1.20 | |
 | `HPAScaleToZero` | `false` | Alpha | 1.16 | |
 | `IndexedJob` | `false` | Alpha | 1.21 | 1.21 |
@@ -573,10 +574,10 @@ Each feature gate is designed for enabling/disabling a specific feature:
   extended tokens by starting `kube-apiserver` with flag `--service-account-extend-token-expiration=false`.
   Check [Bound Service Account Tokens](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/1205-bound-service-account-tokens/README.md)
    for more details.
-- `ControllerManagerLeaderMigration`: Enables Leader Migration for 
-  [kube-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#initial-leader-migration-configuration) and 
-  [cloud-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#deploy-cloud-controller-manager) which allows a cluster operator to live migrate 
-  controllers from the kube-controller-manager into an external controller-manager 
+- `ControllerManagerLeaderMigration`: Enables Leader Migration for
+  [kube-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#initial-leader-migration-configuration) and
+  [cloud-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#deploy-cloud-controller-manager) which allows a cluster operator to live migrate
+  controllers from the kube-controller-manager into an external controller-manager
   (e.g. the cloud-controller-manager) in an HA cluster without downtime.
 - `CPUManager`: Enable container level CPU affinity support, see
   [CPU Management Policies](/docs/tasks/administer-cluster/cpu-management-policies/).
@@ -782,6 +783,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
   and gracefully terminate pods running on the node. See
   [Graceful Node Shutdown](/docs/concepts/architecture/nodes/#graceful-node-shutdown)
   for more details.
+- `GRPCContainerProbe`: Enables gPRC probe method for {Liveness,Readiness,Startup}Probe. See [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe).
 - `HPAContainerMetrics`: Enable the `HorizontalPodAutoscaler` to scale based on
   metrics from individual containers in target pods.
 - `HPAScaleToZero`: Enables setting `minReplicas` to 0 for `HorizontalPodAutoscaler`
diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index d9ab2056dac80..2ef2b1368c06f 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -220,11 +220,57 @@ After 15 seconds, view Pod events to verify that liveness probes:
 kubectl describe pod goproxy
 ```
 
+## Define a gRPC liveness probe
+
+{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+
+If your application implements [gRPC Health Checking Protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md),
+kubelet can be configured to use it for application liveness checks.
+
+{{< codenew file="pods/probe/grpc-liveness.yaml">}}
+
+To use a gRPC probe, `port` must be configured. If the health endpoint is configured
+on a non-default service, `service` must be configured.
+
+{{< note >}}
+Unlike HTTP and TCP probes, named ports cannot be used and custom host cannot be configured.
+{{< /note >}}
+
+Configuration problems (e.g. incorrect port and service, unimplemented health checking protocol)
+are considered a probe failure, similar to HTTP and TCP probes.
+
+Before Kubernetes 1.23, gRPC health probes were often implemented using [grpc-health-probe](https://github.com/grpc-ecosystem/grpc-health-probe/),
+as described in the blog post [Health checking gRPC servers on Kubernetes](/blog/2018/10/01/health-checking-grpc-servers-on-kubernetes/).
+The built-in gRPC probes behavior is similar to one implemented by grpc-health-probe.
+When migrating from grpc-health-probe to built-in probes, remember the following differences:
+
+- Built-in probes will run against pod IP, unlike grpc-health-probe that often runs against `127.0.0.1`.
+  Be sure to configure your gRPC endpoint to listen for pod IP address.
+- Built-in probes do not currently support any authentication parameters (like `-tls`).
+- There are no error codes in built-in probes. All errors are considered as probe failures.
+- If `ExecProbeTimeout` feature gate is set to `false`, grpc-health-probe will NOT
+  respect `timeoutSeconds` setting (which defaults to 1s),
+  while built-in probe will fail on timeout.
+
+To try the gRPC liveness check, create a Pod using the command below.
+In the example below, etcd pod is configured to use gRPC liveness probe.
+
+
+```shell
+kubectl apply -f https://k8s.io/examples/pods/probe/content/en/examples/pods/probe/grpc-liveness.yaml
+```
+
+After 15 seconds, view Pod events to verify that the liveness probes has not failed:
+
+```shell
+kubectl describe pod etcd-with-grpc
+```
+
 ## Use a named port
 
 You can use a named
 [ContainerPort](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerport-v1-core)
-for HTTP or TCP liveness checks:
+for HTTP and TCP probes. Note, gRPC probe does not support named port.
 
 ```yaml
 ports:
@@ -349,7 +395,7 @@ This defect was corrected in Kubernetes v1.20. You may have been relying on the
 even without realizing it, as the default timeout is 1 second.
 As a cluster administrator, you can disable the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) `ExecProbeTimeout` (set it to `false`)
 on each kubelet to restore the  behavior from older versions, then remove that override
-once all the exec probes in the cluster have a `timeoutSeconds` value set.  
+once all the exec probes in the cluster have a `timeoutSeconds` value set.
 If you have pods that are impacted from the default 1 second timeout,
 you should update their probe timeout so that you're ready for the
 eventual removal of that feature gate.
diff --git a/content/en/examples/pods/probe/grpc-liveness.yaml b/content/en/examples/pods/probe/grpc-liveness.yaml
new file mode 100644
index 0000000000000..84d716df28009
--- /dev/null
+++ b/content/en/examples/pods/probe/grpc-liveness.yaml
@@ -0,0 +1,15 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: etcd-with-grpc
+spec:
+  containers:
+  - name: etcd
+    image: k8s.gcr.io/etcd:3.5.1-0
+    command: [ "/usr/local/bin/etcd", "--data-dir",  "/var/lib/etcd", "--listen-client-urls", "http://0.0.0.0:2379", "--advertise-client-urls", "http://127.0.0.1:2379", "--log-level", "debug"]
+    ports:
+    - containerPort: 2379
+    livenessProbe:
+      gRPC:
+        port: 2379
+      initialDelaySeconds: 10

From 6a684469cb9fd385e61fc1f75ae6b35eef332b77 Mon Sep 17 00:00:00 2001
From: Brandon Smith <BRASMITH@MICROSOFT.COM>
Date: Tue, 30 Nov 2021 15:49:17 -0800
Subject: [PATCH 53/68] Windows HostProcess Beta 1.23 Documentation (#30391)

* Added initial version change

* Added more information for HostProcess in 1.23, removed content relating to 1.22 specifically.

* Made containerd mention specific to 1.6

* Added note about base images and removed annotation mentions

* Reworded prerequisites section.
---
 .../feature-gates.md                          |   2 +-
 .../create-hostprocess-pod.md                 | 135 ++++++++----------
 2 files changed, 64 insertions(+), 73 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index b4f0b7c38c6ea..83bce338d87c3 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -203,7 +203,7 @@ different Kubernetes components.
 | `WinDSR` | `false` | Alpha | 1.14 | |
 | `WinOverlay` | `false` | Alpha | 1.14 | 1.19 |
 | `WinOverlay` | `true` | Beta | 1.20 | |
-| `WindowsHostProcessContainers` | `false` | Alpha | 1.22 | |
+| `WindowsHostProcessContainers` | `false` | Beta | 1.23 | |
 {{< /table >}}
 
 ### Feature gates for graduated or deprecated features
diff --git a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
index 2ab2bd3661edb..0c33c79552462 100644
--- a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
+++ b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
@@ -7,102 +7,84 @@ min-kubernetes-server-version: 1.22
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.23" state="beta" >}}
 
-Windows HostProcess containers enable you to run containerized 
-workloads on a Windows host. These containers operate as 
-normal processes but have access to the host network namespace, 
-storage, and devices when given the appropriate user privileges. 
+Windows HostProcess containers enable you to run containerized
+workloads on a Windows host. These containers operate as
+normal processes but have access to the host network namespace,
+storage, and devices when given the appropriate user privileges.
 HostProcess containers can be used to deploy network plugins,
-storage configurations, device plugins, kube-proxy, and other 
-components to Windows nodes without the need for dedicated proxies or 
+storage configurations, device plugins, kube-proxy, and other
+components to Windows nodes without the need for dedicated proxies or
 the direct installation of host services.
 
-Administrative tasks such as installation of security patches, event 
-log collection, and more can be performed without requiring cluster operators to 
-log onto each Window node. HostProcess containers can run as any user that is 
-available on the host or is in the domain of the host machine, allowing administrators 
-to restrict resource access through user permissions. While neither filesystem or process 
-isolation are supported, a new volume is created on the host upon starting the container 
-to give it a clean and consolidated workspace. HostProcess containers can also be built on 
-top of existing Windows base images and do not inherit the same 
-[compatibility requirements](https://docs.microsoft.com/virtualization/windowscontainers/deploy-containers/version-compatibility) 
-as Windows server containers, meaning that the version of the base images does not need 
-to match that of the host. HostProcess containers also support 
+Administrative tasks such as installation of security patches, event
+log collection, and more can be performed without requiring cluster operators to
+log onto each Window node. HostProcess containers can run as any user that is
+available on the host or is in the domain of the host machine, allowing administrators
+to restrict resource access through user permissions. While neither filesystem or process
+isolation are supported, a new volume is created on the host upon starting the container
+to give it a clean and consolidated workspace. HostProcess containers can also be built on
+top of existing Windows base images and do not inherit the same
+[compatibility requirements](https://docs.microsoft.com/virtualization/windowscontainers/deploy-containers/version-compatibility)
+as Windows server containers, meaning that the version of the base images does not need
+to match that of the host. It is, however, recommended that you use the same base image
+version as your Windows Server container workloads to ensure you do not have any unused
+images taking up space on the node. HostProcess containers also support
 [volume mounts](./create-hostprocess-pod#volume-mounts) within the container volume.
 
 ### When should I use a Windows HostProcess container?
 
-- When you need to perform tasks which require the networking namespace of the host. 
+- When you need to perform tasks which require the networking namespace of the host.
 HostProcess containers have access to the host's network interfaces and IP addresses.
 - You need access to resources on the host such as the filesystem, event logs, etc.
 - Installation of specific device drivers or Windows services.
-- Consolidation of administrative tasks and security policies. This reduces the degree of 
+- Consolidation of administrative tasks and security policies. This reduces the degree of
 privileges needed by Windows nodes.
 
 
-## {{% heading "prerequisites" %}}
+## {{% heading "prerequisites" %}}% version-check %}}
 
-{{% version-check %}}
+In 1.23 the HostProcess container feature is enabled by default. The kublet will
+communicate with containerd directly by passing the hostprocess flag via CRI. You can use the
+latest version of containerd (v1.6+) to run HostProcess containers.
+[How to install containerd.](/docs/setup/production-environment/container-runtimes/#containerd)
 
-To enable HostProcess containers while in Alpha you need to pass the following feature gate flag to 
-**kubelet** and **kube-apiserver**. 
-See [Features Gates](/docs/reference/command-line-tools-reference/feature-gates/#overview) 
-documentation for more details.
+To *disable* HostProcess containers you need to pass the following feature gate flag to the
+**kubelet** and **kube-apiserver**:
 
-```
---feature-gates=WindowsHostProcessContainers=true
+```powershell
+--feature-gates=WindowsHostProcessContainers=false
 ```
 
-You can use the latest version of Containerd (v1.5.4+) with the following settings using the containerd 
-v2 configuration. Add these annotations to any runtime configurations were you wish to enable the 
-HostProcess container feature.
-
+See [Features Gates](/docs/reference/command-line-tools-reference/feature-gates/#overview)
+documentation for more details.
 
-```
-[plugins]
-  [plugins."io.containerd.grpc.v1.cri"]
-    [plugins."io.containerd.grpc.v1.cri".containerd]
-      [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
-        container_annotations = ["microsoft.com/hostprocess-container"]
-        pod_annotations = ["microsoft.com/hostprocess-container"]
-    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
-      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runhcs-wcow-process]
-        container_annotations = ["microsoft.com/hostprocess-container"]
-        pod_annotations = ["microsoft.com/hostprocess-container"]
-```
 
-The current versions of containerd ship with a version of hcsshim that does not have support. 
-You will need to build a version of hcsshim from the main branch following the 
-[instructions in hcsshim](https://github.com/Microsoft/hcsshim/#containerd-shim). 
-Once the containerd shim is built you can replace the file in your contianerd installation. 
-For example if you followed the instructions to 
-[install containerd](/docs/setup/production-environment/container-runtimes/#containerd)
-replace the `containerd-shim-runhcs-v1.exe` is installed at `$Env:ProgramFiles\containerd` with the newly built shim.
 
 ## Limitations
 
-- HostProcess containers require version 1.5.4 or higher of the containerd {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
-- As of v1.22 HostProcess pods can only contain HostProcess containers. This is a current limitation 
+- HostProcess containers require containerd 1.6 or higher
+{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
+- As of v1.23 HostProcess pods can only contain HostProcess containers. This is a current limitation
 of the Windows OS; non-privileged Windows containers cannot share a vNIC with the host IP namespace.
-- HostProcess containers run as a process on the host and do not have any degree of 
-isolation other than resource constraints imposed on the HostProcess user account. Neither 
+- HostProcess containers run as a process on the host and do not have any degree of
+isolation other than resource constraints imposed on the HostProcess user account. Neither
 filesystem or Hyper-V isolation are supported for HostProcess containers.
-- Volume mounts are supported and are mounted under the container volume. 
-See [Volume Mounts](#volume-mounts)
-- A limited set of host user accounts are available for HostProcess containers by default. 
+- Volume mounts are supported and are mounted under the container volume. See [Volume Mounts](#volume-mounts)
+- As of 1.23, a limited set of host user accounts are available for HostProcess containers by default.
 See [Choosing a User Account](#choosing-a-user-account).
-- Resource limits (disk, memory, cpu count) are supported in the same fashion as processes 
+- Resource limits (disk, memory, cpu count) are supported in the same fashion as processes
 on the host.
-- Both Named pipe mounts and Unix domain sockets are **not** currently supported and should instead 
+- Both Named pipe mounts and Unix domain sockets are **not** currently supported and should instead
 be accessed via their path on the host (e.g. \\\\.\\pipe\\\*)
 
 ## HostProcess Pod configuration requirements
 
-Enabling a Windows HostProcess pod requires setting the right configurations in the pod security 
-configuration. Of the policies defined in the [Pod Security Standards](/docs/concepts/security/pod-security-standards) 
-HostProcess pods are disallowed by the baseline and restricted policies. It is therefore recommended 
-that HostProcess pods run in alignment with the privileged profile. 
+Enabling a Windows HostProcess pod requires setting the right configurations in the pod security
+configuration. Of the policies defined in the [Pod Security Standards](/docs/concepts/security/pod-security-standards)
+HostProcess pods are disallowed by the baseline and restricted policies. It is therefore recommended
+that HostProcess pods run in alignment with the privileged profile.
 
 When running under the privileged policy, here are
 the configurations which need to be set to enable the creation of a HostProcess pod:
@@ -185,10 +167,10 @@ spec:
 
 ## Volume Mounts
 
-HostProcess containers support the ability to mount volumes within the container volume space. 
-Applications running inside the container can access volume mounts directly via relative or 
-absolute paths. An environment variable `$CONTAINER_SANDBOX_MOUNT_POINT` is set upon container 
-creation and provides the absolute host path to the container volume. Relative paths are based 
+HostProcess containers support the ability to mount volumes within the container volume space.
+Applications running inside the container can access volume mounts directly via relative or
+absolute paths. As of v1.23, an environment variable `$CONTAINER_SANDBOX_MOUNT_POINT` is set upon container
+creation and provides the absolute host path to the container volume. Relative paths are based
 upon the `Pod.containers.volumeMounts.mountPath` configuration.
 
 ### Example {#volume-mount-example}
@@ -199,13 +181,22 @@ To access service account tokens the following path structures are supported wit
 
 `$CONTAINER_SANDBOX_MOUNT_POINT\var\run\secrets\kubernetes.io\serviceaccount\`
 
+## Resource Limits
+
+Resource limits (disk, memory, cpu count) are applied to the job and are job wide.
+For example, with a limit of 10MB set, the memory allocated for any HostProcess job object
+will be capped at 10MB. This is the same behavior as other Windows container types.
+These limits would be specified the same way they are currently for whatever orchestrator
+or runtime is being used. The only difference is in the disk resource usage calculation
+used for resource tracking due to the difference in how HostProcess containers are bootstrapped.
+
 ## Choosing a User Account
 
-HostProcess containers support the ability to run as one of three supported Windows service accounts:
+As of 1.23, HostProcess containers support the ability to run as one of three supported Windows service accounts:
 
-- **[LocalSystem](https://docs.microsoft.com/en-us/windows/win32/services/localsystem-account)**
-- **[LocalService](https://docs.microsoft.com/en-us/windows/win32/services/localservice-account)**
-- **[NetworkService](https://docs.microsoft.com/en-us/windows/win32/services/networkservice-account)**
+- **[LocalSystem](https://docs.microsoft.com/windows/win32/services/localsystem-account)**
+- **[LocalService](https://docs.microsoft.com/windows/win32/services/localservice-account)**
+- **[NetworkService](https://docs.microsoft.com/windows/win32/services/networkservice-account)**
 
 You should select an appropriate Windows service account for each HostProcess
 container, aiming to limit the degree of privileges so as to avoid accidental (or even

From 0cbedcfeedf1354176bddc73f1da6a62af939e50 Mon Sep 17 00:00:00 2001
From: Ayushman Mishra <ayushvidushi01@gmail.com>
Date: Wed, 1 Dec 2021 18:22:19 +0530
Subject: [PATCH 54/68] changes made

Signed-off-by: Ayushman Mishra <ayushvidushi01@gmail.com>

changes

Signed-off-by: Ayushman Mishra <ayushvidushi01@gmail.com>
---
 content/en/docs/concepts/extend-kubernetes/_index.md          | 2 +-
 content/en/docs/concepts/storage/persistent-volumes.md        | 4 ++--
 content/en/docs/reference/glossary/flexvolume.md              | 4 ++--
 .../tools/kubeadm/troubleshooting-kubeadm.md                  | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/concepts/extend-kubernetes/_index.md b/content/en/docs/concepts/extend-kubernetes/_index.md
index edb550bbeda4b..35669cc9556be 100644
--- a/content/en/docs/concepts/extend-kubernetes/_index.md
+++ b/content/en/docs/concepts/extend-kubernetes/_index.md
@@ -163,7 +163,7 @@ After a request is authorized, if it is a write operation, it also goes through
 ) allow users to mount volume types without built-in support by having the
 Kubelet call a Binary Plugin to mount the volume.
 
-FlexVolume is deprecated in v1.23. Out-of-tree CSI driver is the recommended way to write volume drivers in Kubernetes. See this doc [here](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md#kubernetes-volume-plugin-faq-for-storage-vendors) for more information.
+FlexVolume is deprecated since Kubernetes v1.23. The Out-of-tree CSI driver is the recommended way to write volume drivers in Kubernetes. See [Kubernetes Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md#kubernetes-volume-plugin-faq-for-storage-vendors) for more information.
 
 
 ### Device Plugins
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 8e8a6241ca867..b5a6f234b01cf 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -318,8 +318,6 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
 * [`cephfs`](/docs/concepts/storage/volumes/#cephfs) - CephFS volume
 * [`csi`](/docs/concepts/storage/volumes/#csi) - Container Storage Interface (CSI)
 * [`fc`](/docs/concepts/storage/volumes/#fc) - Fibre Channel (FC) storage
-* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume
-  (**deprecated** in v1.23)
 * [`gcePersistentDisk`](/docs/concepts/storage/volumes/#gcepersistentdisk) - GCE Persistent Disk
 * [`glusterfs`](/docs/concepts/storage/volumes/#glusterfs) - Glusterfs volume
 * [`hostPath`](/docs/concepts/storage/volumes/#hostpath) - HostPath volume
@@ -335,6 +333,8 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
 
 The following types of PersistentVolume are deprecated. This means that support is still available but will be removed in a future Kubernetes release.
 
+* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume
+  (**deprecated** in v1.23)
 * [`cinder`](/docs/concepts/storage/volumes/#cinder) - Cinder (OpenStack block storage)
   (**deprecated** in v1.18)
 * [`flocker`](/docs/concepts/storage/volumes/#flocker) - Flocker storage
diff --git a/content/en/docs/reference/glossary/flexvolume.md b/content/en/docs/reference/glossary/flexvolume.md
index aa885000c8626..1f54e4dc683ba 100644
--- a/content/en/docs/reference/glossary/flexvolume.md
+++ b/content/en/docs/reference/glossary/flexvolume.md
@@ -4,14 +4,14 @@ id: flexvolume
 date: 2018-06-25
 full_link: /docs/concepts/storage/volumes/#flexvolume
 short_description: >
-    FlexVolume is an interface for creating out-of-tree volume plugins. It is deprecated in v1.23. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
+    FlexVolume is a deprecated interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface that addresses several problems with FlexVolume.
 
 
 aka: 
 tags:
 - storage 
 ---
- FlexVolume is an interface for creating out-of-tree volume plugins. It is deprecated in v1.23. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
+ FlexVolume is a deprecated interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface that addresses several problems with FlexVolume.
 
 <!--more--> 
 
diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
index 25a2e648155d2..9108ecafcd5a1 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
@@ -375,7 +375,7 @@ For [flex-volume support](https://github.com/kubernetes/community/blob/ab55d85/c
 Kubernetes components like the kubelet and kube-controller-manager use the default path of
 `/usr/libexec/kubernetes/kubelet-plugins/volume/exec/`, yet the flex-volume directory _must be writeable_
 for the feature to work.
-(**Note** FlexVolume is deprecated in v1.23)
+(**Note**: FlexVolume was deprecated in the Kubernetes v1.23 release)
 
 To workaround this issue you can configure the flex-volume directory using the kubeadm
 [configuration file](/docs/reference/config-api/kubeadm-config.v1beta3/).

From 3797c338a70d1cf9ae9fda1d941ebc6cd00f99a0 Mon Sep 17 00:00:00 2001
From: Sergey Kanzhelev <S.Kanzhelev@live.com>
Date: Wed, 1 Dec 2021 18:57:07 +0000
Subject: [PATCH 55/68] grpc field name consistency

---
 content/en/examples/pods/probe/grpc-liveness.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/examples/pods/probe/grpc-liveness.yaml b/content/en/examples/pods/probe/grpc-liveness.yaml
index 84d716df28009..578fd080a4c38 100644
--- a/content/en/examples/pods/probe/grpc-liveness.yaml
+++ b/content/en/examples/pods/probe/grpc-liveness.yaml
@@ -10,6 +10,6 @@ spec:
     ports:
     - containerPort: 2379
     livenessProbe:
-      gRPC:
+      grpc:
         port: 2379
       initialDelaySeconds: 10

From 40e06a6fdb055c8df1f1d362b1d1b2d12f934924 Mon Sep 17 00:00:00 2001
From: Matthew Cary <mattcary@google.com>
Date: Thu, 3 Jun 2021 09:39:09 -0700
Subject: [PATCH 56/68] KEP 1847 Statefulset auto-delete documentation

---
 .../workloads/controllers/statefulset.md      | 78 +++++++++++++++++++
 1 file changed, 78 insertions(+)

diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index 5197fe4f20d25..07782425185d8 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -301,6 +301,84 @@ already attempted to run with the bad configuration.
 StatefulSet will then begin to recreate the Pods using the reverted template.
 
 
+## PersistentVolumeClaim retention
+
+{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+
+The optional `.spec.persistentVolumeClaimRetentionPolicy` field controls if
+and how PVCs are deleted during the lifecycle of a StatefulSet. You must enable the
+`StatefulSetAutoDeletePVC` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+to use this field. Once enabled, there are two policies you can configure for each
+StatefulSet:
+
+`whenDeleted`
+: configures the volume retention behavior that applies when the StatefulSet is deleted
+
+`whenScaled`
+: configures the volume retention behavior that applies when the replica count of
+  the StatefulSet   is reduced; for example, when scaling down the set.
+  
+For each policy that you can configure, you can set the value to either `Delete` or `Retain`.
+
+`Delete`
+: The PVCs created from the StatefulSet `volumeClaimTemplate` are deleted for each Pod
+  affected by the policy. With the `whenDeleted` policy all PVCs from the
+  `volumeClaimTemplate` are deleted after their Pods have been deleted. With the
+  `whenScaled` policy, only PVCs corresponding to Pod replicas being scaled down are
+  deleted, after their Pods have been deleted.
+
+`Retain` (default)
+: PVCs from the `volumeClaimTemplate` are not affected when their Pod is
+  deleted. This is the behavior before this new feature.
+
+Bear in mind that these policies **only** apply when Pods are being removed due to the
+StatefulSet being deleted or scaled down. For example, if a Pod associated with a StatefulSet
+fails due to node failure, and the control plane creates a replacement Pod, the StatefulSet
+retains the existing PVC.  The existing volume is unaffected, and the cluster will attach it to
+the node where the new Pod is about to launch.
+  
+The default for policies is `Retain`, matching the StatefulSet behavior before this new feature.
+
+Here is an example policy.
+
+```yaml
+apiVersion: apps/v1
+kind: StatefulSet
+...
+spec:
+  persistentVolumeClaimRetentionPolicy:
+    whenDeleted: Retain
+    whenScaled: Delete
+...
+```
+
+The StatefulSet {{<glossary_tooltip text="controller" term_id="controller">}} adds [owner
+references](/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications)
+to its PVCs, which are then deleted by the {{<glossary_tooltip text="garbage collector"
+term_id="garbage-collection">}} after the Pod is terminated. This enables the Pod to
+cleanly unmount all volumes before the PVCs are deleted (and before the backing PV and
+volume are deleted, depending on the retain policy).  When you set the `whenDeleted`
+policy to `Delete`, an owner reference to the StatefulSet instance is placed on all PVCs
+associated with that StatefulSet.
+
+The `whenScaled` policy must delete PVCs only when a Pod is scaled down, and not when a
+Pod is deleted for another reason. When reconciling, the StatefulSet controller compares
+its desired replica count to the actual Pods present on the cluster. Any StatefulSet Pod
+whose id greater than the replica count is condemned and marked for deletion. If the
+`whenScaled` policy is `Delete`, the condemned Pods are first set as owners to the
+associated StatefulSet template PVCs, before the Pod is deleted. This causes the PVCs
+to be garbage collected after only the condemned Pods have terminated.
+
+This means that if the controller crashes and restarts, no Pod will be deleted before its
+owner reference has been updated appropriate to the policy. If a condemned Pod is
+force-deleted while the controller is down, the owner reference may or may not have been
+set up, depending on when the controller crashed. It may take several reconcile loops to
+update the owner references, so some condemned Pods may have set up owner references and
+other may not. For this reason we recommend waiting for the controller to come back up,
+which will verify owner references before terminating Pods. If that is not possible, the
+operator should verify the owner references on PVCs to ensure the expected objects are
+deleted when Pods are force-deleted.
+
 ## {{% heading "whatsnext" %}}
 
 * Learn about [Pods](/docs/concepts/workloads/pods).

From 94e62c43bf56fe4772c93a272866313186c3b24b Mon Sep 17 00:00:00 2001
From: David Porter <porterdavid@google.com>
Date: Tue, 23 Nov 2021 12:05:09 -0800
Subject: [PATCH 57/68] docs: Pod priority based graceful node shutdown

Signed-off-by: David Porter <porterdavid@google.com>
---
 .../en/docs/concepts/architecture/nodes.md    | 98 +++++++++++++++++--
 1 file changed, 91 insertions(+), 7 deletions(-)

diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md
index a57d47219e482..4b3ee0e1aa103 100644
--- a/content/en/docs/concepts/architecture/nodes.md
+++ b/content/en/docs/concepts/architecture/nodes.md
@@ -424,20 +424,104 @@ for gracefully terminating normal pods, and the last 10 seconds would be
 reserved for terminating [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical).
 
 {{< note >}}
-When pods were evicted during the graceful node shutdown, they are marked as failed.
-Running `kubectl get pods` shows the status of the the evicted pods as `Shutdown`.
+When pods were evicted during the graceful node shutdown, they are marked as shutdown.
+Running `kubectl get pods` shows the status of the the evicted pods as `Terminated`.
 And `kubectl describe pod` indicates that the pod was evicted because of node shutdown:
 
 ```
-Status:         Failed
-Reason:         Shutdown
-Message:        Node is shutting, evicting pods
+Reason:         Terminated
+Message:        Pod was terminated in response to imminent node shutdown.
 ```
 
-Failed pod objects will be preserved until explicitly deleted or [cleaned up by the GC](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection).
-This is a change of behavior compared to abrupt node termination.
 {{< /note >}}
 
+### Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown}
+
+{{< feature-state state="alpha" for_k8s_version="v1.23" >}}
+
+To provide more flexibility during graceful node shutdown around the ordering
+of pods during shutdown, graceful node shutdown honors the PriorityClass for
+Pods, provided that you enabled this feature in your cluster. The feature
+allows allows cluster administers to explicitly define the ordering of pods
+during graceful node shutdown based on [priority
+classes](docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass).
+
+The [Graceful Node Shutdown](#graceful-node-shutdown) feature, as described
+above, shuts down pods in two phases, non-critical pods, followed by critical
+pods. If additional flexibility is needed to explicitly define the ordering of
+pods during shutdown in a more granular way, pod priority based graceful
+shutdown can be used.
+
+When graceful node shutdown honors pod priorities, this makes it possible to do
+graceful node shutdown in multiple phases, each phase shutting down a
+particular priority class of pods. The kubelet can be configured with the exact
+phases and shutdown time per phase.
+
+Assuming the following custom pod [priority
+classes](docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass)
+in a cluster,
+
+|Pod priority class name|Pod priority class value|
+|-------------------------|------------------------|
+|`custom-class-a`         | 100000                 |
+|`custom-class-b`         | 10000                  |
+|`custom-class-c`         | 1000                   |
+|`regular/unset`          | 0                      |
+
+Within the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
+the settings for `shutdownGracePeriodByPodPriority` could look like:
+
+|Pod priority class value|Shutdown period|
+|------------------------|---------------|
+| 100000                 |10 seconds     |
+| 10000                  |180 seconds    |
+| 1000                   |120 seconds    |
+| 0                      |60 seconds     |
+
+The corresponding kubelet config YAML configuration would be:
+
+```yaml
+shutdownGracePeriodByPodPriority:
+  - priority: 100000
+    shutdownGracePeriodSeconds: 10
+  - priority: 10000
+    shutdownGracePeriodSeconds: 180
+  - priority: 1000
+    shutdownGracePeriodSeconds: 120
+  - priority: 0
+    shutdownGracePeriodSeconds: 60
+```
+
+The above table implies that any pod with priority value >= 100000 will get
+just 10 seconds to stop, any pod with value >= 10000 and < 100000 will get 180
+seconds to stop, any pod with value >= 1000 and < 10000 will get 120 seconds to stop.
+Finally, all other pods will get 60 seconds to stop.
+
+One doesn't have to specify values corresponding to all of the classes. For
+example, you could instead use these settings:
+
+|Pod priority class value|Shutdown period|
+|------------------------|---------------|
+| 100000                 |300 seconds    |
+| 1000                   |120 seconds    |
+| 0                      |60 seconds     |
+
+
+In the above case, the pods with custom-class-b will go into the same bucket
+as custom-class-c for shutdown.
+
+If there are no pods in a particular range, then the kubelet does not wait
+for pods in that priority range. Instead, the kubelet immediately skips to the
+next priority class value range.
+
+If this feature is enabled and no configuration is provided, then no ordering
+action will be taken.
+
+Using this feature, requires enabling the
+`GracefulNodeShutdownBasedOnPodPriority` feature gate, and setting the kubelet
+config's `ShutdownGracePeriodByPodPriority` to the desired configuration
+containing the pod priority class values and their respective shutdown periods.
+
 ## Swap memory management {#swap-memory}
 
 {{< feature-state state="alpha" for_k8s_version="v1.22" >}}

From 4a7a977901b668a069ec573d36b6ac60fbbeb6f9 Mon Sep 17 00:00:00 2001
From: Guneetconvent2002 <itsguneetsingh@gmail.com>
Date: Mon, 13 Sep 2021 17:59:53 +0530
Subject: [PATCH 58/68] Fix headings for well-known labels annotations and
 taints

Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../reference/labels-annotations-taints.md     | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md
index e2fc2b317e941..325bfc2d9feed 100644
--- a/content/en/docs/reference/labels-annotations-taints.md
+++ b/content/en/docs/reference/labels-annotations-taints.md
@@ -427,8 +427,18 @@ or updating objects that contain Pod templates, such as Deployments, Jobs, State
 See [Enforcing Pod Security at the Namespace Level](/docs/concepts/security/pod-security-admission)
 for more information.
 
-## seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io/[NAME] (deprecated)
+## seccomp.security.alpha.kubernetes.io/pod (deprecated) {#seccomp-security-alpha-kubernetes-io-pod}
 
-The seccomp annotations have been deprecated since Kubernetes v1.19 and will
-become non-functional in v1.25. Please use the `seccompProfile` of the
-`SecurityContext` instead.
\ No newline at end of file
+This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25.
+To specify security settings for a Pod, include the `securityContext` field in the Pod specification.
+The [`securityContext`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context) field within a Pod's `.spec` defines pod-level security attributes.
+When you [specify the security context for a Pod](/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod),
+the settings you specify apply to all containers in that Pod.
+
+## container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io}
+
+This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25.
+The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes
+you through the steps you follow to apply a seccomp profile to a Pod or to one of
+its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes,
+based on setting `securityContext` within the Pod's `.spec`.
\ No newline at end of file

From 87f371ac8d67606be55fd6cbf6643b42e4769b66 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Wed, 1 Dec 2021 23:27:21 +0000
Subject: [PATCH 59/68] Fix typo

---
 .../reference/command-line-tools-reference/feature-gates.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 17e28a42fe778..2f788cae34cb0 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -792,7 +792,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
   and gracefully terminate pods running on the node. See
   [Graceful Node Shutdown](/docs/concepts/architecture/nodes/#graceful-node-shutdown)
   for more details.
-- `GRPCContainerProbe`: Enables gPRC probe method for {Liveness,Readiness,Startup}Probe. See [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe).
+- `GRPCContainerProbe`: Enables the gRPC probe method for {Liveness,Readiness,Startup}Probe. See [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe).
 - `HPAContainerMetrics`: Enable the `HorizontalPodAutoscaler` to scale based on
   metrics from individual containers in target pods.
 - `HPAScaleToZero`: Enables setting `minReplicas` to 0 for `HorizontalPodAutoscaler`

From b90d125e1cd5cd78f75945f1d2956b268cc6542b Mon Sep 17 00:00:00 2001
From: Brandon Smith <BRASMITH@MICROSOFT.COM>
Date: Thu, 2 Dec 2021 09:45:34 -0800
Subject: [PATCH 60/68] kublet -> kubelet (#30700)

---
 .../tasks/configure-pod-container/create-hostprocess-pod.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
index 0c33c79552462..e989aa868f6ef 100644
--- a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
+++ b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
@@ -45,7 +45,7 @@ privileges needed by Windows nodes.
 
 ## {{% heading "prerequisites" %}}% version-check %}}
 
-In 1.23 the HostProcess container feature is enabled by default. The kublet will
+In 1.23 the HostProcess container feature is enabled by default. The kubelet will
 communicate with containerd directly by passing the hostprocess flag via CRI. You can use the
 latest version of containerd (v1.6+) to run HostProcess containers.
 [How to install containerd.](/docs/setup/production-environment/container-runtimes/#containerd)

From d09282b3f023b390f133f6cb7c6d5f3adfa2a67c Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Wed, 1 Dec 2021 17:18:37 +0000
Subject: [PATCH 61/68] Tweak FlexVolume deprecation text

---
 .../concepts/storage/persistent-volumes.md    | 24 +++++++++----------
 content/en/docs/concepts/storage/volumes.md   | 21 +++++++++-------
 2 files changed, 24 insertions(+), 21 deletions(-)

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 619dbc8405939..ea9538b20ee2b 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -221,19 +221,19 @@ to `Retain`, including cases where you are reusing an existing PV.
 
 {{< feature-state for_k8s_version="v1.11" state="beta" >}}
 
-Support for expanding PersistentVolumeClaims (PVCs) is now enabled by default. You can expand
+Support for expanding PersistentVolumeClaims (PVCs) is enabled by default. You can expand
 the following types of volumes:
 
-* gcePersistentDisk
+* azureDisk
+* azureFile
 * awsElasticBlockStore
-* Cinder
+* cinder (deprecated)
+* {{< glossary_tooltip text="csi" term_id="csi" >}}
+* flexVolume (deprecated)
+* gcePersistentDisk
 * glusterfs
 * rbd
-* Azure File
-* Azure Disk
-* Portworx
-* FlexVolumes
-* {{< glossary_tooltip text="CSI" term_id="csi" >}}
+* portworxVolume
 
 You can only expand a PVC if its storage class's `allowVolumeExpansion` field is set to true.
 
@@ -270,8 +270,8 @@ When a volume contains a file system, the file system is only resized when a new
 the PersistentVolumeClaim in `ReadWrite` mode. File system expansion is either done when a Pod is starting up
 or when a Pod is running and the underlying file system supports online expansion.
 
-FlexVolumes allow resize if the driver is set with the `RequiresFSResize` capability to `true`.
-The FlexVolume can be resized on Pod restart.
+FlexVolumes (deprecated since Kubernetes v1.23) allow resize if the driver is configured with the
+`RequiresFSResize` capability to `true`. The FlexVolume can be resized on Pod restart.
 
 #### Resizing an in-use PersistentVolumeClaim
 
@@ -362,10 +362,10 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
 
 The following types of PersistentVolume are deprecated. This means that support is still available but will be removed in a future Kubernetes release.
 
-* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume
-  (**deprecated** in v1.23)
 * [`cinder`](/docs/concepts/storage/volumes/#cinder) - Cinder (OpenStack block storage)
   (**deprecated** in v1.18)
+* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume
+  (**deprecated** in v1.23)
 * [`flocker`](/docs/concepts/storage/volumes/#flocker) - Flocker storage
   (**deprecated** in v1.22)
 * [`quobyte`](/docs/concepts/storage/volumes/#quobyte) - Quobyte volume
diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 792ceae69bd34..7a0be7e524923 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -1155,8 +1155,7 @@ To learn about requesting space using a resource specification, see
 ## Out-of-tree volume plugins
 
 The out-of-tree volume plugins include
-{{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} (CSI)
-and FlexVolume. These plugins enable storage vendors to create custom storage plugins
+{{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} (CSI), and also FlexVolume (which is deprecated). These plugins enable storage vendors to create custom storage plugins
 without adding their plugin source code to the Kubernetes repository.
 
 Previously, all volume plugins were "in-tree". The "in-tree" plugins were built, linked, compiled,
@@ -1289,16 +1288,20 @@ are listed in [Types of Volumes](#volume-types).
 
 ### flexVolume
 
-FlexVolume is an out-of-tree plugin interface that has existed in Kubernetes
-since version 1.2 (before CSI). It uses an exec-based model to interface with
-drivers. The FlexVolume driver binaries must be installed in a pre-defined volume
-plugin path on each node and in some cases the control plane nodes as well.
+{{< feature-state for_k8s_version="v1.23" state="deprecated" >}}
 
-Pods interact with FlexVolume drivers through the `flexvolume` in-tree volume plugin.
-For more details, see the [FlexVolume](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md) examples.
+FlexVolume is an out-of-tree plugin interface that uses an exec-based model to interface
+with storage drivers. The FlexVolume driver binaries must be installed in a pre-defined
+volume plugin path on each node and in some cases the control plane nodes as well.
+
+Pods interact with FlexVolume drivers through the `flexVolume` in-tree volume plugin.
+For more details, see the FlexVolume [README](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md#readme) document.
 
 {{< note >}}
-FlexVolume is deprecated starting v1.23. Out-of-tree CSI driver is the recommended way to write volume driver in Kubernetes. Maintainers of FlexVolume driver should implement a CSI Driver and move users of FlexVolume to CSI. Users of FlexVolume should move their workloads to CSI Driver.
+FlexVolume is deprecated. Using an out-of-tree CSI driver is the recommended way to integrate external storage with Kubernetes.
+
+Maintainers of FlexVolume driver should implement a CSI Driver and help to migrate users of FlexVolume drivers to CSI.
+Users of FlexVolume should move their workloads to use the equivalent CSI Driver.
 {{< /note >}}
 
 ## Mount propagation

From 8a0f330654ed500520f4c34e145668dcff1ede24 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Wed, 1 Dec 2021 23:50:18 +0000
Subject: [PATCH 62/68] Improve documentation for container probes

- mention gRPC probes in concept page
- revise explanation of gRPC probes in task page
- general tidying
---
 .../concepts/workloads/pods/pod-lifecycle.md  | 112 +++++++++++-------
 ...igure-liveness-readiness-startup-probes.md |  52 ++++----
 2 files changed, 99 insertions(+), 65 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index 75e4a0ba34e70..5d75bba37d66d 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -233,57 +233,87 @@ When a Pod's containers are Ready but at least one custom condition is missing o
 
 ## Container probes
 
-A [Probe](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#probe-v1-core) is a diagnostic
+A _probe_ is a diagnostic
 performed periodically by the
 [kubelet](/docs/reference/command-line-tools-reference/kubelet/)
-on a Container. To perform a diagnostic,
-the kubelet calls a
-[Handler](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#handler-v1-core) implemented by
-the container. There are three types of handlers:
+on a container. To perform a diagnostic,
+the kubelet either executes code within the container, or makes
+a network request.
 
-* [ExecAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#execaction-v1-core):
-  Executes a specified command inside the container. The diagnostic
-  is considered successful if the command exits with a status code of 0.
+### Check mechanisms {#probe-check-methods}
+
+There are four different ways to check a container using a probe.
+Each probe must define exactly one of these four mechanisms:
 
-* [TCPSocketAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#tcpsocketaction-v1-core):
-  Performs a TCP check against the Pod's IP address on
-  a specified port. The diagnostic is considered successful if the port is open.
+`exec`
+: Executes a specified command inside the container. The diagnostic
+  is considered successful if the command exits with a status code of 0.
 
-* [HTTPGetAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#httpgetaction-v1-core):
-  Performs an HTTP `GET` request against the Pod's IP
-  address on a specified port and path. The diagnostic is considered successful
-  if the response has a status code greater than or equal to 200 and less than 400.
+`grpc`
+: Performs a remote procedure call using [gRPC](https://grpc.io/).
+  The target should implement
+  [gRPC health checks](https://grpc.io/grpc/core/md_doc_health-checking.html).
+  The diagnostic is considered successful if the `status`
+  of the response is `SERVING`.  
+  gRPC probes are an alpha feature and are only available if you
+  enable the `GRPCContainerProbe`
+  [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
+
+`httpGet`
+: Performs an HTTP `GET` request against the Pod's IP
+  address on a specified port and path. The diagnostic is
+  considered successful if the response has a status code
+  greater than or equal to 200 and less than 400.
+
+`tcpSocket`
+: Performs a TCP check against the Pod's IP address on
+  a specified port. The diagnostic is considered successful if
+  the port is open. If the remote system (the container) closes
+  the connection immediately after it opens, this counts as healthy.
+
+### Probe outcome
 
 Each probe has one of three results:
 
-* `Success`: The container passed the diagnostic.
-* `Failure`: The container failed the diagnostic.
-* `Unknown`: The diagnostic failed, so no action should be taken.
+`Success`
+: The container passed the diagnostic.
 
-The kubelet can optionally perform and react to three kinds of probes on running
-containers:
+`Failure`
+: The container failed the diagnostic.
+
+`Unknown`
+: The diagnostic failed (no action should be taken, and the kubelet
+  will make further checks).
 
-* `livenessProbe`: Indicates whether the container is running. If
-   the liveness probe fails, the kubelet kills the container, and the container
-   is subjected to its [restart policy](#restart-policy). If a Container does not
-   provide a liveness probe, the default state is `Success`.
+### Types of probe
 
-* `readinessProbe`: Indicates whether the container is ready to respond to requests.
-   If the readiness probe fails, the endpoints controller removes the Pod's IP
-   address from the endpoints of all Services that match the Pod. The default
-   state of readiness before the initial delay is `Failure`. If a Container does
-   not provide a readiness probe, the default state is `Success`.
+The kubelet can optionally perform and react to three kinds of probes on running
+containers:
 
-* `startupProbe`: Indicates whether the application within the container is started.
-   All other probes are disabled if a startup probe is provided, until it succeeds.
-   If the startup probe fails, the kubelet kills the container, and the container
-   is subjected to its [restart policy](#restart-policy). If a Container does not
-   provide a startup probe, the default state is `Success`.
+`livenessProbe`
+: Indicates whether the container is running. If
+  the liveness probe fails, the kubelet kills the container, and the container
+  is subjected to its [restart policy](#restart-policy). If a container does not
+  provide a liveness probe, the default state is `Success`.
+
+`readinessProbe`
+: Indicates whether the container is ready to respond to requests.
+  If the readiness probe fails, the endpoints controller removes the Pod's IP
+  address from the endpoints of all Services that match the Pod. The default
+  state of readiness before the initial delay is `Failure`. If a container does
+  not provide a readiness probe, the default state is `Success`.
+
+`startupProbe`
+: Indicates whether the application within the container is started.
+  All other probes are disabled if a startup probe is provided, until it succeeds.
+  If the startup probe fails, the kubelet kills the container, and the container
+ is subjected to its [restart policy](#restart-policy). If a container does not
+  provide a startup probe, the default state is `Success`.
 
 For more information about how to set up a liveness, readiness, or startup probe,
 see [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).
 
-### When should you use a liveness probe?
+#### When should you use a liveness probe?
 
 {{< feature-state for_k8s_version="v1.0" state="stable" >}}
 
@@ -295,7 +325,7 @@ with the Pod's `restartPolicy`.
 If you'd like your container to be killed and restarted if a probe fails, then
 specify a liveness probe, and specify a `restartPolicy` of Always or OnFailure.
 
-### When should you use a readiness probe?
+#### When should you use a readiness probe?
 
 {{< feature-state for_k8s_version="v1.0" state="stable" >}}
 
@@ -329,7 +359,7 @@ The Pod remains in the unready state while it waits for the containers in the Po
 to stop.
 {{< /note >}}
 
-### When should you use a startup probe?
+#### When should you use a startup probe?
 
 {{< feature-state for_k8s_version="v1.20" state="stable" >}}
 
@@ -451,13 +481,13 @@ This avoids a resource leak as Pods are created and terminated over time.
 ## {{% heading "whatsnext" %}}
 
 * Get hands-on experience
-  [attaching handlers to Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/).
+  [attaching handlers to container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/).
 
 * Get hands-on experience
   [configuring Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).
 
 * Learn more about [container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/).
 
-* For detailed information about Pod / Container status in the API, see [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core)
-and
-[ContainerStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerstatus-v1-core).
+* For detailed information about Pod and container status in the API, see
+  the API reference documentation covering
+  [`.status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus) for Pod.
diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index 2ef2b1368c06f..155378730185b 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -226,51 +226,56 @@ kubectl describe pod goproxy
 
 If your application implements [gRPC Health Checking Protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md),
 kubelet can be configured to use it for application liveness checks.
+You must enable the `GRPCContainerProbe`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+in order to configure checks that rely on gRPC.
+
+Here is an example manifest:
 
 {{< codenew file="pods/probe/grpc-liveness.yaml">}}
 
 To use a gRPC probe, `port` must be configured. If the health endpoint is configured
-on a non-default service, `service` must be configured.
+on a non-default service, you must also specify the `service`.
 
 {{< note >}}
 Unlike HTTP and TCP probes, named ports cannot be used and custom host cannot be configured.
 {{< /note >}}
 
-Configuration problems (e.g. incorrect port and service, unimplemented health checking protocol)
+Configuration problems (for example: incorrect port and service, unimplemented health checking protocol)
 are considered a probe failure, similar to HTTP and TCP probes.
 
-Before Kubernetes 1.23, gRPC health probes were often implemented using [grpc-health-probe](https://github.com/grpc-ecosystem/grpc-health-probe/),
-as described in the blog post [Health checking gRPC servers on Kubernetes](/blog/2018/10/01/health-checking-grpc-servers-on-kubernetes/).
-The built-in gRPC probes behavior is similar to one implemented by grpc-health-probe.
-When migrating from grpc-health-probe to built-in probes, remember the following differences:
-
-- Built-in probes will run against pod IP, unlike grpc-health-probe that often runs against `127.0.0.1`.
-  Be sure to configure your gRPC endpoint to listen for pod IP address.
-- Built-in probes do not currently support any authentication parameters (like `-tls`).
-- There are no error codes in built-in probes. All errors are considered as probe failures.
-- If `ExecProbeTimeout` feature gate is set to `false`, grpc-health-probe will NOT
-  respect `timeoutSeconds` setting (which defaults to 1s),
-  while built-in probe will fail on timeout.
-
 To try the gRPC liveness check, create a Pod using the command below.
-In the example below, etcd pod is configured to use gRPC liveness probe.
-
+In the example below, the etcd pod is configured to use gRPC liveness probe.
 
 ```shell
 kubectl apply -f https://k8s.io/examples/pods/probe/content/en/examples/pods/probe/grpc-liveness.yaml
 ```
 
-After 15 seconds, view Pod events to verify that the liveness probes has not failed:
+After 15 seconds, view Pod events to verify that the liveness check has not failed:
 
 ```shell
 kubectl describe pod etcd-with-grpc
 ```
 
+Before Kubernetes 1.23, gRPC health probes were often implemented using [grpc-health-probe](https://github.com/grpc-ecosystem/grpc-health-probe/),
+as described in the blog post [Health checking gRPC servers on Kubernetes](/blog/2018/10/01/health-checking-grpc-servers-on-kubernetes/).
+The built-in gRPC probes behavior is similar to one implemented by grpc-health-probe.
+When migrating from grpc-health-probe to built-in probes, remember the following differences:
+
+- Built-in probes run against the pod IP address, unlike grpc-health-probe that often runs against `127.0.0.1`.
+  Be sure to configure your gRPC endpoint to listen on the Pod's IP address.
+- Built-in probes do not support any authentication parameters (like `-tls`).
+- There are no error codes for built-in probes. All errors are considered as probe failures.
+- If `ExecProbeTimeout` feature gate is set to `false`, grpc-health-probe does **not** respect the `timeoutSeconds` setting (which defaults to 1s),
+  while built-in probe would fail on timeout.
+
 ## Use a named port
 
 You can use a named
-[ContainerPort](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerport-v1-core)
-for HTTP and TCP probes. Note, gRPC probe does not support named port.
+[`port`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#ports)
+for HTTP and TCP probes. (gRPC probes do not support named ports).
+
+For example:
 
 ```yaml
 ports:
@@ -533,12 +538,11 @@ It will be rejected by the API server.
 
 ## {{% heading "whatsnext" %}}
 
-
 * Learn more about
 [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
 
 You can also read the API references for:
 
-* [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
-* [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core)
-* [Probe](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#probe-v1-core)
+* [Pod](/docs/reference/kubernetes-api/workload-resources/pod-v1/), and specifically:
+  * [container(s)](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container)
+  * [probe(s)](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Probe)

From e1bf8f22b24413038dde4327c7a766676beba3b6 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Tue, 23 Nov 2021 17:18:57 +0000
Subject: [PATCH 63/68] Improve docs for HorizontalPodAutoscaler

Co-authored-by: Chris Negus <cnegus@redhat.com>
---
 .../horizontal-pod-autoscale-walkthrough.md   | 160 ++++++----
 .../horizontal-pod-autoscale.md               | 288 ++++++++++--------
 2 files changed, 261 insertions(+), 187 deletions(-)

diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
index f5582b9416a0d..02018745d406b 100644
--- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
@@ -4,42 +4,59 @@ reviewers:
 - jszczepkowski
 - justinsb
 - directxman12
-title: Horizontal Pod Autoscaler Walkthrough
+title: HorizontalPodAutoscaler Walkthrough
 content_type: task
 weight: 100
+min-kubernetes-server-version: 1.23
 ---
 
 <!-- overview -->
 
-Horizontal Pod Autoscaler automatically scales the number of Pods
-in a replication controller, deployment, replica set or stateful set based on observed CPU utilization
-(or, with beta support, on some other, application-provided metrics).
+A [HorizontalPodAutoscaler](/docs/tasks/run-application/horizontal-pod-autoscale/)
+(HPA for short)
+automatically updates a workload resource (such as
+a {{< glossary_tooltip text="Deployment" term_id="deployment" >}} or
+{{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}}), with the
+aim of automatically scaling the workload to match demand.
 
-This document walks you through an example of enabling Horizontal Pod Autoscaler for the php-apache server.
-For more information on how Horizontal Pod Autoscaler behaves, see the
-[Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscale/).
+Horizontal scaling means that the response to increased load is to deploy more
+{{< glossary_tooltip text="Pods" term_id="pod" >}}.
+This is different from _vertical_ scaling, which for Kubernetes would mean
+assigning more resources (for example: memory or CPU) to the Pods that are already
+running for the workload.
+
+If the load decreases, and the number of Pods is above the configured minimum,
+the HorizontalPodAutoscaler instructs the workload resource (the Deployment, StatefulSet,
+or other similar resource) to scale back down.
+
+This document walks you through an example of enabling HorizontalPodAutoscaler to
+automatically manage scale for an example web app. This example workload is Apache
+httpd running some PHP code.
 
 ## {{% heading "prerequisites" %}}
 
-This example requires a running Kubernetes cluster and kubectl, version 1.2 or later.
-[Metrics server](https://github.com/kubernetes-sigs/metrics-server) monitoring needs to be deployed
-in the cluster to provide metrics through the [Metrics API](https://github.com/kubernetes/metrics).
-Horizontal Pod Autoscaler uses this API to collect metrics. To learn how to deploy the metrics-server,
-see the [metrics-server documentation](https://github.com/kubernetes-sigs/metrics-server#deployment).
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} If you're running an older
+release of Kubernetes, refer to the version of the documentation for that release (see
+[available documentation versions](/docs/home/supported-doc-versions/).
+
+To follow this walkthrough, you also need to use a cluster that has a
+[Metrics Server](https://github.com/kubernetes-sigs/metrics-server#readme) deployed and configured.
+The Kubernetes Metrics Server collects resource metrics from
+the {{<glossary_tooltip term_id="kubelet" text="kubelets">}} in your cluster, and exposes those metrics
+through the [Kubernetes API](/docs/concepts/overview/kubernetes-api/),
+using an [APIService](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) to add
+new kinds of resource that represent metric readings.
 
-To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a
-Kubernetes cluster and kubectl at version 1.6 or later. To make use of custom metrics, your cluster
-must be able to communicate with the API server providing the custom Metrics API.
-Finally, to use metrics not related to any Kubernetes object you must have a
-Kubernetes cluster at version 1.10 or later, and you must be able to communicate
-with the API server that provides the external Metrics API.
-See the [Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-custom-metrics) for more details.
+To learn how to deploy the Metrics Server, see the
+[metrics-server documentation](https://github.com/kubernetes-sigs/metrics-server#deployment).
 
 <!-- steps -->
 
 ## Run and expose php-apache server
 
-To demonstrate Horizontal Pod Autoscaler we will use a custom docker image based on the php-apache image. The Dockerfile has the following content:
+To demonstrate a HorizontalPodAutoscaler, you will first make a custom container image that uses
+the `php-apache` image from Docker Hub as its starting point. The `Dockerfile` is ready-made for you,
+and has the following content:
 
 ```dockerfile
 FROM php:5-apache
@@ -47,7 +64,8 @@ COPY index.php /var/www/html/index.php
 RUN chmod a+rx index.php
 ```
 
-It defines an index.php page which performs some CPU intensive computations:
+This code defines a simple `index.php` page that performs some CPU intensive computations,
+in order to simulate load in your cluster.
 
 ```php
 <?php
@@ -59,12 +77,13 @@ It defines an index.php page which performs some CPU intensive computations:
 ?>
 ```
 
-First, we will start a deployment running the image and expose it as a service
-using the following configuration:
+Once you have made that container image, start a Deployment that runs a container using the
+image you made, and expose it as a {{< glossary_tooltip term_id="service">}}
+using the following manifest:
 
 {{< codenew file="application/php-apache.yaml" >}}
 
-Run the following command:
+To do so, run the following command:
 
 ```shell
 kubectl apply -f https://k8s.io/examples/application/php-apache.yaml
@@ -75,16 +94,27 @@ deployment.apps/php-apache created
 service/php-apache created
 ```
 
-## Create Horizontal Pod Autoscaler
+## Create the HorizontalPodAutoscaler {#create-horizontal-pod-autoscaler}
+
+Now that the server is running, create the autoscaler using `kubectl`. There is
+[`kubectl autoscale`](/docs/reference/generated/kubectl/kubectl-commands#autoscale) subcommand,
+part of `kubectl`, that helps you do this.
+
+You will shortly run a command that creates a HorizontalPodAutoscaler that maintains
+between 1 and 10 replicas of the Pods controlled by the php-apache Deployment that
+you created in the first step of these instructions.
+
+Roughly speaking, the HPA {{<glossary_tooltip text="controller" term_id="controller">}} will increase and decrease
+the number of replicas (by updating the Deployment) to maintain an average CPU utilization across all Pods of 50%.
+The Deployment then updates the ReplicaSet - this is part of how all Deployments work in Kubernetes -
+and then the ReplicaSet either adds or removes Pods based on the change to its `.spec`.
 
-Now that the server is running, we will create the autoscaler using
-[kubectl autoscale](/docs/reference/generated/kubectl/kubectl-commands#autoscale).
-The following command will create a Horizontal Pod Autoscaler that maintains between 1 and 10 replicas of the Pods
-controlled by the php-apache deployment we created in the first step of these instructions.
-Roughly speaking, HPA will increase and decrease the number of replicas
-(via the deployment) to maintain an average CPU utilization across all Pods of 50%.
 Since each pod requests 200 milli-cores by `kubectl run`, this means an average CPU usage of 100 milli-cores.
-See [here](/docs/tasks/run-application/horizontal-pod-autoscale/#algorithm-details) for more details on the algorithm.
+See [Algorithm details](/docs/tasks/run-application/horizontal-pod-autoscale/#algorithm-details) for more details
+on the algorithm.
+
+
+Create the HorizontalPodAutoscaler:
 
 ```shell
 kubectl autoscale deployment php-apache --cpu-percent=50 --min=1 --max=10
@@ -94,47 +124,64 @@ kubectl autoscale deployment php-apache --cpu-percent=50 --min=1 --max=10
 horizontalpodautoscaler.autoscaling/php-apache autoscaled
 ```
 
-We may check the current status of autoscaler by running:
+You can check the current status of the newly-made HorizontalPodAutoscaler, by running:
 
 ```shell
+# You can use "hpa" or "horizontalpodautoscaler"; either name works OK.
 kubectl get hpa
 ```
 
+The output is similar to:
 ```
 NAME         REFERENCE                     TARGET    MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   0% / 50%  1         10        1          18s
 ```
 
-Please note that the current CPU consumption is 0% as we are not sending any requests to the server
-(the ``TARGET`` column shows the average across all the pods controlled by the corresponding deployment).
+(if you see other HorizontalPodAutoscalers with different names, that means they already existed,
+and isn't usually a problem).
+
+Please note that the current CPU consumption is 0% as there are no clients sending requests to the server
+(the ``TARGET`` column shows the average across all the Pods controlled by the corresponding deployment).
 
-## Increase load
+## Increase the load {#increase-load}
 
-Now, we will see how the autoscaler reacts to increased load.
-We will start a container, and send an infinite loop of queries to the php-apache service (please run it in a different terminal):
+Next, see how the autoscaler reacts to increased load.
+To do this, you'll start a different Pod to act as a client. The container within the client Pod
+runs in an infinite loop, sending queries to the php-apache service.
 
 ```shell
+# Run this in a separate terminal
+# so that the load generation continues and you can carry on with the rest of the steps
 kubectl run -i --tty load-generator --rm --image=busybox --restart=Never -- /bin/sh -c "while sleep 0.01; do wget -q -O- http://php-apache; done"
 ```
 
-Within a minute or so, we should see the higher CPU load by executing:
-
+Now run:
 ```shell
-kubectl get hpa
+# type Ctrl+C to end the watch when you're ready
+kubectl get hpa php-apache --watch
 ```
 
+Within a minute or so, you should see the higher CPU load; for example:
+
 ```
 NAME         REFERENCE                     TARGET      MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   305% / 50%  1         10        1          3m
 ```
 
+and then, more replicas. For example:
+```
+NAME         REFERENCE                     TARGET      MINPODS   MAXPODS   REPLICAS   AGE
+php-apache   Deployment/php-apache/scale   305% / 50%  1         10        7          3m
+```
+
 Here, CPU consumption has increased to 305% of the request.
-As a result, the deployment was resized to 7 replicas:
+As a result, the Deployment was resized to 7 replicas:
 
 ```shell
 kubectl get deployment php-apache
 ```
 
+You should see the replica count matching the figure from the HorizontalPodAutoscaler
 ```
 NAME         READY   UP-TO-DATE   AVAILABLE   AGE
 php-apache   7/7      7           7           19m
@@ -146,24 +193,29 @@ of load is not controlled in any way it may happen that the final number of repl
 will differ from this example.
 {{< /note >}}
 
-## Stop load
+## Stop generating load {#stop-load}
 
-We will finish our example by stopping the user load.
+To finish the example, stop sending the load.
 
-In the terminal where we created the container with `busybox` image, terminate
+In the terminal where you created the Pod that runs a `busybox` image, terminate
 the load generation by typing `<Ctrl> + C`.
 
-Then we will verify the result state (after a minute or so):
+Then verify the result state (after a minute or so):
 
 ```shell
-kubectl get hpa
+# type Ctrl+C to end the watch when you're ready
+kubectl get hpa php-apache --watch
 ```
 
+The output is similar to:
+
 ```
 NAME         REFERENCE                     TARGET       MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   0% / 50%     1         10        1          11m
 ```
 
+and the Deployment also shows that it has scaled down:
+
 ```shell
 kubectl get deployment php-apache
 ```
@@ -173,11 +225,9 @@ NAME         READY   UP-TO-DATE   AVAILABLE   AGE
 php-apache   1/1     1            1           27m
 ```
 
-Here CPU utilization dropped to 0, and so HPA autoscaled the number of replicas back down to 1.
+Once CPU utilization dropped to 0, the HPA automatically scaled the number of replicas back down to 1.
 
-{{< note >}}
 Autoscaling the replicas may take a few minutes.
-{{< /note >}}
 
 <!-- discussion -->
 
@@ -444,7 +494,7 @@ Conditions:
 Events:
 ```
 
-For this HorizontalPodAutoscaler, we can see several conditions in a healthy state.  The first,
+For this HorizontalPodAutoscaler, you can see several conditions in a healthy state.  The first,
 `AbleToScale`, indicates whether or not the HPA is able to fetch and update scales, as well as
 whether or not any backoff-related conditions would prevent scaling.  The second, `ScalingActive`,
 indicates whether or not the HPA is enabled (i.e. the replica count of the target is not zero) and
@@ -454,7 +504,7 @@ was capped by the maximum or minimum of the HorizontalPodAutoscaler.  This is an
 you may wish to raise or lower the minimum or maximum replica count constraints on your
 HorizontalPodAutoscaler.
 
-## Appendix: Quantities
+## Quantities
 
 All metrics in the HorizontalPodAutoscaler and metrics APIs are specified using
 a special whole-number notation known in Kubernetes as a
@@ -464,16 +514,16 @@ will return whole numbers without a suffix when possible, and will generally ret
 quantities in milli-units otherwise.  This means you might see your metric value fluctuate
 between `1` and `1500m`, or `1` and `1.5` when written in decimal notation.
 
-## Appendix: Other possible scenarios
+## Other possible scenarios
 
 ### Creating the autoscaler declaratively
 
 Instead of using `kubectl autoscale` command to create a HorizontalPodAutoscaler imperatively we
-can use the following file to create it declaratively:
+can use the following manifest to create it declaratively:
 
 {{< codenew file="application/hpa/php-apache.yaml" >}}
 
-We will create the autoscaler by executing the following command:
+Then, create the autoscaler by executing the following command:
 
 ```shell
 kubectl create -f https://k8s.io/examples/application/hpa/php-apache.yaml
diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
index 3208035a975db..acec1e6af9d81 100644
--- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
+++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
@@ -3,41 +3,59 @@ reviewers:
 - fgrzadkowski
 - jszczepkowski
 - directxman12
-title: Horizontal Pod Autoscaler
+title: Horizontal Pod Autoscaling
 feature:
   title: Horizontal scaling
   description: >
     Scale your application up and down with a simple command, with a UI, or automatically based on CPU usage.
-
 content_type: concept
 weight: 90
 ---
 
 <!-- overview -->
 
-The Horizontal Pod Autoscaler automatically scales the number of Pods
-in a replication controller, deployment, replica set or stateful set based on observed CPU utilization (or, with
-[custom metrics](https://git.k8s.io/community/contributors/design-proposals/instrumentation/custom-metrics-api.md)
-support, on some other application-provided metrics). Note that Horizontal
-Pod Autoscaling does not apply to objects that can't be scaled, for example, DaemonSets.
+In Kubernetes, a _HorizontalPodAutoscaler_ automatically updates a workload resource (such as
+a {{< glossary_tooltip text="Deployment" term_id="deployment" >}} or
+{{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}}), with the
+aim of automatically scaling the workload to match demand.
 
-The Horizontal Pod Autoscaler is implemented as a Kubernetes API resource and a controller.
-The resource determines the behavior of the controller.
-The controller periodically adjusts the number of replicas in a replication controller or deployment to match the observed metrics such as average CPU utilisation, average memory utilisation or any other custom metric to the target specified by the user.
+Horizontal scaling means that the response to increased load is to deploy more
+{{< glossary_tooltip text="Pods" term_id="pod" >}}.
+This is different from _vertical_ scaling, which for Kubernetes would mean
+assigning more resources (for example: memory or CPU) to the Pods that are already
+running for the workload.
+
+If the load decreases, and the number of Pods is above the configured minimum,
+the HorizontalPodAutoscaler instructs the workload resource (the Deployment, StatefulSet,
+or other similar resource) to scale back down.
 
+Horizontal pod autoscaling does not apply to objects that can't be scaled (for example:
+a {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}.)
 
+The HorizontalPodAutoscaler is implemented as a Kubernetes API resource and a
+{{< glossary_tooltip text="controller" term_id="controller" >}}.
+The resource determines the behavior of the controller.
+The horizontal pod autoscaling controller, running within the Kubernetes
+{{< glossary_tooltip text="control plane" term_id="control-plane" >}}, periodically adjusts the
+desired scale of its target (for example, a Deployment) to match observed metrics such as average
+CPU utilization, average memory utilization, or any other custom metric you specify.
+
+There is [walkthrough example](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) of using
+horizontal pod autoscaling.
 
 <!-- body -->
 
-## How does the Horizontal Pod Autoscaler work?
+## How does a HorizontalPodAutoscaler work?
 
-![Horizontal Pod Autoscaler diagram](/images/docs/horizontal-pod-autoscaler.svg)
+{{< figure src="/images/docs/horizontal-pod-autoscaler.svg" caption="HorizontalPodAutoscaler controls the scale of a Deployment and its ReplicaSet" class="diagram-medium">}}
 
-The Horizontal Pod Autoscaler is implemented as a control loop, with a period controlled
-by the controller manager's `--horizontal-pod-autoscaler-sync-period` flag (with a default
-value of 15 seconds).
+Kubernetes implements horizontal pod autoscaling as a control loop that runs intermittently
+(it is not a continuous process). The interval is set by the
+`--horizontal-pod-autoscaler-sync-period` parameter to the
+[`kube-controller-manager`](/docs/reference/command-line-tools-reference/kube-controller-manager/)
+(and the default interval is 15 seconds).
 
-During each period, the controller manager queries the resource utilization against the
+Once during each period, the controller manager queries the resource utilization against the
 metrics specified in each HorizontalPodAutoscaler definition.  The controller manager
 obtains the metrics from either the resource metrics API (for per-pod resource metrics),
 or the custom metrics API (for all other metrics).
@@ -45,17 +63,17 @@ or the custom metrics API (for all other metrics).
 * For per-pod resource metrics (like CPU), the controller fetches the metrics
   from the resource metrics API for each Pod targeted by the HorizontalPodAutoscaler.
   Then, if a target utilization value is set, the controller calculates the utilization
-  value as a percentage of the equivalent resource request on the containers in
-  each Pod.  If a target raw value is set, the raw metric values are used directly.
+  value as a percentage of the equivalent
+  [resource request](/docs/concepts/configuration/manage-resources-containers/#requests-and-limits)
+  on the containers in each Pod.  If a target raw value is set, the raw metric values are used directly.
   The controller then takes the mean of the utilization or the raw value (depending on the type
   of target specified) across all targeted Pods, and produces a ratio used to scale
   the number of desired replicas.
 
   Please note that if some of the Pod's containers do not have the relevant resource request set,
   CPU utilization for the Pod will not be defined and the autoscaler will
-  not take any action for that metric. See the [algorithm
-  details](#algorithm-details) section below for more information about
-  how the autoscaling algorithm works.
+  not take any action for that metric. See the [algorithm details](#algorithm-details) section below
+  for more information about how the autoscaling algorithm works.
 
 * For per-pod custom metrics, the controller functions similarly to per-pod resource metrics,
   except that it works with raw values, not utilization values.
@@ -66,20 +84,25 @@ or the custom metrics API (for all other metrics).
   version, this value can optionally be divided by the number of Pods before the
   comparison is made.
 
-The HorizontalPodAutoscaler normally fetches metrics from a series of aggregated APIs (`metrics.k8s.io`,
-`custom.metrics.k8s.io`, and `external.metrics.k8s.io`).  The `metrics.k8s.io` API is usually provided by
-metrics-server, which needs to be launched separately. For more information about resource metrics, see [Metrics Server](/docs/tasks/debug-application-cluster/resource-metrics-pipeline/#metrics-server).
+The common use for HorizontalPodAutoscaler is to configure it to fetch metrics from
+{{< glossary_tooltip text="aggregated APIs" term_id="aggregation-layer" >}}
+(`metrics.k8s.io`, `custom.metrics.k8s.io`, or `external.metrics.k8s.io`).  The `metrics.k8s.io` API is
+usually provided by an add on named Metrics Server, which needs to be launched separately.
+For more information about resource metrics, see
+[Metrics Server](/docs/tasks/debug-application-cluster/resource-metrics-pipeline/#metrics-server).
 
-See [Support for metrics APIs](#support-for-metrics-apis) for more details.
+[Support for metrics APIs](#support-for-metrics-apis) explains the stability guarantees and support status for these
+different APIs.
 
-The autoscaler accesses corresponding scalable controllers (such as replication controllers, deployments, and replica sets)
-by using the scale sub-resource. Scale is an interface that allows you to dynamically set the number of replicas and examine
-each of their current states. More details on scale sub-resource can be found
-[here](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md#scale-subresource).
+The HorizontalPodAutoscaler controller accesses corresponding workload resources that support scaling (such as Deployments
+and StatefulSet). These resources each have a subresource named `scale`, an interface that allows you to dynamically set the
+number of replicas and examine each of their current states.
+For general information about subresources in the Kubernetes API, see
+[Kubernetes API Concepts](/docs/reference/using-api/api-concepts/).
 
-### Algorithm Details
+### Algorithm details
 
-From the most basic perspective, the Horizontal Pod Autoscaler controller
+From the most basic perspective, the HorizontalPodAutoscaler controller
 operates on the ratio between desired metric value and current metric
 value:
 
@@ -89,26 +112,28 @@ desiredReplicas = ceil[currentReplicas * ( currentMetricValue / desiredMetricVal
 
 For example, if the current metric value is `200m`, and the desired value
 is `100m`, the number of replicas will be doubled, since `200.0 / 100.0 ==
-2.0` If the current value is instead `50m`, we'll halve the number of
-replicas, since `50.0 / 100.0 == 0.5`.  We'll skip scaling if the ratio is
-sufficiently close to 1.0 (within a globally-configurable tolerance, from
-the `--horizontal-pod-autoscaler-tolerance` flag, which defaults to 0.1).
+2.0` If the current value is instead `50m`, you'll halve the number of
+replicas, since `50.0 / 100.0 == 0.5`.  The control plane skips any scaling
+action if the ratio is sufficiently close to 1.0 (within a globally-configurable
+tolerance, 0.1 by default).
 
 When a `targetAverageValue` or `targetAverageUtilization` is specified,
 the `currentMetricValue` is computed by taking the average of the given
 metric across all Pods in the HorizontalPodAutoscaler's scale target.
-Before checking the tolerance and deciding on the final values, we take
-pod readiness and missing metrics into consideration, however.
 
-All Pods with a deletion timestamp set (i.e. Pods in the process of being
-shut down) and all failed Pods are discarded.
+Before checking the tolerance and deciding on the final values, the control
+plane also considers whether any metrics are missing, and how many Pods
+are [`Ready`](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions).
+All Pods with a deletion timestamp set (objects with a deletion timestamp are
+in the process of being shut down / removed) are ignored, and all failed Pods
+are discarded.
 
 If a particular Pod is missing metrics, it is set aside for later; Pods
 with missing metrics will be used to adjust the final scaling amount.
 
-When scaling on CPU, if any pod has yet to become ready (i.e. it's still
-initializing) *or* the most recent metric point for the pod was before it
-became ready, that pod is set aside as well.
+When scaling on CPU, if any pod has yet to become ready (it's still
+initializing, or possibly is unhealthy) *or* the most recent metric point for
+the pod was before it became ready, that pod is set aside as well.
 
 Due to technical constraints, the HorizontalPodAutoscaler controller
 cannot exactly determine the first time a pod becomes ready when
@@ -124,20 +149,21 @@ default is 5 minutes.
 The `currentMetricValue / desiredMetricValue` base scale ratio is then
 calculated using the remaining pods not set aside or discarded from above.
 
-If there were any missing metrics, we recompute the average more
+If there were any missing metrics, the control plane recomputes the average more
 conservatively, assuming those pods were consuming 100% of the desired
 value in case of a scale down, and 0% in case of a scale up.  This dampens
 the magnitude of any potential scale.
 
-Furthermore, if any not-yet-ready pods were present, and we would have
-scaled up without factoring in missing metrics or not-yet-ready pods, we
-conservatively assume the not-yet-ready pods are consuming 0% of the
-desired metric, further dampening the magnitude of a scale up.
+Furthermore, if any not-yet-ready pods were present, and the workload would have
+scaled up without factoring in missing metrics or not-yet-ready pods,
+the controller conservatively assumes that the not-yet-ready pods are consuming 0%
+of the desired metric, further dampening the magnitude of a scale up.
 
-After factoring in the not-yet-ready pods and missing metrics, we
-recalculate the usage ratio.  If the new ratio reverses the scale
-direction, or is within the tolerance, we skip scaling.  Otherwise, we use
-the new ratio to scale.
+After factoring in the not-yet-ready pods and missing metrics, the
+controller recalculates the usage ratio.  If the new ratio reverses the scale
+direction, or is within the tolerance, the controller doesn't take any scaling
+action. In other cases, the new ratio is used to decide any change to the
+number of Pods.
 
 Note that the *original* value for the average utilization is reported
 back via the HorizontalPodAutoscaler status, without factoring in the
@@ -173,19 +199,13 @@ When you create a HorizontalPodAutoscaler API object, make sure the name specifi
 More details about the API object can be found at
 [HorizontalPodAutoscaler Object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#horizontalpodautoscaler-v2-autoscaling).
 
+## Stability of workload scale {#flapping}
 
-## Support for Horizontal Pod Autoscaler in kubectl
-
-Horizontal Pod Autoscaler, like every API resource, is supported in a standard way by `kubectl`.
-We can create a new autoscaler using `kubectl create` command.
-We can list autoscalers by `kubectl get hpa` and get detailed description by `kubectl describe hpa`.
-Finally, we can delete an autoscaler using `kubectl delete hpa`.
+When managing the scale of a group of replicas using the HorizontalPodAutoscaler,
+it is possible that the number of replicas keeps fluctuating frequently due to the
+dynamic nature of the metrics evaluated. This is sometimes referred to as *thrashing*,
+or *flapping*. It's similar to the concept of *hysteresis* in cybernetics.
 
-In addition, there is a special `kubectl autoscale` command for creating a HorizontalPodAutoscaler object.
-For instance, executing `kubectl autoscale rs foo --min=2 --max=5 --cpu-percent=80`
-will create an autoscaler for replication set *foo*, with target CPU utilization set to `80%`
-and the number of replicas between 2 and 5.
-The detailed documentation of `kubectl autoscale` can be found [here](/docs/reference/generated/kubectl/kubectl-commands/#autoscale).
 
 
 ## Autoscaling during rolling update
@@ -202,31 +222,6 @@ If you perform a rolling update of a StatefulSet that has an autoscaled number o
 replicas, the StatefulSet directly manages its set of Pods (there is no intermediate resource
 similar to ReplicaSet).
 
-## Support for cooldown/delay
-
-When managing the scale of a group of replicas using the Horizontal Pod Autoscaler,
-it is possible that the number of replicas keeps fluctuating frequently due to the
-dynamic nature of the metrics evaluated. This is sometimes referred to as *thrashing*.
-
-Starting from v1.6, a cluster operator can mitigate this problem by tuning
-the global HPA settings exposed as flags for the `kube-controller-manager` component:
-
-Starting from v1.12, a new algorithmic update removes the need for the
-upscale delay.
-
-- `--horizontal-pod-autoscaler-downscale-stabilization`: Specifies the duration of the
-  downscale stabilization time window. Horizontal Pod Autoscaler remembers
-  the historical recommended sizes and only acts on the largest size within this time window.
-  The default value is 5 minutes (`5m0s`).
-
-{{< note >}}
-When tuning these parameter values, a cluster operator should be aware of the possible
-consequences. If the delay (cooldown) value is set too long, there could be complaints
-that the Horizontal Pod Autoscaler is not responsive to workload changes. However, if
-the delay value is set too short, the scale of the replicas set may keep thrashing as
-usual.
-{{< /note >}}
-
 ## Support for resource metrics
 
 Any HPA target can be scaled based on the resource usage of the pods in the scaling target.
@@ -255,11 +250,11 @@ a single container might be running with high usage and the HPA will not scale o
 pod usage is still within acceptable limits.
 {{< /note >}}
 
-### Container Resource Metrics
+### Container resource metrics
 
 {{< feature-state for_k8s_version="v1.20" state="alpha" >}}
 
-`HorizontalPodAutoscaler` also supports a container metric source where the HPA can track the
+The HorizontalPodAutoscaler API also supports a container metric source where the HPA can track the
 resource usage of individual containers across a set of Pods, in order to scale the target resource.
 This lets you configure scaling thresholds for the containers that matter most in a particular Pod.
 For example, if you have a web application and a logging sidecar, you can scale based on the resource
@@ -271,6 +266,7 @@ scaling. If the specified container in the metric source is not present or only
 of the pods then those pods are ignored and the recommendation is recalculated. See [Algorithm](#algorithm-details)
 for more details about the calculation. To use container resources for autoscaling define a metric
 source as follows:
+
 ```yaml
 type: ContainerResource
 containerResource:
@@ -296,30 +292,32 @@ Once you have rolled out the container name change to the workload resource, tid
 the old container name from the HPA specification.
 {{< /note >}}
 
-## Support for multiple metrics
 
-Kubernetes 1.6 adds support for scaling based on multiple metrics. You can use the `autoscaling/v2` API
-version to specify multiple metrics for the Horizontal Pod Autoscaler to scale on. Then, the Horizontal Pod
-Autoscaler controller will evaluate each metric, and propose a new scale based on that metric. The largest of the
-proposed scales will be used as the new scale.
+## Scaling on custom metrics
 
-## Support for custom metrics
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
-{{< note >}}
-Kubernetes 1.2 added alpha support for scaling based on application-specific metrics using special annotations.
-Support for these annotations was removed in Kubernetes 1.6 in favor of the new autoscaling API.  While the old method for collecting
-custom metrics is still available, these metrics will not be available for use by the Horizontal Pod Autoscaler, and the former
-annotations for specifying which custom metrics to scale on are no longer honored by the Horizontal Pod Autoscaler controller.
-{{< /note >}}
+(the `autoscaling/v2beta2` API version previously provided this ability as a beta feature)
 
-You can also use a HorizontalPodAutoscaler to change the scale of a
-workload based on custom metrics.  You can add custom metrics for the
-Horizontal Pod Autoscaler to use in the `autoscaling/v2` API.
-Kubernetes then queries the new custom metrics API to fetch the values
-of the appropriate custom metrics.
+Provided that you use the `autoscaling/v2` API version, you can configure a HorizontalPodAutoscaler
+to scale based on a custom metric (that is not built in to Kubernetes or any Kubernetes component).
+The HorizontalPodAutoscaler controller then queries for these custom metrics from the Kubernetes
+API.
 
 See [Support for metrics APIs](#support-for-metrics-apis) for the requirements.
 
+## Scaling on multiple metrics
+
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
+
+(the `autoscaling/v2beta2` API version previously provided this ability as a beta feature)
+
+Provided that you use the `autoscaling/v2` API version, you can specify multiple metrics for a
+HorizontalPodAutoscaler to scale on. Then, the HorizontalPodAutoscaler controller evaluates each metric,
+and proposes a new scale based on that metric. The HorizontalPodAutoscaler takes the maximum scale
+recommended for each metric and sets the workload to that size (provided that this isn't larger than the
+overall maximum that you configured).
+
 ## Support for metrics APIs
 
 By default, the HorizontalPodAutoscaler controller retrieves metrics from a series of APIs.  In order for it to access these
@@ -333,8 +331,7 @@ APIs, cluster administrators must ensure that:
      It can be launched as a cluster addon.
 
    * For custom metrics, this is the `custom.metrics.k8s.io` API.  It's provided by "adapter" API servers provided by metrics solution vendors.
-     Check with your metrics pipeline, or the [list of known solutions](https://github.com/kubernetes/metrics/blob/master/IMPLEMENTATIONS.md#custom-metrics-api).
-     If you would like to write your own, check out the [boilerplate](https://github.com/kubernetes-sigs/custom-metrics-apiserver) to get started.
+     Check with your metrics pipeline to see if there is a Kubernetes metrics adapter available.
 
    * For external metrics, this is the `external.metrics.k8s.io` API.  It may be provided by the custom metrics adapters provided above.
 
@@ -346,20 +343,23 @@ and [external.metrics.k8s.io](https://github.com/kubernetes/community/blob/maste
 For examples of how to use them see [the walkthrough for using custom metrics](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#autoscaling-on-multiple-metrics-and-custom-metrics)
 and [the walkthrough for using external metrics](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#autoscaling-on-metrics-not-related-to-kubernetes-objects).
 
-## Support for configurable scaling behavior
+## Configurable scaling behavior
+
+{{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
-Starting from
-[v1.18](https://github.com/kubernetes/enhancements/blob/master/keps/sig-autoscaling/853-configurable-hpa-scale-velocity/README.md)
-the `v2beta2` API (and from v1.23 the `v2` API) allows scaling
-behavior to be configured through the HPA `behavior` field. Behaviors
-are specified separately for scaling up and down in `scaleUp` or
-`scaleDown` section under the `behavior` field. A stabilization window
-can be specified for both directions which prevents the flapping of
-the number of the replicas in the scaling target. Similarly specifying
-scaling policies controls the rate of change of replicas while
-scaling.
+(the `autoscaling/v2beta2` API version previously provided this ability as a beta feature)
 
-### Scaling Policies
+If you use the `v2` HorizontalPodAutoscaler API, you can use the `behavior` field
+(see the [API reference](/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2/#HorizontalPodAutoscalerSpec))
+to configure separate scale-up and scale-down behaviors.
+You specify these behaviours by setting `scaleUp` and / or `scaleDown`
+under the `behavior` field.
+
+You can specify a _stabilization window_ that prevents [flapping](#flapping)
+the replica count for a scaling target. Scaling policies also let you controls the
+rate of change of replicas while scaling.
+
+### Scaling policies
 
 One or more scaling policies can be specified in the `behavior` section of the spec.
 When multiple policies are specified the policy which allows the highest amount of
@@ -396,21 +396,27 @@ direction. By setting the value to `Min` which would select the policy which all
 smallest change in the replica count. Setting the value to `Disabled` completely disables
 scaling in that direction.
 
-### Stabilization Window
+### Stabilization window
+
+The stabilization window is used to restrict the [flapping](#flapping) of
+replicas count when the metrics used for scaling keep fluctuating. The autoscaling algorithm
+uses this window to infer a previous desired state and avoid unwanted changes to workload
+scale.
 
-The stabilization window is used to restrict the flapping of replicas when the metrics
-used for scaling keep fluctuating. The stabilization window is used by the autoscaling
-algorithm to consider the computed desired state from the past to prevent scaling. In
-the following example the stabilization window is specified for `scaleDown`.
+For example, in the following example snippet, a stabilization window is specified for `scaleDown`.
 
 ```yaml
-scaleDown:
-  stabilizationWindowSeconds: 300
+behavior:
+  scaleDown:
+    stabilizationWindowSeconds: 300
 ```
 
 When the metrics indicate that the target should be scaled down the algorithm looks
-into previously computed desired states and uses the highest value from the specified
-interval. In above example all desired states from the past 5 minutes will be considered.
+into previously computed desired states, and uses the highest value from the specified
+interval. In the above example, all desired states from the past 5 minutes will be considered.
+
+This approximates a rolling maximum, and avoids having the scaling algorithm frequently
+remove Pods only to trigger recreating an equivalent Pod just moments later.
 
 ### Default Behavior
 
@@ -498,6 +504,18 @@ behavior:
     selectPolicy: Disabled
 ```
 
+## Support for HorizontalPodAutoscaler in kubectl
+
+HorizontalPodAutoscaler, like every API resource, is supported in a standard way by `kubectl`.
+You can create a new autoscaler using `kubectl create` command.
+You can list autoscalers by `kubectl get hpa` or get detailed description by `kubectl describe hpa`.
+Finally, you can delete an autoscaler using `kubectl delete hpa`.
+
+In addition, there is a special `kubectl autoscale` command for creating a HorizontalPodAutoscaler object.
+For instance, executing `kubectl autoscale rs foo --min=2 --max=5 --cpu-percent=80`
+will create an autoscaler for replication set *foo*, with target CPU utilization set to `80%`
+and the number of replicas between 2 and 5.
+
 ## Implicit maintenance-mode deactivation
 
 You can implicitly deactivate the HPA for a target without the
@@ -509,7 +527,13 @@ replica count or HPA's minimum replica count.
 
 ## {{% heading "whatsnext" %}}
 
+If you configure autoscaling in your cluster, you may also want to consider running a
+cluster-level autoscaler such as [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler).
+
+For more information on HorizontalPodAutoscaler:
 
-* Design documentation: [Horizontal Pod Autoscaling](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md).
-* kubectl autoscale command: [kubectl autoscale](/docs/reference/generated/kubectl/kubectl-commands/#autoscale).
-* Usage example of [Horizontal Pod Autoscaler](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/).
+* Read a [walkthrough example](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) for horizontal pod autoscaling.
+* Read documentation for [`kubectl autoscale`](/docs/reference/generated/kubectl/kubectl-commands/#autoscale).
+* If you would like to write your own custom metrics adapter, check out the
+  [boilerplate](https://github.com/kubernetes-sigs/custom-metrics-apiserver) to get started.
+* Read the [API reference](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler/) for HorizontalPodAutoscaler.

From c1af8d4c1bd5ea704765e58edd1a323f96c923cd Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Wed, 1 Dec 2021 22:33:19 +0000
Subject: [PATCH 64/68] Present scope for IngressClass params using tabs

Use tabs for the two different options that an IngressClass can use to
refer to another object, in order to specific parameters that relate to
that IngressClass:
- namespaced scope
- cluster scope (the default / historical behavior)
---
 .../concepts/services-networking/ingress.md   | 99 ++++++++++++++++---
 1 file changed, 86 insertions(+), 13 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index 5f4837fa2972f..4fb7a2c215e7a 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -219,25 +219,98 @@ of the controller that should implement the class.
 
 {{< codenew file="service/networking/external-lb.yaml" >}}
 
-IngressClass resources contain an optional parameters field. This can be used to
-reference additional implementation-specific configuration for this class.
+The `.spec.parameters` field of an IngressClass lets you reference another
+resource that provides configuration related to that IngressClass.
 
-#### Namespace-scoped parameters
+The specific type of parameters to use depends on the ingress controller
+that you specify in the `.spec.controller` field of the IngressClass.
 
+### IngressClass scope
+
+Depending on your ingress controller, you may be able to use parameters
+that you set cluster-wide, or just for one namespace.
+
+{{< tabs name="tabs_ingressclass_parameter_scope" >}}
+{{% tab name="Cluster" %}}
+The default scope for IngressClass parameters is cluster-wide.
+
+If you set the `.spec.parameters` field and don't set
+`.spec.parameters.scope`, or if you set `.spec.parameters.scope` to
+`Cluster`, then the IngressClass refers to a cluster-scoped resource.
+The `kind` (in combination the `apiGroup`) of the parameters
+refers to a cluster-scoped API (possibly a custom resource), and
+the `name` of the parameters identifies a specific cluster scoped
+resource for that API.
+
+For example:
+```yaml
+---
+apiVersion: networking.k8s.io/v1
+kind: IngressClass
+metadata:
+  name: external-lb-1
+spec:
+  controller example.com/ingress-controller
+  parameters:
+    # The parameters for this IngressClass are specified in an
+    # ClusterIngressParameter (API group k8s.example.net) named
+    # "external-config-1". This definition tells Kubernetes to
+    # look for a cluster-scoped parameter resource.
+    scope: Cluster
+    apiGroup: k8s.example.net
+    kind: ClusterIngressParameter
+    name: external-config
+```
+{{% /tab %}}
+{{% tab name="Namespaced" %}}
 {{< feature-state for_k8s_version="v1.23" state="stable" >}}
 
-`Parameters` field has a `scope` and `namespace` field that can be used to
-reference a namespace-specific resource for configuration of an Ingress class.
-`Scope` field defaults to `Cluster`, meaning, the default is cluster-scoped
-resource. Setting `Scope` to `Namespace` and setting the `Namespace` field
-will reference a parameters resource in a specific namespace:
+If you set the `.spec.parameters` field and set
+`.spec.parameters.scope` to `Namespace`, then the IngressClass refers
+to a namespaced-scoped resource. You must also set the `namespace`
+field within `.spec.parameters` to the namespace that contains
+the parameters you want to use.
 
-Namespace-scoped parameters avoid the need for a cluster-scoped CustomResourceDefinition
-for a parameters resource. This further avoids RBAC-related resources
-that would otherwise be required to grant permissions to cluster-scoped
-resources.
+The `kind` (in combination the `apiGroup`) of the parameters
+refers to a namespaced API (for example: ConfigMap), and
+the `name` of the parameters identifies a specific resource
+in the namespace you specified in `namespace`.
+
+Namespace-scoped parameters help the cluster operator delegate control over the
+configuration (for example: load balancer settings, API gateway definition)
+that is used for a workload. If you used a cluster-scoped parameter then either:
+
+- the cluster operator team needs to approve a different team's changes every
+  time there's a new configuration change being applied.
+- the cluster operator must define specific access controls, such as
+  [RBAC](/docs/reference/access-authn-authz/rbac/) roles and bindings, that let
+  the application team make changes to the cluster-scoped parameters resource.
+
+The IngressClass API itself is always cluster-scoped.
+
+Here is an example of an IngressClass that refers to parameters that are
+namespaced:
+```yaml
+---
+apiVersion: networking.k8s.io/v1
+kind: IngressClass
+metadata:
+  name: external-lb-2
+spec:
+  controller example.com/ingress-controller
+  parameters:
+    # The parameters for this IngressClass are specified in an
+    # IngressParameter (API group k8s.example.com) named "external-config",
+    # that's in the "external-configuration" configuration namespace.
+    scope: Namespace
+    apiGroup: k8s.example.com
+    kind: IngressParameter
+    namespace: external-configuration
+    name: external-config
+```
 
-{{< codenew file="service/networking/namespaced-params.yaml" >}}
+{{% /tab %}}
+{{< /tabs >}}
 
 ### Deprecated annotation
 

From 366ae6e48bb7c959cd2040000ab52e19dbbb5f86 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sun, 5 Dec 2021 22:26:49 +0000
Subject: [PATCH 65/68] Fix IngressClass tabs

---
 content/en/docs/concepts/services-networking/ingress.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index 4fb7a2c215e7a..0bcacd7e20874 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -252,14 +252,14 @@ metadata:
 spec:
   controller example.com/ingress-controller
   parameters:
-    # The parameters for this IngressClass are specified in an
+    # The parameters for this IngressClass are specified in a
     # ClusterIngressParameter (API group k8s.example.net) named
     # "external-config-1". This definition tells Kubernetes to
     # look for a cluster-scoped parameter resource.
     scope: Cluster
     apiGroup: k8s.example.net
     kind: ClusterIngressParameter
-    name: external-config
+    name: external-config-1
 ```
 {{% /tab %}}
 {{% tab name="Namespaced" %}}

From 8983d73fff36307a83df706f20c0afb57006a0b9 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Mon, 6 Dec 2021 21:07:33 +0000
Subject: [PATCH 66/68] Tidy HostProcess task page (#30762)

* Tidy HostProcess task page

* Use spaces for indentation

Tabs for indentation are less easy to work with between different
contributors. Switch to spaces.

* Fix table for HostProcess requirements
---
 .../create-hostprocess-pod.md                 | 135 ++++++++++--------
 1 file changed, 72 insertions(+), 63 deletions(-)

diff --git a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
index 9e18805cf8352..10052fd68e220 100644
--- a/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
+++ b/content/en/docs/tasks/configure-pod-container/create-hostprocess-pod.md
@@ -2,7 +2,7 @@
 title: Create a Windows HostProcess Pod
 content_type: task
 weight: 20
-min-kubernetes-server-version: 1.22
+min-kubernetes-server-version: 1.23
 ---
 
 <!-- overview -->
@@ -43,9 +43,15 @@ HostProcess containers have access to the host's network interfaces and IP addre
 privileges needed by Windows nodes.
 
 
-## {{% heading "prerequisites" %}}% version-check %}}
+## {{% heading "prerequisites" %}}
 
-In 1.23 the HostProcess container feature is enabled by default. The kubelet will
+<!-- change this when graduating to stable -->
+
+This task guide is specific to Kubernetes v{{< skew currentVersion >}}.
+If you are not running Kubernetes v{{< skew currentVersion >}}, check the documentation for
+that version of Kubernetes.
+
+In Kubernetes {{< skew currentVersion >}}, the HostProcess container feature is enabled by default. The kubelet will
 communicate with containerd directly by passing the hostprocess flag via CRI. You can use the
 latest version of containerd (v1.6+) to run HostProcess containers.
 [How to install containerd.](/docs/setup/production-environment/container-runtimes/#containerd)
@@ -64,20 +70,21 @@ documentation for more details.
 
 ## Limitations
 
+These limitations are relevant for Kubernetes v{{< skew currentVersion >}}:
+
 - HostProcess containers require containerd 1.6 or higher
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
-- As of v1.23 HostProcess pods can only contain HostProcess containers. This is a current limitation
+- HostProcess pods can only contain HostProcess containers. This is a current limitation
 of the Windows OS; non-privileged Windows containers cannot share a vNIC with the host IP namespace.
 - HostProcess containers run as a process on the host and do not have any degree of
 isolation other than resource constraints imposed on the HostProcess user account. Neither
 filesystem or Hyper-V isolation are supported for HostProcess containers.
 - Volume mounts are supported and are mounted under the container volume. See [Volume Mounts](#volume-mounts)
-- As of 1.23, a limited set of host user accounts are available for HostProcess containers by default.
 - A limited set of host user accounts are available for HostProcess containers by default.
-See [Choosing a User Account](#choosing-a-user-account).
+  See [Choosing a User Account](#choosing-a-user-account).
 - Resource limits (disk, memory, cpu count) are supported in the same fashion as processes
 on the host.
-- Both Named pipe mounts and Unix domain sockets are **not** currently supported and should instead
+- Both Named pipe mounts and Unix domain sockets are **not** supported and should instead
 be accessed via their path on the host (e.g. \\\\.\\pipe\\\*)
 
 ## HostProcess Pod configuration requirements
@@ -91,62 +98,64 @@ When running under the privileged policy, here are
 the configurations which need to be set to enable the creation of a HostProcess pod:
 
 <table>
-	<caption style="display:none">Privileged policy specification</caption>
-	<tbody>
-		<tr>
-			<td><strong>Control</strong></td>
-			<td><strong>Policy</strong></td>
-		</tr>
-		<tr>
-			<td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards">Windows HostProcess</a></td>
-			<td>
-				<p>Windows pods offer the ability to run <a href="/docs/tasks/configure-pod-container/create-hostprocess-pod">
+  <caption style="display: none">Privileged policy specification</caption>
+  <thead>
+    <tr>
+      <th>Control</th>
+      <th>Policy</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards"><tt>securityContext.windowsOptions.hostProcess</tt></a></td>
+      <td>
+        <p>Windows pods offer the ability to run <a href="/docs/tasks/configure-pod-container/create-hostprocess-pod">
         HostProcess containers</a> which enables privileged access to the Windows node. </p>
-				<p><strong>Allowed Values</strong></p>
-				<ul>
-					<li><code>true</code></li>
-				</ul>
-			</td>
-		</tr>
-		<tr>
-			<td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards">Host Networking</a></td>
-			<td>
-				<p>Will be in host network by default initially. Support 
-				to set network to a different compartment may be desirable in 
-				the future.</p>
-				<p><strong>Allowed Values</strong></p>
-				<ul>
-					<li><code>true</code></li>
-				</ul>
-			</td>
-		</tr>
+        <p><strong>Allowed Values</strong></p>
+        <ul>
+          <li><code>true</code></li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards"><tt>hostNetwork</tt></a></td>
+      <td>
+        <p>Will be in host network by default initially. Support
+        to set network to a different compartment may be desirable in
+        the future.</p>
+        <p><strong>Allowed Values</strong></p>
+        <ul>
+          <li><code>true</code></li>
+        </ul>
+      </td>
+    </tr>
     <tr>
-			<td style="white-space: nowrap"><a href="/docs/tasks/configure-pod-container/configure-runasusername/">runAsUsername</a></td>
-			<td>
-				<p>Specification of which user the HostProcess container should run as is required for the pod spec.</p>
-				<p><strong>Allowed Values</strong></p>
-				<ul>
-          			<li><code>NT AUTHORITY\SYSTEM</code></li>
-					<li><code>NT AUTHORITY\Local service</code></li>
-					<li><code>NT AUTHORITY\NetworkService</code></li>
-				</ul>
-			</td>
-		</tr>
+      <td style="white-space: nowrap"><a href="/docs/tasks/configure-pod-container/configure-runasusername/"><tt>securityContext.windowsOptions.runAsUsername</tt></a></td>
+      <td>
+        <p>Specification of which user the HostProcess container should run as is required for the pod spec.</p>
+        <p><strong>Allowed Values</strong></p>
+        <ul>
+          <li><code>NT AUTHORITY\SYSTEM</code></li>
+          <li><code>NT AUTHORITY\Local service</code></li>
+          <li><code>NT AUTHORITY\NetworkService</code></li>
+        </ul>
+      </td>
+    </tr>
     <tr>
-			<td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards">runAsNonRoot</a></td>
-			<td>
-				<p>Because HostProcess containers have privileged access to the host, the <tt>runAsNonRoot</tt> field cannot be set to true.</p>
-				<p><strong>Allowed Values</strong></p>
-				<ul>
+      <td style="white-space: nowrap"><a href="/docs/concepts/security/pod-security-standards"><tt>runAsNonRoot</tt></a></td>
+      <td>
+        <p>Because HostProcess containers have privileged access to the host, the <tt>runAsNonRoot</tt> field cannot be set to true.</p>
+        <p><strong>Allowed Values</strong></p>
+        <ul>
           <li>Undefined/Nil</li>
-					<li><code>false</code></li>
-				</ul>
-			</td>
-		</tr>
-	</tbody>
+          <li><code>false</code></li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-### Example Manifest (excerpt)
+### Example manifest (excerpt) {#manifest-example}
 
 ```yaml
 spec:
@@ -166,13 +175,13 @@ spec:
     "kubernetes.io/os": windows
 ```
 
-## Volume Mounts
+## Volume mounts
 
 HostProcess containers support the ability to mount volumes within the container volume space.
 Applications running inside the container can access volume mounts directly via relative or
-absolute paths. As of v1.23, an environment variable `$CONTAINER_SANDBOX_MOUNT_POINT` is set upon container
+absolute paths. An environment variable `$CONTAINER_SANDBOX_MOUNT_POINT` is set upon container
 creation and provides the absolute host path to the container volume. Relative paths are based
-upon the `Pod.containers.volumeMounts.mountPath` configuration.
+upon the `.spec.containers.volumeMounts.mountPath` configuration.
 
 ### Example {#volume-mount-example}
 
@@ -182,7 +191,7 @@ To access service account tokens the following path structures are supported wit
 
 `$CONTAINER_SANDBOX_MOUNT_POINT\var\run\secrets\kubernetes.io\serviceaccount\`
 
-## Resource Limits
+## Resource limits
 
 Resource limits (disk, memory, cpu count) are applied to the job and are job wide.
 For example, with a limit of 10MB set, the memory allocated for any HostProcess job object
@@ -191,9 +200,9 @@ These limits would be specified the same way they are currently for whatever orc
 or runtime is being used. The only difference is in the disk resource usage calculation
 used for resource tracking due to the difference in how HostProcess containers are bootstrapped.
 
-## Choosing a User Account
+## Choosing a user account
 
-As of 1.23, HostProcess containers support the ability to run as one of three supported Windows service accounts:
+HostProcess containers support the ability to run as one of three supported Windows service accounts:
 
 - **[LocalSystem](https://docs.microsoft.com/windows/win32/services/localsystem-account)**
 - **[LocalService](https://docs.microsoft.com/windows/win32/services/localservice-account)**

From c0e8dd526b32b2963c0e5eab20120699b6ced78c Mon Sep 17 00:00:00 2001
From: Jesse Butler <butlerjl@amazon.com>
Date: Mon, 6 Dec 2021 18:15:42 -0500
Subject: [PATCH 67/68] update config for release 1.23

---
 config.toml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/config.toml b/config.toml
index 5380a72bdff6a..c71f4fcdeafe5 100644
--- a/config.toml
+++ b/config.toml
@@ -186,30 +186,30 @@ docsbranch = "main"
 url = "https://kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.22.1"
+fullversion = "v1.22.4"
 version = "v1.22"
-githubbranch = "v1.22.1"
+githubbranch = "v1.22.4"
 docsbranch = "release-1.22"
 url = "https://v1-22.docs.kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.21.4"
+fullversion = "v1.21.7"
 version = "v1.21"
-githubbranch = "v1.21.4"
+githubbranch = "v1.21.7"
 docsbranch = "release-1.21"
 url = "https://v1-21.docs.kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.20.10"
+fullversion = "v1.20.13"
 version = "v1.20"
-githubbranch = "v1.20.10"
+githubbranch = "v1.20.13"
 docsbranch = "release-1.20"
 url = "https://v1-20.docs.kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.19.14"
+fullversion = "v1.19.16"
 version = "v1.19"
-githubbranch = "v1.19.14"
+githubbranch = "v1.19.16"
 docsbranch = "release-1.19"
 url = "https://v1-19.docs.kubernetes.io"
 

From 8506e8b1de09f658c3f806c30a59afbf0a74b965 Mon Sep 17 00:00:00 2001
From: Jesse Butler <butlerjl@amazon.com>
Date: Tue, 7 Dec 2021 16:26:34 -0500
Subject: [PATCH 68/68] Generate single-page API reference for 1.23

---
 .../generated/kubernetes-api/v1.23/index.html | 43998 ++++++++++++++++
 .../kubernetes-api/v1.23/js/navData.js        |     1 +
 2 files changed, 43999 insertions(+)
 create mode 100644 static/docs/reference/generated/kubernetes-api/v1.23/index.html
 create mode 100644 static/docs/reference/generated/kubernetes-api/v1.23/js/navData.js

diff --git a/static/docs/reference/generated/kubernetes-api/v1.23/index.html b/static/docs/reference/generated/kubernetes-api/v1.23/index.html
new file mode 100644
index 0000000000000..1d1d5e8afc12a
--- /dev/null
+++ b/static/docs/reference/generated/kubernetes-api/v1.23/index.html
@@ -0,0 +1,43998 @@
+<!DOCTYPE html>
+<HTML>
+<HEAD>
+<META charset="UTF-8">
+<TITLE>Kubernetes API Reference Docs</TITLE>
+<LINK rel="shortcut icon" href="favicon.ico" type="image/vnd.microsoft.icon">
+<LINK rel="stylesheet" href="/css/bootstrap-4.3.1.min.css">
+<LINK rel="stylesheet" href="/css/fontawesome-4.7.0.min.css" type="text/css">
+<LINK rel="stylesheet" href="/css/style_apiref.css" type="text/css">
+</HEAD>
+<BODY>
+<DIV id="wrapper" class="container-fluid">
+<DIV class="row">
+<DIV id="sidebar-wrapper" class="col-xs-4 col-sm-3 col-md-2 side-nav side-bar-nav">
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-api-overview-strong-" class="nav-item"><STRONG>Overview</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-api-groups-strong-" class="nav-item"><STRONG>API Groups</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-workloads-apis-strong-" class="nav-item"><STRONG>WORKLOADS APIS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#container-v1-core" class="nav-item">Container v1 core</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#cronjob-v1-batch" class="nav-item">CronJob v1 batch</A></LI>
+ <UL id="cronjob-v1-batch-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-cronjob-v1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-cronjob-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-cronjob-v1-batch" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-cronjob-v1-batch" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-cronjob-v1-batch" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-cronjob-v1-batch" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-cronjob-v1-batch" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-cronjob-v1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-cronjob-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-cronjob-v1-batch" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-cronjob-v1-batch" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-cronjob-v1-batch" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-cronjob-v1-batch" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-cronjob-v1-batch" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-cronjob-v1-batch" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-cronjob-v1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-cronjob-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-cronjob-v1-batch" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-cronjob-v1-batch" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-cronjob-v1-batch" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#daemonset-v1-apps" class="nav-item">DaemonSet v1 apps</A></LI>
+ <UL id="daemonset-v1-apps-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-daemonset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-daemonset-v1-apps" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-daemonset-v1-apps" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-daemonset-v1-apps" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-daemonset-v1-apps" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-daemonset-v1-apps" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-daemonset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-daemonset-v1-apps" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-daemonset-v1-apps" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-daemonset-v1-apps" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-daemonset-v1-apps" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-daemonset-v1-apps" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-daemonset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-daemonset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-daemonset-v1-apps" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-daemonset-v1-apps" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-daemonset-v1-apps" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#deployment-v1-apps" class="nav-item">Deployment v1 apps</A></LI>
+ <UL id="deployment-v1-apps-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-deployment-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-deployment-v1-apps" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-deployment-v1-apps" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-deployment-v1-apps" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-deployment-v1-apps" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-deployment-v1-apps" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-deployment-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-deployment-v1-apps" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-deployment-v1-apps" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-deployment-v1-apps" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-deployment-v1-apps" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-deployment-v1-apps" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-deployment-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-deployment-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-deployment-v1-apps" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-deployment-v1-apps" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-deployment-v1-apps" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
+   <UL id="-strong-misc-operations-deployment-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-scale-deployment-v1-apps" class="nav-item">Read Scale</A></LI>
+    <LI class="nav-level-2"><A href="#replace-scale-deployment-v1-apps" class="nav-item">Replace Scale</A></LI>
+    <LI class="nav-level-2"><A href="#patch-scale-deployment-v1-apps" class="nav-item">Patch Scale</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#job-v1-batch" class="nav-item">Job v1 batch</A></LI>
+ <UL id="job-v1-batch-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-job-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-job-v1-batch" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-job-v1-batch" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-job-v1-batch" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-job-v1-batch" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-job-v1-batch" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-job-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-job-v1-batch" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-job-v1-batch" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-job-v1-batch" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-job-v1-batch" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-job-v1-batch" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-job-v1-batch" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-job-v1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-job-v1-batch" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-job-v1-batch" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-job-v1-batch" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#pod-v1-core" class="nav-item">Pod v1 core</A></LI>
+ <UL id="pod-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-pod-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#create-eviction-pod-v1-core" class="nav-item">Create Eviction</A></LI>
+    <LI class="nav-level-2"><A href="#patch-pod-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-pod-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-pod-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-pod-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-pod-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-pod-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-pod-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-pod-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-pod-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-pod-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-pod-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-pod-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-pod-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-ephemeralcontainers-operations-pod-v1-core-strong-" class="nav-item"><STRONG>EphemeralContainers Operations</STRONG></A></LI>
+   <UL id="-strong-ephemeralcontainers-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-ephemeralcontainers-pod-v1-core" class="nav-item">Patch EphemeralContainers</A></LI>
+    <LI class="nav-level-2"><A href="#read-ephemeralcontainers-pod-v1-core" class="nav-item">Read EphemeralContainers</A></LI>
+    <LI class="nav-level-2"><A href="#replace-ephemeralcontainers-pod-v1-core" class="nav-item">Replace EphemeralContainers</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
+   <UL id="-strong-proxy-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-connect-portforward-pod-v1-core" class="nav-item">Create Connect Portforward</A></LI>
+    <LI class="nav-level-2"><A href="#create-connect-proxy-pod-v1-core" class="nav-item">Create Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#create-connect-proxy-path-pod-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-pod-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-path-pod-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-portforward-pod-v1-core" class="nav-item">Get Connect Portforward</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-pod-v1-core" class="nav-item">Get Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-path-pod-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-pod-v1-core" class="nav-item">Head Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-path-pod-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-pod-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-path-pod-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
+   <UL id="-strong-misc-operations-pod-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-log-pod-v1-core" class="nav-item">Read Log</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#replicaset-v1-apps" class="nav-item">ReplicaSet v1 apps</A></LI>
+ <UL id="replicaset-v1-apps-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-replicaset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-replicaset-v1-apps" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-replicaset-v1-apps" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-replicaset-v1-apps" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-replicaset-v1-apps" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-replicaset-v1-apps" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-replicaset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-replicaset-v1-apps" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-replicaset-v1-apps" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-replicaset-v1-apps" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-replicaset-v1-apps" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-replicaset-v1-apps" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicaset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-replicaset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-replicaset-v1-apps" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-replicaset-v1-apps" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-replicaset-v1-apps" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
+   <UL id="-strong-misc-operations-replicaset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-scale-replicaset-v1-apps" class="nav-item">Read Scale</A></LI>
+    <LI class="nav-level-2"><A href="#replace-scale-replicaset-v1-apps" class="nav-item">Replace Scale</A></LI>
+    <LI class="nav-level-2"><A href="#patch-scale-replicaset-v1-apps" class="nav-item">Patch Scale</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#replicationcontroller-v1-core" class="nav-item">ReplicationController v1 core</A></LI>
+ <UL id="replicationcontroller-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-replicationcontroller-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-replicationcontroller-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-replicationcontroller-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-replicationcontroller-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-replicationcontroller-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-replicationcontroller-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-replicationcontroller-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-replicationcontroller-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-replicationcontroller-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-replicationcontroller-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicationcontroller-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-replicationcontroller-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-replicationcontroller-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-replicationcontroller-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
+   <UL id="-strong-misc-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-scale-replicationcontroller-v1-core" class="nav-item">Read Scale</A></LI>
+    <LI class="nav-level-2"><A href="#replace-scale-replicationcontroller-v1-core" class="nav-item">Replace Scale</A></LI>
+    <LI class="nav-level-2"><A href="#patch-scale-replicationcontroller-v1-core" class="nav-item">Patch Scale</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#statefulset-v1-apps" class="nav-item">StatefulSet v1 apps</A></LI>
+ <UL id="statefulset-v1-apps-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-statefulset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-statefulset-v1-apps" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-statefulset-v1-apps" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-statefulset-v1-apps" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-statefulset-v1-apps" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-statefulset-v1-apps" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-statefulset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-statefulset-v1-apps" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-statefulset-v1-apps" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-statefulset-v1-apps" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-statefulset-v1-apps" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-statefulset-v1-apps" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-statefulset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-statefulset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-statefulset-v1-apps" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-statefulset-v1-apps" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-statefulset-v1-apps" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
+   <UL id="-strong-misc-operations-statefulset-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-scale-statefulset-v1-apps" class="nav-item">Read Scale</A></LI>
+    <LI class="nav-level-2"><A href="#replace-scale-statefulset-v1-apps" class="nav-item">Replace Scale</A></LI>
+    <LI class="nav-level-2"><A href="#patch-scale-statefulset-v1-apps" class="nav-item">Patch Scale</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-service-apis-strong-" class="nav-item"><STRONG>SERVICE APIS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpoints-v1-core" class="nav-item">Endpoints v1 core</A></LI>
+ <UL id="endpoints-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-endpoints-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-endpoints-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-endpoints-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-endpoints-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-endpoints-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-endpoints-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-endpoints-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-endpoints-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-endpoints-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-endpoints-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-endpoints-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-endpoints-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-endpoints-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-endpoints-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-endpoints-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointslice-v1-discovery-k8s-io" class="nav-item">EndpointSlice v1 discovery.k8s.io</A></LI>
+ <UL id="endpointslice-v1-discovery-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-endpointslice-v1-discovery-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-endpointslice-v1-discovery-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-endpointslice-v1-discovery-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-endpointslice-v1-discovery-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-endpointslice-v1-discovery-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-endpointslice-v1-discovery-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-endpointslice-v1-discovery-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-endpointslice-v1-discovery-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-endpointslice-v1-discovery-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-endpointslice-v1-discovery-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-endpointslice-v1-discovery-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-endpointslice-v1-discovery-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#ingress-v1-networking-k8s-io" class="nav-item">Ingress v1 networking.k8s.io</A></LI>
+ <UL id="ingress-v1-networking-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-ingress-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-ingress-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-ingress-v1-networking-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-ingress-v1-networking-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-ingress-v1-networking-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-ingress-v1-networking-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-ingress-v1-networking-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-ingress-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-ingress-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-ingress-v1-networking-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-ingress-v1-networking-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-ingress-v1-networking-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-ingress-v1-networking-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-ingress-v1-networking-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-ingress-v1-networking-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-ingress-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-ingress-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-ingress-v1-networking-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-ingress-v1-networking-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-ingress-v1-networking-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#ingressclass-v1-networking-k8s-io" class="nav-item">IngressClass v1 networking.k8s.io</A></LI>
+ <UL id="ingressclass-v1-networking-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-ingressclass-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-ingressclass-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-ingressclass-v1-networking-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-ingressclass-v1-networking-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-ingressclass-v1-networking-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-ingressclass-v1-networking-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-ingressclass-v1-networking-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-ingressclass-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-ingressclass-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-ingressclass-v1-networking-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-ingressclass-v1-networking-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-ingressclass-v1-networking-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-ingressclass-v1-networking-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#service-v1-core" class="nav-item">Service v1 core</A></LI>
+ <UL id="service-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-service-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-service-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-service-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-service-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-service-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-service-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-service-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-service-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-service-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-service-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-service-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-service-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-service-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-service-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-service-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-service-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-service-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-service-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-service-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-service-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-service-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
+   <UL id="-strong-proxy-operations-service-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-connect-proxy-service-v1-core" class="nav-item">Create Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#create-connect-proxy-path-service-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-service-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-path-service-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-service-v1-core" class="nav-item">Get Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-path-service-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-service-v1-core" class="nav-item">Head Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-path-service-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-service-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-path-service-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-config-and-storage-apis-strong-" class="nav-item"><STRONG>CONFIG AND STORAGE APIS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#configmap-v1-core" class="nav-item">ConfigMap v1 core</A></LI>
+ <UL id="configmap-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-configmap-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-configmap-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-configmap-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-configmap-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-configmap-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-configmap-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-configmap-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-configmap-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-configmap-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-configmap-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-configmap-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-configmap-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-configmap-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-configmap-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-configmap-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#csidriver-v1-storage-k8s-io" class="nav-item">CSIDriver v1 storage.k8s.io</A></LI>
+ <UL id="csidriver-v1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-csidriver-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-csidriver-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-csidriver-v1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-csidriver-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-csidriver-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-csidriver-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-csidriver-v1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-csidriver-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-csidriver-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-csidriver-v1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-csidriver-v1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-csidriver-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-csidriver-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#csinode-v1-storage-k8s-io" class="nav-item">CSINode v1 storage.k8s.io</A></LI>
+ <UL id="csinode-v1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-csinode-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-csinode-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-csinode-v1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-csinode-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-csinode-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-csinode-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-csinode-v1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-csinode-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-csinode-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-csinode-v1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-csinode-v1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-csinode-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-csinode-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#secret-v1-core" class="nav-item">Secret v1 core</A></LI>
+ <UL id="secret-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-secret-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-secret-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-secret-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-secret-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-secret-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-secret-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-secret-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-secret-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-secret-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-secret-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-secret-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-secret-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-secret-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-secret-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-secret-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#persistentvolumeclaim-v1-core" class="nav-item">PersistentVolumeClaim v1 core</A></LI>
+ <UL id="persistentvolumeclaim-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-persistentvolumeclaim-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-persistentvolumeclaim-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-persistentvolumeclaim-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-persistentvolumeclaim-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-persistentvolumeclaim-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-persistentvolumeclaim-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-persistentvolumeclaim-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-persistentvolumeclaim-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-persistentvolumeclaim-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-persistentvolumeclaim-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-persistentvolumeclaim-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-persistentvolumeclaim-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#storageclass-v1-storage-k8s-io" class="nav-item">StorageClass v1 storage.k8s.io</A></LI>
+ <UL id="storageclass-v1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-storageclass-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-storageclass-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-storageclass-v1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-storageclass-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-storageclass-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-storageclass-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-storageclass-v1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-storageclass-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-storageclass-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-storageclass-v1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-storageclass-v1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-storageclass-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-storageclass-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">CSIStorageCapacity v1beta1 storage.k8s.io</A></LI>
+ <UL id="csistoragecapacity-v1beta1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#volume-v1-core" class="nav-item">Volume v1 core</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#volumeattachment-v1-storage-k8s-io" class="nav-item">VolumeAttachment v1 storage.k8s.io</A></LI>
+ <UL id="volumeattachment-v1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-volumeattachment-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-volumeattachment-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-volumeattachment-v1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-volumeattachment-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-volumeattachment-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-volumeattachment-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-volumeattachment-v1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-volumeattachment-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-volumeattachment-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-volumeattachment-v1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-volumeattachment-v1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-volumeattachment-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-volumeattachment-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-volumeattachment-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-volumeattachment-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-metadata-apis-strong-" class="nav-item"><STRONG>METADATA APIS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#controllerrevision-v1-apps" class="nav-item">ControllerRevision v1 apps</A></LI>
+ <UL id="controllerrevision-v1-apps-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-controllerrevision-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-controllerrevision-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-controllerrevision-v1-apps" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-controllerrevision-v1-apps" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-controllerrevision-v1-apps" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-controllerrevision-v1-apps" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-controllerrevision-v1-apps" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-controllerrevision-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-controllerrevision-v1-apps-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-controllerrevision-v1-apps" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-controllerrevision-v1-apps" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-controllerrevision-v1-apps" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-controllerrevision-v1-apps" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-controllerrevision-v1-apps" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-controllerrevision-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinition v1 apiextensions.k8s.io</A></LI>
+ <UL id="customresourcedefinition-v1-apiextensions-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#event-v1-events-k8s-io" class="nav-item">Event v1 events.k8s.io</A></LI>
+ <UL id="event-v1-events-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-event-v1-events-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-event-v1-events-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-event-v1-events-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-event-v1-events-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-event-v1-events-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-event-v1-events-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-event-v1-events-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-event-v1-events-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-event-v1-events-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-event-v1-events-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-event-v1-events-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-event-v1-events-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-event-v1-events-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-event-v1-events-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-event-v1-events-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#limitrange-v1-core" class="nav-item">LimitRange v1 core</A></LI>
+ <UL id="limitrange-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-limitrange-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-limitrange-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-limitrange-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-limitrange-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-limitrange-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-limitrange-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-limitrange-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-limitrange-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-limitrange-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-limitrange-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-limitrange-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-limitrange-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-limitrange-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-limitrange-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-limitrange-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscaler-v1-autoscaling" class="nav-item">HorizontalPodAutoscaler v1 autoscaling</A></LI>
+ <UL id="horizontalpodautoscaler-v1-autoscaling-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">MutatingWebhookConfiguration v1 admissionregistration.k8s.io</A></LI>
+ <UL id="mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">ValidatingWebhookConfiguration v1 admissionregistration.k8s.io</A></LI>
+ <UL id="validatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podtemplate-v1-core" class="nav-item">PodTemplate v1 core</A></LI>
+ <UL id="podtemplate-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podtemplate-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-podtemplate-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-podtemplate-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-podtemplate-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-podtemplate-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-podtemplate-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-podtemplate-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podtemplate-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-podtemplate-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-podtemplate-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-podtemplate-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-podtemplate-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-podtemplate-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-podtemplate-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-podtemplate-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#poddisruptionbudget-v1-policy" class="nav-item">PodDisruptionBudget v1 policy</A></LI>
+ <UL id="poddisruptionbudget-v1-policy-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-poddisruptionbudget-v1-policy-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-poddisruptionbudget-v1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-poddisruptionbudget-v1-policy" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-poddisruptionbudget-v1-policy" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-poddisruptionbudget-v1-policy" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-poddisruptionbudget-v1-policy" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-poddisruptionbudget-v1-policy" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-poddisruptionbudget-v1-policy-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-poddisruptionbudget-v1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-poddisruptionbudget-v1-policy" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-poddisruptionbudget-v1-policy" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-poddisruptionbudget-v1-policy" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-poddisruptionbudget-v1-policy" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-poddisruptionbudget-v1-policy" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-poddisruptionbudget-v1-policy" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-poddisruptionbudget-v1-policy-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-poddisruptionbudget-v1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-poddisruptionbudget-v1-policy" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-poddisruptionbudget-v1-policy" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-poddisruptionbudget-v1-policy" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#priorityclass-v1-scheduling-k8s-io" class="nav-item">PriorityClass v1 scheduling.k8s.io</A></LI>
+ <UL id="priorityclass-v1-scheduling-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-priorityclass-v1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-priorityclass-v1-scheduling-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-priorityclass-v1-scheduling-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-priorityclass-v1-scheduling-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-priorityclass-v1-scheduling-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-priorityclass-v1-scheduling-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-priorityclass-v1-scheduling-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-priorityclass-v1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-priorityclass-v1-scheduling-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-priorityclass-v1-scheduling-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-priorityclass-v1-scheduling-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-priorityclass-v1-scheduling-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-priorityclass-v1-scheduling-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podsecuritypolicy-v1beta1-policy" class="nav-item">PodSecurityPolicy v1beta1 policy</A></LI>
+ <UL id="podsecuritypolicy-v1beta1-policy-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-podsecuritypolicy-v1beta1-policy" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-podsecuritypolicy-v1beta1-policy" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-podsecuritypolicy-v1beta1-policy" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-podsecuritypolicy-v1beta1-policy" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-podsecuritypolicy-v1beta1-policy" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-podsecuritypolicy-v1beta1-policy" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-podsecuritypolicy-v1beta1-policy" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-podsecuritypolicy-v1beta1-policy" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-podsecuritypolicy-v1beta1-policy" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-cluster-apis-strong-" class="nav-item"><STRONG>CLUSTER APIS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#apiservice-v1-apiregistration-k8s-io" class="nav-item">APIService v1 apiregistration.k8s.io</A></LI>
+ <UL id="apiservice-v1-apiregistration-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-apiservice-v1-apiregistration-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-apiservice-v1-apiregistration-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#binding-v1-core" class="nav-item">Binding v1 core</A></LI>
+ <UL id="binding-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-binding-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-binding-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-binding-v1-core" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">CertificateSigningRequest v1 certificates.k8s.io</A></LI>
+ <UL id="certificatesigningrequest-v1-certificates-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-certificatesigningrequest-v1-certificates-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-certificatesigningrequest-v1-certificates-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-certificatesigningrequest-v1-certificates-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">ClusterRole v1 rbac.authorization.k8s.io</A></LI>
+ <UL id="clusterrole-v1-rbac-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">ClusterRoleBinding v1 rbac.authorization.k8s.io</A></LI>
+ <UL id="clusterrolebinding-v1-rbac-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#componentstatus-v1-core" class="nav-item">ComponentStatus v1 core</A></LI>
+ <UL id="componentstatus-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-componentstatus-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-componentstatus-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-componentstatus-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-componentstatus-v1-core" class="nav-item">List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchema v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="flowschema-v1beta1-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#lease-v1-coordination-k8s-io" class="nav-item">Lease v1 coordination.k8s.io</A></LI>
+ <UL id="lease-v1-coordination-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-lease-v1-coordination-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-lease-v1-coordination-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-lease-v1-coordination-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-lease-v1-coordination-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-lease-v1-coordination-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-lease-v1-coordination-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-lease-v1-coordination-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-lease-v1-coordination-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-lease-v1-coordination-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-lease-v1-coordination-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-lease-v1-coordination-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-lease-v1-coordination-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-lease-v1-coordination-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-lease-v1-coordination-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-lease-v1-coordination-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">LocalSubjectAccessReview v1 authorization.k8s.io</A></LI>
+ <UL id="localsubjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#namespace-v1-core" class="nav-item">Namespace v1 core</A></LI>
+ <UL id="namespace-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-namespace-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-namespace-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-namespace-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-namespace-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-namespace-v1-core" class="nav-item">Delete</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-namespace-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-namespace-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-namespace-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-namespace-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-namespace-v1-core" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-namespace-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-namespace-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-namespace-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-namespace-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#node-v1-core" class="nav-item">Node v1 core</A></LI>
+ <UL id="node-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-node-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-node-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-node-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-node-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-node-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-node-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-node-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-node-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-node-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-node-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-node-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-node-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-node-v1-core" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-node-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-node-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-node-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-node-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-node-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-node-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
+   <UL id="-strong-proxy-operations-node-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-connect-proxy-node-v1-core" class="nav-item">Create Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#create-connect-proxy-path-node-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-node-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#delete-connect-proxy-path-node-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-node-v1-core" class="nav-item">Get Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#get-connect-proxy-path-node-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-node-v1-core" class="nav-item">Head Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#head-connect-proxy-path-node-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-node-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
+    <LI class="nav-level-2"><A href="#replace-connect-proxy-path-node-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#persistentvolume-v1-core" class="nav-item">PersistentVolume v1 core</A></LI>
+ <UL id="persistentvolume-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-persistentvolume-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-persistentvolume-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-persistentvolume-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-persistentvolume-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-persistentvolume-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-persistentvolume-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-persistentvolume-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-persistentvolume-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-persistentvolume-v1-core" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-persistentvolume-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-persistentvolume-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-persistentvolume-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcequota-v1-core" class="nav-item">ResourceQuota v1 core</A></LI>
+ <UL id="resourcequota-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-resourcequota-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-resourcequota-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-resourcequota-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-resourcequota-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-resourcequota-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-resourcequota-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-resourcequota-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-resourcequota-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-resourcequota-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-resourcequota-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-resourcequota-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-resourcequota-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-resourcequota-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-resourcequota-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-resourcequota-v1-core" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-resourcequota-v1-core" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-resourcequota-v1-core" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#role-v1-rbac-authorization-k8s-io" class="nav-item">Role v1 rbac.authorization.k8s.io</A></LI>
+ <UL id="role-v1-rbac-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-role-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-role-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-role-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-role-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-role-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">RoleBinding v1 rbac.authorization.k8s.io</A></LI>
+ <UL id="rolebinding-v1-rbac-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#runtimeclass-v1-node-k8s-io" class="nav-item">RuntimeClass v1 node.k8s.io</A></LI>
+ <UL id="runtimeclass-v1-node-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-runtimeclass-v1-node-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-runtimeclass-v1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-runtimeclass-v1-node-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-runtimeclass-v1-node-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-runtimeclass-v1-node-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-runtimeclass-v1-node-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-runtimeclass-v1-node-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-runtimeclass-v1-node-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-runtimeclass-v1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-runtimeclass-v1-node-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-runtimeclass-v1-node-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-runtimeclass-v1-node-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-runtimeclass-v1-node-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">SelfSubjectAccessReview v1 authorization.k8s.io</A></LI>
+ <UL id="selfsubjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">SelfSubjectRulesReview v1 authorization.k8s.io</A></LI>
+ <UL id="selfsubjectrulesreview-v1-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#serviceaccount-v1-core" class="nav-item">ServiceAccount v1 core</A></LI>
+ <UL id="serviceaccount-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-serviceaccount-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-serviceaccount-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-serviceaccount-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-serviceaccount-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-serviceaccount-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-serviceaccount-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-serviceaccount-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-serviceaccount-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-serviceaccount-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-serviceaccount-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-serviceaccount-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-serviceaccount-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-serviceaccount-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-serviceaccount-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-serviceaccount-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">StorageVersion v1alpha1 internal.apiserver.k8s.io</A></LI>
+ <UL id="storageversion-v1alpha1-internal-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#subjectaccessreview-v1-authorization-k8s-io" class="nav-item">SubjectAccessReview v1 authorization.k8s.io</A></LI>
+ <UL id="subjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-subjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#tokenrequest-v1-authentication-k8s-io" class="nav-item">TokenRequest v1 authentication.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#tokenreview-v1-authentication-k8s-io" class="nav-item">TokenReview v1 authentication.k8s.io</A></LI>
+ <UL id="tokenreview-v1-authentication-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-tokenreview-v1-authentication-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#networkpolicy-v1-networking-k8s-io" class="nav-item">NetworkPolicy v1 networking.k8s.io</A></LI>
+ <UL id="networkpolicy-v1-networking-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-networkpolicy-v1-networking-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-networkpolicy-v1-networking-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-networkpolicy-v1-networking-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-networkpolicy-v1-networking-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-networkpolicy-v1-networking-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-definitions-strong-" class="nav-item"><STRONG>DEFINITIONS</STRONG></A></LI>
+</UL>
+ <UL id="-strong-definitions-strong--nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2"><A href="#apigroup-v1-meta" class="nav-item">APIGroup v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#apiresource-v1-meta" class="nav-item">APIResource v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#apiservicecondition-v1-apiregistration-k8s-io" class="nav-item">APIServiceCondition v1 apiregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#apiversions-v1-meta" class="nav-item">APIVersions v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#awselasticblockstorevolumesource-v1-core" class="nav-item">AWSElasticBlockStoreVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#affinity-v1-core" class="nav-item">Affinity v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#aggregationrule-v1-rbac-authorization-k8s-io" class="nav-item">AggregationRule v1 rbac.authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#allowedcsidriver-v1beta1-policy" class="nav-item">AllowedCSIDriver v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#allowedflexvolume-v1beta1-policy" class="nav-item">AllowedFlexVolume v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#allowedhostpath-v1beta1-policy" class="nav-item">AllowedHostPath v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#attachedvolume-v1-core" class="nav-item">AttachedVolume v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#azurediskvolumesource-v1-core" class="nav-item">AzureDiskVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#azurefilepersistentvolumesource-v1-core" class="nav-item">AzureFilePersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#azurefilevolumesource-v1-core" class="nav-item">AzureFileVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#boundobjectreference-v1-authentication-k8s-io" class="nav-item">BoundObjectReference v1 authentication.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#csinodedriver-v1-storage-k8s-io" class="nav-item">CSINodeDriver v1 storage.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#csipersistentvolumesource-v1-core" class="nav-item">CSIPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#csivolumesource-v1-core" class="nav-item">CSIVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#capabilities-v1-core" class="nav-item">Capabilities v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#cephfspersistentvolumesource-v1-core" class="nav-item">CephFSPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#cephfsvolumesource-v1-core" class="nav-item">CephFSVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#certificatesigningrequestcondition-v1-certificates-k8s-io" class="nav-item">CertificateSigningRequestCondition v1 certificates.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#cinderpersistentvolumesource-v1-core" class="nav-item">CinderPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#cindervolumesource-v1-core" class="nav-item">CinderVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#clientipconfig-v1-core" class="nav-item">ClientIPConfig v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#componentcondition-v1-core" class="nav-item">ComponentCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#condition-v1-meta" class="nav-item">Condition v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#configmapenvsource-v1-core" class="nav-item">ConfigMapEnvSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#configmapkeyselector-v1-core" class="nav-item">ConfigMapKeySelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#configmapnodeconfigsource-v1-core" class="nav-item">ConfigMapNodeConfigSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#configmapprojection-v1-core" class="nav-item">ConfigMapProjection v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#configmapvolumesource-v1-core" class="nav-item">ConfigMapVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerimage-v1-core" class="nav-item">ContainerImage v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerport-v1-core" class="nav-item">ContainerPort v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerresourcemetricsource-v2-autoscaling" class="nav-item">ContainerResourceMetricSource v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerresourcemetricstatus-v2-autoscaling" class="nav-item">ContainerResourceMetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerstate-v1-core" class="nav-item">ContainerState v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerstaterunning-v1-core" class="nav-item">ContainerStateRunning v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerstateterminated-v1-core" class="nav-item">ContainerStateTerminated v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#containerstatewaiting-v1-core" class="nav-item">ContainerStateWaiting v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#crossversionobjectreference-v1-autoscaling" class="nav-item">CrossVersionObjectReference v1 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcecolumndefinition-v1-apiextensions-k8s-io" class="nav-item">CustomResourceColumnDefinition v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourceconversion-v1-apiextensions-k8s-io" class="nav-item">CustomResourceConversion v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcedefinitioncondition-v1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionCondition v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcedefinitionnames-v1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionNames v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcedefinitionversion-v1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionVersion v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcesubresourcescale-v1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresourceScale v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcesubresourcestatus-v1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresourceStatus v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcesubresources-v1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresources v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#customresourcevalidation-v1-apiextensions-k8s-io" class="nav-item">CustomResourceValidation v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#daemonendpoint-v1-core" class="nav-item">DaemonEndpoint v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#daemonsetcondition-v1-apps" class="nav-item">DaemonSetCondition v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#daemonsetupdatestrategy-v1-apps" class="nav-item">DaemonSetUpdateStrategy v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#deleteoptions-v1-meta" class="nav-item">DeleteOptions v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#deploymentcondition-v1-apps" class="nav-item">DeploymentCondition v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#downwardapiprojection-v1-core" class="nav-item">DownwardAPIProjection v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#downwardapivolumefile-v1-core" class="nav-item">DownwardAPIVolumeFile v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#downwardapivolumesource-v1-core" class="nav-item">DownwardAPIVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#emptydirvolumesource-v1-core" class="nav-item">EmptyDirVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpoint-v1-discovery-k8s-io" class="nav-item">Endpoint v1 discovery.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpointaddress-v1-core" class="nav-item">EndpointAddress v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpointconditions-v1-discovery-k8s-io" class="nav-item">EndpointConditions v1 discovery.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpointhints-v1-discovery-k8s-io" class="nav-item">EndpointHints v1 discovery.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpointport-v1-core" class="nav-item">EndpointPort v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#endpointsubset-v1-core" class="nav-item">EndpointSubset v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#envfromsource-v1-core" class="nav-item">EnvFromSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#envvar-v1-core" class="nav-item">EnvVar v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#envvarsource-v1-core" class="nav-item">EnvVarSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ephemeralcontainer-v1-core" class="nav-item">EphemeralContainer v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ephemeralvolumesource-v1-core" class="nav-item">EphemeralVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#eventseries-v1-events-k8s-io" class="nav-item">EventSeries v1 events.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#eventsource-v1-core" class="nav-item">EventSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#eviction-v1-policy" class="nav-item">Eviction v1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#execaction-v1-core" class="nav-item">ExecAction v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#externaldocumentation-v1-apiextensions-k8s-io" class="nav-item">ExternalDocumentation v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#externalmetricsource-v2-autoscaling" class="nav-item">ExternalMetricSource v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#externalmetricstatus-v2-autoscaling" class="nav-item">ExternalMetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#fcvolumesource-v1-core" class="nav-item">FCVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#fsgroupstrategyoptions-v1beta1-policy" class="nav-item">FSGroupStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#fieldsv1-v1-meta" class="nav-item">FieldsV1 v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flexpersistentvolumesource-v1-core" class="nav-item">FlexPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flexvolumesource-v1-core" class="nav-item">FlexVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flockervolumesource-v1-core" class="nav-item">FlockerVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">FlowDistinguisherMethod v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchema v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchemaCondition v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#forzone-v1-discovery-k8s-io" class="nav-item">ForZone v1 discovery.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#gcepersistentdiskvolumesource-v1-core" class="nav-item">GCEPersistentDiskVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#grpcaction-v1-core" class="nav-item">GRPCAction v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#gitrepovolumesource-v1-core" class="nav-item">GitRepoVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#glusterfspersistentvolumesource-v1-core" class="nav-item">GlusterfsPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#glusterfsvolumesource-v1-core" class="nav-item">GlusterfsVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#groupsubject-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">GroupSubject v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#groupversionfordiscovery-v1-meta" class="nav-item">GroupVersionForDiscovery v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#hpascalingpolicy-v2-autoscaling" class="nav-item">HPAScalingPolicy v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#hpascalingrules-v2-autoscaling" class="nav-item">HPAScalingRules v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#httpgetaction-v1-core" class="nav-item">HTTPGetAction v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#httpheader-v1-core" class="nav-item">HTTPHeader v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#httpingresspath-v1-networking-k8s-io" class="nav-item">HTTPIngressPath v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#httpingressrulevalue-v1-networking-k8s-io" class="nav-item">HTTPIngressRuleValue v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#horizontalpodautoscaler-v2-autoscaling" class="nav-item">HorizontalPodAutoscaler v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#horizontalpodautoscalerbehavior-v2-autoscaling" class="nav-item">HorizontalPodAutoscalerBehavior v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#horizontalpodautoscalercondition-v2-autoscaling" class="nav-item">HorizontalPodAutoscalerCondition v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#hostalias-v1-core" class="nav-item">HostAlias v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#hostpathvolumesource-v1-core" class="nav-item">HostPathVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#hostportrange-v1beta1-policy" class="nav-item">HostPortRange v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#idrange-v1beta1-policy" class="nav-item">IDRange v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ipblock-v1-networking-k8s-io" class="nav-item">IPBlock v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#iscsipersistentvolumesource-v1-core" class="nav-item">ISCSIPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#iscsivolumesource-v1-core" class="nav-item">ISCSIVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressbackend-v1-networking-k8s-io" class="nav-item">IngressBackend v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressclassparametersreference-v1-networking-k8s-io" class="nav-item">IngressClassParametersReference v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressrule-v1-networking-k8s-io" class="nav-item">IngressRule v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressservicebackend-v1-networking-k8s-io" class="nav-item">IngressServiceBackend v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingresstls-v1-networking-k8s-io" class="nav-item">IngressTLS v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#json-v1-apiextensions-k8s-io" class="nav-item">JSON v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#jsonschemaprops-v1-apiextensions-k8s-io" class="nav-item">JSONSchemaProps v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#jsonschemapropsorarray-v1-apiextensions-k8s-io" class="nav-item">JSONSchemaPropsOrArray v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#jsonschemapropsorbool-v1-apiextensions-k8s-io" class="nav-item">JSONSchemaPropsOrBool v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#jobcondition-v1-batch" class="nav-item">JobCondition v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#jobtemplatespec-v1-batch" class="nav-item">JobTemplateSpec v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#keytopath-v1-core" class="nav-item">KeyToPath v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#labelselector-v1-meta" class="nav-item">LabelSelector v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#labelselectorrequirement-v1-meta" class="nav-item">LabelSelectorRequirement v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#lifecycle-v1-core" class="nav-item">Lifecycle v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#lifecyclehandler-v1-core" class="nav-item">LifecycleHandler v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#limitrangeitem-v1-core" class="nav-item">LimitRangeItem v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#limitresponse-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">LimitResponse v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">LimitedPriorityLevelConfiguration v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#listmeta-v1-meta" class="nav-item">ListMeta v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#loadbalanceringress-v1-core" class="nav-item">LoadBalancerIngress v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#loadbalancerstatus-v1-core" class="nav-item">LoadBalancerStatus v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#localobjectreference-v1-core" class="nav-item">LocalObjectReference v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#localvolumesource-v1-core" class="nav-item">LocalVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#managedfieldsentry-v1-meta" class="nav-item">ManagedFieldsEntry v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#metricidentifier-v2-autoscaling" class="nav-item">MetricIdentifier v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#metricspec-v2-autoscaling" class="nav-item">MetricSpec v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#metricstatus-v2-autoscaling" class="nav-item">MetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#metrictarget-v2-autoscaling" class="nav-item">MetricTarget v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#metricvaluestatus-v2-autoscaling" class="nav-item">MetricValueStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#microtime-v1-meta" class="nav-item">MicroTime v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#mutatingwebhook-v1-admissionregistration-k8s-io" class="nav-item">MutatingWebhook v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nfsvolumesource-v1-core" class="nav-item">NFSVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#namespacecondition-v1-core" class="nav-item">NamespaceCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#networkpolicyegressrule-v1-networking-k8s-io" class="nav-item">NetworkPolicyEgressRule v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#networkpolicyingressrule-v1-networking-k8s-io" class="nav-item">NetworkPolicyIngressRule v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#networkpolicypeer-v1-networking-k8s-io" class="nav-item">NetworkPolicyPeer v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#networkpolicyport-v1-networking-k8s-io" class="nav-item">NetworkPolicyPort v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeaddress-v1-core" class="nav-item">NodeAddress v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeaffinity-v1-core" class="nav-item">NodeAffinity v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodecondition-v1-core" class="nav-item">NodeCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeconfigsource-v1-core" class="nav-item">NodeConfigSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeconfigstatus-v1-core" class="nav-item">NodeConfigStatus v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodedaemonendpoints-v1-core" class="nav-item">NodeDaemonEndpoints v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeselector-v1-core" class="nav-item">NodeSelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeselectorrequirement-v1-core" class="nav-item">NodeSelectorRequirement v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodeselectorterm-v1-core" class="nav-item">NodeSelectorTerm v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nodesysteminfo-v1-core" class="nav-item">NodeSystemInfo v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nonresourceattributes-v1-authorization-k8s-io" class="nav-item">NonResourceAttributes v1 authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">NonResourcePolicyRule v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#nonresourcerule-v1-authorization-k8s-io" class="nav-item">NonResourceRule v1 authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#objectfieldselector-v1-core" class="nav-item">ObjectFieldSelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#objectmeta-v1-meta" class="nav-item">ObjectMeta v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#objectmetricsource-v2-autoscaling" class="nav-item">ObjectMetricSource v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#objectmetricstatus-v2-autoscaling" class="nav-item">ObjectMetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#objectreference-v1-core" class="nav-item">ObjectReference v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#overhead-v1-node-k8s-io" class="nav-item">Overhead v1 node.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ownerreference-v1-meta" class="nav-item">OwnerReference v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#patch-v1-meta" class="nav-item">Patch v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#persistentvolumeclaimcondition-v1-core" class="nav-item">PersistentVolumeClaimCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#persistentvolumeclaimtemplate-v1-core" class="nav-item">PersistentVolumeClaimTemplate v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#persistentvolumeclaimvolumesource-v1-core" class="nav-item">PersistentVolumeClaimVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#photonpersistentdiskvolumesource-v1-core" class="nav-item">PhotonPersistentDiskVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podaffinity-v1-core" class="nav-item">PodAffinity v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podaffinityterm-v1-core" class="nav-item">PodAffinityTerm v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podantiaffinity-v1-core" class="nav-item">PodAntiAffinity v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podcondition-v1-core" class="nav-item">PodCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#poddnsconfig-v1-core" class="nav-item">PodDNSConfig v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#poddnsconfigoption-v1-core" class="nav-item">PodDNSConfigOption v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podip-v1-core" class="nav-item">PodIP v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podos-v1-core" class="nav-item">PodOS v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podreadinessgate-v1-core" class="nav-item">PodReadinessGate v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podsecuritycontext-v1-core" class="nav-item">PodSecurityContext v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podsmetricsource-v2-autoscaling" class="nav-item">PodsMetricSource v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podsmetricstatus-v2-autoscaling" class="nav-item">PodsMetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#policyrule-v1-rbac-authorization-k8s-io" class="nav-item">PolicyRule v1 rbac.authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">PolicyRulesWithSubjects v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#portstatus-v1-core" class="nav-item">PortStatus v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#portworxvolumesource-v1-core" class="nav-item">PortworxVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#preconditions-v1-meta" class="nav-item">Preconditions v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#preferredschedulingterm-v1-core" class="nav-item">PreferredSchedulingTerm v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfiguration v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationCondition v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationReference v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#probe-v1-core" class="nav-item">Probe v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#projectedvolumesource-v1-core" class="nav-item">ProjectedVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#quantity-resource-core" class="nav-item">Quantity resource core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">QueuingConfiguration v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#quobytevolumesource-v1-core" class="nav-item">QuobyteVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#rbdpersistentvolumesource-v1-core" class="nav-item">RBDPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#rbdvolumesource-v1-core" class="nav-item">RBDVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#replicasetcondition-v1-apps" class="nav-item">ReplicaSetCondition v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#replicationcontrollercondition-v1-core" class="nav-item">ReplicationControllerCondition v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourceattributes-v1-authorization-k8s-io" class="nav-item">ResourceAttributes v1 authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcefieldselector-v1-core" class="nav-item">ResourceFieldSelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcemetricsource-v2-autoscaling" class="nav-item">ResourceMetricSource v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcemetricstatus-v2-autoscaling" class="nav-item">ResourceMetricStatus v2 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">ResourcePolicyRule v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcerequirements-v1-core" class="nav-item">ResourceRequirements v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourcerule-v1-authorization-k8s-io" class="nav-item">ResourceRule v1 authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#roleref-v1-rbac-authorization-k8s-io" class="nav-item">RoleRef v1 rbac.authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#rollingupdatestatefulsetstrategy-v1-apps" class="nav-item">RollingUpdateStatefulSetStrategy v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#rulewithoperations-v1-admissionregistration-k8s-io" class="nav-item">RuleWithOperations v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#runasgroupstrategyoptions-v1beta1-policy" class="nav-item">RunAsGroupStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#runasuserstrategyoptions-v1beta1-policy" class="nav-item">RunAsUserStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#runtimeclassstrategyoptions-v1beta1-policy" class="nav-item">RuntimeClassStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#selinuxoptions-v1-core" class="nav-item">SELinuxOptions v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#selinuxstrategyoptions-v1beta1-policy" class="nav-item">SELinuxStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scale-v1-autoscaling" class="nav-item">Scale v1 autoscaling</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scaleiopersistentvolumesource-v1-core" class="nav-item">ScaleIOPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scaleiovolumesource-v1-core" class="nav-item">ScaleIOVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scheduling-v1-node-k8s-io" class="nav-item">Scheduling v1 node.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scopeselector-v1-core" class="nav-item">ScopeSelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#scopedresourceselectorrequirement-v1-core" class="nav-item">ScopedResourceSelectorRequirement v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#seccompprofile-v1-core" class="nav-item">SeccompProfile v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#secretenvsource-v1-core" class="nav-item">SecretEnvSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#secretkeyselector-v1-core" class="nav-item">SecretKeySelector v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#secretprojection-v1-core" class="nav-item">SecretProjection v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#secretreference-v1-core" class="nav-item">SecretReference v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#secretvolumesource-v1-core" class="nav-item">SecretVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#securitycontext-v1-core" class="nav-item">SecurityContext v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#serveraddressbyclientcidr-v1-meta" class="nav-item">ServerAddressByClientCIDR v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#serverstorageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">ServerStorageVersion v1alpha1 internal.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">ServiceAccountSubject v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#serviceaccounttokenprojection-v1-core" class="nav-item">ServiceAccountTokenProjection v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#servicebackendport-v1-networking-k8s-io" class="nav-item">ServiceBackendPort v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#serviceport-v1-core" class="nav-item">ServicePort v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#servicereference-v1-admissionregistration-k8s-io" class="nav-item">ServiceReference v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#sessionaffinityconfig-v1-core" class="nav-item">SessionAffinityConfig v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#statefulsetcondition-v1-apps" class="nav-item">StatefulSetCondition v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#statefulsetpersistentvolumeclaimretentionpolicy-v1-apps" class="nav-item">StatefulSetPersistentVolumeClaimRetentionPolicy v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#statefulsetupdatestrategy-v1-apps" class="nav-item">StatefulSetUpdateStrategy v1 apps</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#status-v1-meta" class="nav-item">Status v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#statuscause-v1-meta" class="nav-item">StatusCause v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#statusdetails-v1-meta" class="nav-item">StatusDetails v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#storageospersistentvolumesource-v1-core" class="nav-item">StorageOSPersistentVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#storageosvolumesource-v1-core" class="nav-item">StorageOSVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io" class="nav-item">StorageVersionCondition v1alpha1 internal.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#subject-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Subject v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#subjectrulesreviewstatus-v1-authorization-k8s-io" class="nav-item">SubjectRulesReviewStatus v1 authorization.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#supplementalgroupsstrategyoptions-v1beta1-policy" class="nav-item">SupplementalGroupsStrategyOptions v1beta1 policy</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#sysctl-v1-core" class="nav-item">Sysctl v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#tcpsocketaction-v1-core" class="nav-item">TCPSocketAction v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#taint-v1-core" class="nav-item">Taint v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#time-v1-meta" class="nav-item">Time v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#toleration-v1-core" class="nav-item">Toleration v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#topologyselectorlabelrequirement-v1-core" class="nav-item">TopologySelectorLabelRequirement v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#topologyselectorterm-v1-core" class="nav-item">TopologySelectorTerm v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#topologyspreadconstraint-v1-core" class="nav-item">TopologySpreadConstraint v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#typedlocalobjectreference-v1-core" class="nav-item">TypedLocalObjectReference v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#uncountedterminatedpods-v1-batch" class="nav-item">UncountedTerminatedPods v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#userinfo-v1-authentication-k8s-io" class="nav-item">UserInfo v1 authentication.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#usersubject-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">UserSubject v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#validatingwebhook-v1-admissionregistration-k8s-io" class="nav-item">ValidatingWebhook v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#validationrule-v1-apiextensions-k8s-io" class="nav-item">ValidationRule v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumeattachmentsource-v1-storage-k8s-io" class="nav-item">VolumeAttachmentSource v1 storage.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumedevice-v1-core" class="nav-item">VolumeDevice v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumeerror-v1-storage-k8s-io" class="nav-item">VolumeError v1 storage.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumemount-v1-core" class="nav-item">VolumeMount v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumenodeaffinity-v1-core" class="nav-item">VolumeNodeAffinity v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumenoderesources-v1-storage-k8s-io" class="nav-item">VolumeNodeResources v1 storage.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#volumeprojection-v1-core" class="nav-item">VolumeProjection v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#vspherevirtualdiskvolumesource-v1-core" class="nav-item">VsphereVirtualDiskVolumeSource v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#watchevent-v1-meta" class="nav-item">WatchEvent v1 meta</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#webhookclientconfig-v1-admissionregistration-k8s-io" class="nav-item">WebhookClientConfig v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#webhookconversion-v1-apiextensions-k8s-io" class="nav-item">WebhookConversion v1 apiextensions.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#weightedpodaffinityterm-v1-core" class="nav-item">WeightedPodAffinityTerm v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#windowssecuritycontextoptions-v1-core" class="nav-item">WindowsSecurityContextOptions v1 core</A></LI>
+ </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-old-api-versions-strong-" class="nav-item"><STRONG>OLD API VERSIONS</STRONG></A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">CSIStorageCapacity v1alpha1 storage.k8s.io</A></LI>
+ <UL id="csistoragecapacity-v1alpha1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#containerresourcemetricsource-v2beta2-autoscaling" class="nav-item">ContainerResourceMetricSource v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#containerresourcemetricsource-v2beta1-autoscaling" class="nav-item">ContainerResourceMetricSource v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#containerresourcemetricstatus-v2beta2-autoscaling" class="nav-item">ContainerResourceMetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#containerresourcemetricstatus-v2beta1-autoscaling" class="nav-item">ContainerResourceMetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#cronjob-v1beta1-batch" class="nav-item">CronJob v1beta1 batch</A></LI>
+ <UL id="cronjob-v1beta1-batch-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-cronjob-v1beta1-batch" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-cronjob-v1beta1-batch" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-cronjob-v1beta1-batch" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-cronjob-v1beta1-batch" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-cronjob-v1beta1-batch" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-cronjob-v1beta1-batch" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-cronjob-v1beta1-batch" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-cronjob-v1beta1-batch" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-cronjob-v1beta1-batch" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-cronjob-v1beta1-batch" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-cronjob-v1beta1-batch" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-cronjob-v1beta1-batch" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-cronjob-v1beta1-batch" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-cronjob-v1beta1-batch" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#crossversionobjectreference-v2-autoscaling" class="nav-item">CrossVersionObjectReference v2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#crossversionobjectreference-v2beta2-autoscaling" class="nav-item">CrossVersionObjectReference v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#crossversionobjectreference-v2beta1-autoscaling" class="nav-item">CrossVersionObjectReference v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpoint-v1beta1-discovery-k8s-io" class="nav-item">Endpoint v1beta1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointconditions-v1beta1-discovery-k8s-io" class="nav-item">EndpointConditions v1beta1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointhints-v1beta1-discovery-k8s-io" class="nav-item">EndpointHints v1beta1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointport-v1-discovery-k8s-io" class="nav-item">EndpointPort v1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointport-v1beta1-discovery-k8s-io" class="nav-item">EndpointPort v1beta1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#endpointslice-v1beta1-discovery-k8s-io" class="nav-item">EndpointSlice v1beta1 discovery.k8s.io</A></LI>
+ <UL id="endpointslice-v1beta1-discovery-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-endpointslice-v1beta1-discovery-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-endpointslice-v1beta1-discovery-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-endpointslice-v1beta1-discovery-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-endpointslice-v1beta1-discovery-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#event-v1-core" class="nav-item">Event v1 core</A></LI>
+ <UL id="event-v1-core-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-event-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-event-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-event-v1-core" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-event-v1-core" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-event-v1-core" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-event-v1-core" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-event-v1-core" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-event-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-event-v1-core-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-event-v1-core" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-event-v1-core" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-event-v1-core" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-event-v1-core" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-event-v1-core" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-event-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#event-v1beta1-events-k8s-io" class="nav-item">Event v1beta1 events.k8s.io</A></LI>
+ <UL id="event-v1beta1-events-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-event-v1beta1-events-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-event-v1beta1-events-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-event-v1beta1-events-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-event-v1beta1-events-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-event-v1beta1-events-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-event-v1beta1-events-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-event-v1beta1-events-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-event-v1beta1-events-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-event-v1beta1-events-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-event-v1beta1-events-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-event-v1beta1-events-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-event-v1beta1-events-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-event-v1beta1-events-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-event-v1beta1-events-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-event-v1beta1-events-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#eventseries-v1-core" class="nav-item">EventSeries v1 core</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#eventseries-v1beta1-events-k8s-io" class="nav-item">EventSeries v1beta1 events.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#externalmetricsource-v2beta2-autoscaling" class="nav-item">ExternalMetricSource v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#externalmetricsource-v2beta1-autoscaling" class="nav-item">ExternalMetricSource v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#externalmetricstatus-v2beta2-autoscaling" class="nav-item">ExternalMetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#externalmetricstatus-v2beta1-autoscaling" class="nav-item">ExternalMetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">FlowDistinguisherMethod v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchema v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="flowschema-v1beta1-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchemaCondition v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#forzone-v1beta1-discovery-k8s-io" class="nav-item">ForZone v1beta1 discovery.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#groupsubject-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">GroupSubject v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#hpascalingpolicy-v2beta2-autoscaling" class="nav-item">HPAScalingPolicy v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#hpascalingrules-v2beta2-autoscaling" class="nav-item">HPAScalingRules v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscaler-v1-autoscaling" class="nav-item">HorizontalPodAutoscaler v1 autoscaling</A></LI>
+ <UL id="horizontalpodautoscaler-v1-autoscaling-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">HorizontalPodAutoscaler v2beta2 autoscaling</A></LI>
+ <UL id="horizontalpodautoscaler-v2beta2-autoscaling-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v2beta2-autoscaling" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">HorizontalPodAutoscaler v2beta1 autoscaling</A></LI>
+ <UL id="horizontalpodautoscaler-v2beta1-autoscaling-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscalerbehavior-v2beta2-autoscaling" class="nav-item">HorizontalPodAutoscalerBehavior v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscalercondition-v2beta2-autoscaling" class="nav-item">HorizontalPodAutoscalerCondition v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#horizontalpodautoscalercondition-v2beta1-autoscaling" class="nav-item">HorizontalPodAutoscalerCondition v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#jobtemplatespec-v1beta1-batch" class="nav-item">JobTemplateSpec v1beta1 batch</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#limitresponse-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">LimitResponse v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">LimitedPriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricidentifier-v2beta2-autoscaling" class="nav-item">MetricIdentifier v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricspec-v2beta2-autoscaling" class="nav-item">MetricSpec v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricspec-v2beta1-autoscaling" class="nav-item">MetricSpec v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricstatus-v2beta2-autoscaling" class="nav-item">MetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricstatus-v2beta1-autoscaling" class="nav-item">MetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metrictarget-v2beta2-autoscaling" class="nav-item">MetricTarget v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#metricvaluestatus-v2beta2-autoscaling" class="nav-item">MetricValueStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">NonResourcePolicyRule v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#objectmetricsource-v2beta2-autoscaling" class="nav-item">ObjectMetricSource v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#objectmetricsource-v2beta1-autoscaling" class="nav-item">ObjectMetricSource v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#objectmetricstatus-v2beta2-autoscaling" class="nav-item">ObjectMetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#objectmetricstatus-v2beta1-autoscaling" class="nav-item">ObjectMetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#overhead-v1beta1-node-k8s-io" class="nav-item">Overhead v1beta1 node.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#overhead-v1alpha1-node-k8s-io" class="nav-item">Overhead v1alpha1 node.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#poddisruptionbudget-v1beta1-policy" class="nav-item">PodDisruptionBudget v1beta1 policy</A></LI>
+ <UL id="poddisruptionbudget-v1beta1-policy-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-poddisruptionbudget-v1beta1-policy" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-poddisruptionbudget-v1beta1-policy" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-poddisruptionbudget-v1beta1-policy" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-poddisruptionbudget-v1beta1-policy" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-poddisruptionbudget-v1beta1-policy" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-poddisruptionbudget-v1beta1-policy" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-poddisruptionbudget-v1beta1-policy" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-poddisruptionbudget-v1beta1-policy" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podsmetricsource-v2beta2-autoscaling" class="nav-item">PodsMetricSource v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podsmetricsource-v2beta1-autoscaling" class="nav-item">PodsMetricSource v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podsmetricstatus-v2beta2-autoscaling" class="nav-item">PodsMetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#podsmetricstatus-v2beta1-autoscaling" class="nav-item">PodsMetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">PolicyRulesWithSubjects v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationCondition v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationReference v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">QueuingConfiguration v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcemetricsource-v2beta2-autoscaling" class="nav-item">ResourceMetricSource v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcemetricsource-v2beta1-autoscaling" class="nav-item">ResourceMetricSource v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcemetricstatus-v2beta2-autoscaling" class="nav-item">ResourceMetricStatus v2beta2 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcemetricstatus-v2beta1-autoscaling" class="nav-item">ResourceMetricStatus v2beta1 autoscaling</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">ResourcePolicyRule v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#runtimeclass-v1beta1-node-k8s-io" class="nav-item">RuntimeClass v1beta1 node.k8s.io</A></LI>
+ <UL id="runtimeclass-v1beta1-node-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-runtimeclass-v1beta1-node-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-runtimeclass-v1beta1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-runtimeclass-v1beta1-node-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-runtimeclass-v1beta1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-runtimeclass-v1beta1-node-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-runtimeclass-v1beta1-node-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#runtimeclass-v1alpha1-node-k8s-io" class="nav-item">RuntimeClass v1alpha1 node.k8s.io</A></LI>
+ <UL id="runtimeclass-v1alpha1-node-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-runtimeclass-v1alpha1-node-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-runtimeclass-v1alpha1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-runtimeclass-v1alpha1-node-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-runtimeclass-v1alpha1-node-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-runtimeclass-v1alpha1-node-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#scheduling-v1beta1-node-k8s-io" class="nav-item">Scheduling v1beta1 node.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#scheduling-v1alpha1-node-k8s-io" class="nav-item">Scheduling v1alpha1 node.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">ServiceAccountSubject v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#servicereference-v1-apiextensions-k8s-io" class="nav-item">ServiceReference v1 apiextensions.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#servicereference-v1-apiregistration-k8s-io" class="nav-item">ServiceReference v1 apiregistration.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#subject-v1-rbac-authorization-k8s-io" class="nav-item">Subject v1 rbac.authorization.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#subject-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">Subject v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#tokenrequest-v1-storage-k8s-io" class="nav-item">TokenRequest v1 storage.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#usersubject-v1beta1-flowcontrol-apiserver-k8s-io" class="nav-item">UserSubject v1beta1 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#webhookclientconfig-v1-apiextensions-k8s-io" class="nav-item">WebhookClientConfig v1 apiextensions.k8s.io</A></LI>
+</UL>
+</DIV>
+<DIV id="page-content-wrapper" class="col-xs-8 offset-xs-4 col-sm-9 offset-sm-3 col-md-10 offset-md-2 body-content">
+<DIV class="row">
+  <DIV class="col-md-6 copyright">
+ <a href="https://github.com/kubernetes/kubernetes">Copyright 2016-2021 The Kubernetes Authors.</a>
+  </DIV>
+  <DIV class="col-md-6 text-right">
+    <DIV>Generated at: 2021-12-07 16:19:07 (EST)</DIV>
+    <DIV>API Version: <a href="https://github.com/kubernetes/kubernetes/blob/release-1.23/api/openapi-spec/swagger.json">v1.23.0</a></DIV>
+  </DIV>
+</DIV><H1 id="-strong-api-overview-strong-"><STRONG>API OVERVIEW</STRONG></H1>
+
+<P>Welcome to the Kubernetes API.  You can use the Kubernetes API to read
+and write Kubernetes resource objects via a Kubernetes API endpoint.</P>
+
+<H2 id="resource-categories">Resource Categories</H2>
+
+<P>This is a high-level overview of the basic types of resources provide by the Kubernetes API and their primary functions.</P>
+<P><B>Workloads</B> are objects you use to manage and run your containers on the cluster.</P>
+<P><B>Discovery &amp; LB</B> resources are objects you use to "stitch" your workloads together into an externally accessible, load-balanced Service.</P>
+<P><B>Config &amp; Storage</B> resources are objects you use to inject initialization data into your applications, and to persist data that is external to your container.</P>
+<P><B>Cluster</B> resources objects define how the cluster itself is configured; these are typically used only by cluster operators.</P>
+<P><B>Metadata</B> resources are objects you use to configure the behavior of other resources within the cluster, such as <code>HorizontalPodAutoscaler</code> for scaling workloads.</P>
+
+<HR />
+
+<H2 id="resource-objects">Resource Objects</H2>
+
+<P>Resource objects typically have 3 components:</P>
+<UL>
+<LI><B>Resource ObjectMeta</B>: This is metadata about the resource, such as its name, type, api version, annotations, and labels.  This contains
+fields that maybe updated both by the end user and the system (e.g. annotations).</LI>
+<LI><B>ResourceSpec</B>: This is defined by the user and describes the desired state of system.  Fill this in when creating or updating an object.</LI>
+<LI><B>ResourceStatus</B>: This is filled in by the server and reports the current state of the system.  In most cases, users don't need to change this.</LI>
+</UL>
+
+<HR />
+
+<H2 id="resource-operations">Resource Operations</H2>
+
+<P>Most resources provide the following Operations:</P>
+
+<H4 id="resource-operations-create">Create</H4>
+
+<P>Create operations will create the resource in the storage backend.  After a resource is create the system will apply
+the desired state.</P>
+
+<H4 id="resource-operations-update">Update</H4>
+
+<P>Updates come in 2 forms: <B>Replace</B> and <B>Patch</B>:
+
+<UL>
+<LI><B>Replace</B>:
+Replacing a resource object will update the resource by replacing the existing spec with the provided one.  For
+read-then-write operations this is safe because an optimistic lock failure will occur if the resource was modified
+between the read and write. <I>Note</I>: The <I>ResourceStatus</I> will be ignored by the system and will not be updated.
+To update the status, one must invoke the specific status update operation.<BR />
+
+Note: Replacing a resource object may not result immediately in changes being propagated to downstream objects.  For instance
+replacing a <CODE>ConfigMap</CODE> or <CODE>Secret</CODE> resource will not result in all <I>Pod</I>s seeing the changes unless the <I>Pod</I>s are
+restarted out of band.</P></LI>
+
+<LI><B>Patch</B>:
+Patch will apply a change to a specific field.  How the change is merged is defined per field.  Lists may either be
+replaced or merged.  Merging lists will not preserve ordering.<BR />
+
+<B>Patches will never cause optimistic locking failures, and the last write will win.</B>  Patches are recommended
+when the full state is not read before an update, or when failing on optimistic locking is undesirable. <I>When patching
+complex types, arrays and maps, how the patch is applied is defined on a per-field basis and may either replace
+the field's current value, or merge the contents into the current value.</I></LI>
+</UL>
+
+<H4 id="resource-operations-read">Read</H4>
+
+<P>Reads come in 3 forms: <B>Get</B>, <B>List</B> and <B>Watch</B>:<P>
+
+<UL>
+<LI><B>Get</B>: Get will retrieve a specific resource object by name.</LI>
+<LI><B>List</B>: List will retrieve all resource objects of a specific type within a namespace, and the results can be restricted to resources matching a selector query.<BR />
+<B>List All Namespaces</B>: Like <B>List</B> but retrieves resources across all namespaces.</LI>
+<LI><B>Watch</B>: Watch will stream results for an object(s) as it is updated.  Similar to a callback, watch is used to respond to resource changes.</LI>
+</UL>
+
+<H4 id="resource-operations-read">Delete</H4>
+
+<P>Delete will delete a resource.  Depending on the specific resource, child objects may or may not be garbage collected by the server.  See
+notes on specific resource objects for details.</P>
+
+<H4 id="resource-operations-additional">Additional Operations</H4>
+
+<P>Resources may define additional operations specific to that resource type.</P>
+
+<UL>
+	<LI><B>Rollback</B>: Rollback a PodTemplate to a previous version.  Only available for some resource types.</LI>
+	<LI><B>Read / Write Scale</B>: Read or Update the number of replicas for the given resource.  Only available for some resource types.</LI>
+	<LI><B>Read / Write Status</B>: Read or Update the Status for a resource object.  The Status can only changed through these update operations.</LI>
+</UL>
+<HR />
+<H1 id="-strong-api-groups-strong-"><STRONG>API Groups</STRONG></H1>
+<P>The API Groups and their versions are summarized in the following table.</P><TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1, v2, v2beta2, v2beta1</CODE></TD></TR>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-workloads-apis-strong-"><STRONG>WORKLOADS</STRONG></H1>
+
+<P>Workloads resources are responsible for managing and running your containers on the cluster. <A href="#container-v1-core">Containers</A> are created
+by Controllers through <A href="#pod-v1-core">Pods</A>. Pods run Containers and provide environmental dependencies such as shared or
+persistent storage <A href="#volume-v1-core">Volumes</A> and <A href="#configmap-v1-core">Configuration</A> or <A href="#secret-v1-core">Secret</A>
+data injected into the container.</P>
+
+<P>The most common Controllers are:</P>
+<UL>
+<LI><A href="#deployment-v1-apps">Deployments</A> for stateless persistent apps (e.g. HTTP servers).</LI>
+<LI><A href="#statefulset-v1-apps">StatefulSets</A> for stateful persistent apps (e.g. databases).</LI>
+<LI><A href="#job-v1-batch">Jobs</A> for run-to-completion apps (e.g. batch Jobs).</LI>
+</UL>
+
+<HR />
+<H1 id="container-v1-core">Container v1 core</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-container-v1-core" aria-controls="example-container-v1-core"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-container-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Container Config to run nginx (must be embedded in a PodSpec to run).</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+name: nginx
+# Run the nginx:1.14 image
+image: nginx:1.14
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Container</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>Containers are only ever created within the context of a <a href="#pod-v1-core">Pod</a>.  This is usually done using a Controller.  See Controllers: <a href="#deployment-v1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1-apps">StatefulSet</a></P></DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>args</CODE><BR /><I>string array</I></TD><TD>Arguments to the entrypoint. The docker image&#39;s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
+<TR><TD><CODE>command</CODE><BR /><I>string array</I></TD><TD>Entrypoint array. Not executed within a shell. The docker image&#39;s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
+<TR><TD><CODE>env</CODE><BR /><I><a href="#envvar-v1-core">EnvVar</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of environment variables to set in the container. Cannot be updated.</TD></TR>
+<TR><TD><CODE>envFrom</CODE><BR /><I><a href="#envfromsource-v1-core">EnvFromSource</a> array</I></TD><TD>List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.</TD></TR>
+<TR><TD><CODE>imagePullPolicy</CODE><BR /><I>string</I></TD><TD>Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images  Possible enum values:  - `&#34;Always&#34;` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `&#34;IfNotPresent&#34;` means that kubelet pulls if the image isn&#39;t present on disk. Container will fail if the image isn&#39;t present and the pull fails.  - `&#34;Never&#34;` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn&#39;t present</TD></TR>
+<TR><TD><CODE>lifecycle</CODE><BR /><I><a href="#lifecycle-v1-core">Lifecycle</a></I></TD><TD>Actions that the management system should take in response to container lifecycle events. Cannot be updated.</TD></TR>
+<TR><TD><CODE>livenessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#containerport-v1-core">ContainerPort</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>containerPort</I></TD><TD>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 &#34;0.0.0.0&#34; address inside a container will be accessible from the network. Cannot be updated.</TD></TR>
+<TR><TD><CODE>readinessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
+<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#securitycontext-v1-core">SecurityContext</a></I></TD><TD>SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
+<TR><TD><CODE>startupProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod&#39;s lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
+<TR><TD><CODE>stdin</CODE><BR /><I>boolean</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>stdinOnce</CODE><BR /><I>boolean</I></TD><TD>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</TD></TR>
+<TR><TD><CODE>terminationMessagePath</CODE><BR /><I>string</I></TD><TD>Optional: Path at which the file to which the container&#39;s termination message will be written is mounted into the container&#39;s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.</TD></TR>
+<TR><TD><CODE>terminationMessagePolicy</CODE><BR /><I>string</I></TD><TD>Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.  Possible enum values:  - `&#34;FallbackToLogsOnError&#34;` will read the most recent contents of the container logs for the container status message when the container exits with an error and the terminationMessagePath has no contents.  - `&#34;File&#34;` is the default behavior and will set the container status message to the contents of the container&#39;s terminationMessagePath when the container exits.</TD></TR>
+<TR><TD><CODE>tty</CODE><BR /><I>boolean</I></TD><TD>Whether this container should allocate a TTY for itself, also requires &#39;stdin&#39; to be true. Default is false.</TD></TR>
+<TR><TD><CODE>volumeDevices</CODE><BR /><I><a href="#volumedevice-v1-core">VolumeDevice</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>devicePath</I></TD><TD>volumeDevices is the list of block devices to be used by the container.</TD></TR>
+<TR><TD><CODE>volumeMounts</CODE><BR /><I><a href="#volumemount-v1-core">VolumeMount</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>mountPath</I></TD><TD>Pod volumes to mount into the container&#39;s filesystem. Cannot be updated.</TD></TR>
+<TR><TD><CODE>workingDir</CODE><BR /><I>string</I></TD><TD>Container&#39;s working directory. If not specified, the container runtime&#39;s default will be used, which might be configured in the container image. Cannot be updated.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="containerstatus-v1-core">ContainerStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>Container&#39;s ID in the format &#39;docker://&lt;container_id&gt;&#39;.</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.</TD></TR>
+<TR><TD><CODE>imageID</CODE><BR /><I>string</I></TD><TD>ImageID of the container&#39;s image.</TD></TR>
+<TR><TD><CODE>lastState</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>Details about the container&#39;s last termination condition.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.</TD></TR>
+<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>Specifies whether the container has passed its readiness probe.</TD></TR>
+<TR><TD><CODE>restartCount</CODE><BR /><I>integer</I></TD><TD>The number of times the container has been restarted.</TD></TR>
+<TR><TD><CODE>started</CODE><BR /><I>boolean</I></TD><TD>Specifies whether the container has passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. Is always true when no startupProbe is defined.</TD></TR>
+<TR><TD><CODE>state</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>Details about the container&#39;s current condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="cronjob-v1-batch">CronJob v1 batch</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CronJob</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#cronjob-v1beta1-batch">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjoblist-v1-batch">CronJobList [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#cronjobspec-v1-batch">CronJobSpec</a></I></TD><TD>Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#cronjobstatus-v1-batch">CronJobStatus</a></I></TD><TD>Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjobspec-v1-batch">CronJobSpec v1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjob-v1-batch">CronJob [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>concurrencyPolicy</CODE><BR /><I>string</I></TD><TD>Specifies how to treat concurrent executions of a Job. Valid values are: - &#34;Allow&#34; (default): allows CronJobs to run concurrently; - &#34;Forbid&#34;: forbids concurrent runs, skipping next run if previous run hasn&#39;t finished yet; - &#34;Replace&#34;: cancels currently running job and replaces it with a new one  Possible enum values:  - `&#34;Allow&#34;` allows CronJobs to run concurrently.  - `&#34;Forbid&#34;` forbids concurrent runs, skipping next run if previous hasn&#39;t finished yet.  - `&#34;Replace&#34;` cancels currently running job and replaces it with a new one.</TD></TR>
+<TR><TD><CODE>failedJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1.</TD></TR>
+<TR><TD><CODE>jobTemplate</CODE><BR /><I><a href="#jobtemplatespec-v1-batch">JobTemplateSpec</a></I></TD><TD>Specifies the job that will be created when executing a CronJob.</TD></TR>
+<TR><TD><CODE>schedule</CODE><BR /><I>string</I></TD><TD>The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.</TD></TR>
+<TR><TD><CODE>startingDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>successfulJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.</TD></TR>
+<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>This flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjobstatus-v1-batch">CronJobStatus v1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjob-v1-batch">CronJob [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>active</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I></TD><TD>A list of pointers to currently running jobs.</TD></TR>
+<TR><TD><CODE>lastScheduleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job was successfully scheduled.</TD></TR>
+<TR><TD><CODE>lastSuccessfulTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job successfully completed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjoblist-v1-batch">CronJobList v1 batch</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#cronjob-v1-batch">CronJob</a> array</I></TD><TD>items is the list of CronJobs.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-cronjob-v1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-cronjob-v1-batch">Create</H2>
+<P>create a CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-cronjob-v1-batch">Patch</H2>
+<P>partially update the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-cronjob-v1-batch">Replace</H2>
+<P>replace the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-cronjob-v1-batch">Delete</H2>
+<P>delete a CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-cronjob-v1-batch">Delete Collection</H2>
+<P>delete collection of CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-cronjob-v1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-cronjob-v1-batch">Read</H2>
+<P>read the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-cronjob-v1-batch">List</H2>
+<P>list or watch objects of kind CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjoblist-v1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-cronjob-v1-batch">List All Namespaces</H2>
+<P>list or watch objects of kind CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/cronjobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjoblist-v1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-cronjob-v1-batch">Watch</H2>
+<P>watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-cronjob-v1-batch">Watch List</H2>
+<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-cronjob-v1-batch">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/cronjobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-cronjob-v1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-cronjob-v1-batch">Patch Status</H2>
+<P>partially update status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-cronjob-v1-batch">Read Status</H2>
+<P>read status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-cronjob-v1-batch">Replace Status</H2>
+<P>replace status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="daemonset-v1-apps">DaemonSet v1 apps</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-daemonset-v1-apps" aria-controls="example-daemonset-v1-apps"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">DaemonSet Config to print the `hostname` on each Node in the cluster every 10 seconds.</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  # Unique key of the DaemonSet instance
+  name: daemonset-example
+spec:
+  selector:
+    matchLabels:
+      app: daemonset-example
+  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 &lt;script&gt;`
+        - &gt;-
+          while [ true ]; do
+          echo &#34;DaemonSet running on $(hostname)&#34; ;
+          sleep 10 ;
+          done
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSet</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonsetlist-v1-apps">DaemonSetList [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#daemonsetspec-v1-apps">DaemonSetSpec</a></I></TD><TD>The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#daemonsetstatus-v1-apps">DaemonSetStatus</a></I></TD><TD>The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="daemonsetspec-v1-apps">DaemonSetSpec v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).</TD></TR>
+<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template&#39;s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
+<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy</a></I></TD><TD>An update strategy to replace existing DaemonSet pods with new pods.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="daemonsetstatus-v1-apps">DaemonSetStatus v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#daemonsetcondition-v1-apps">DaemonSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a DaemonSet&#39;s current state.</TD></TR>
+<TR><TD><CODE>currentNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
+<TR><TD><CODE>desiredNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
+<TR><TD><CODE>numberAvailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
+<TR><TD><CODE>numberMisscheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
+<TR><TD><CODE>numberReady</CODE><BR /><I>integer</I></TD><TD>numberReady is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running with a Ready Condition.</TD></TR>
+<TR><TD><CODE>numberUnavailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The most recent generation observed by the daemon set controller.</TD></TR>
+<TR><TD><CODE>updatedNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that are running updated daemon pod</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="daemonsetlist-v1-apps">DaemonSetList v1 apps</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#daemonset-v1-apps">DaemonSet</a> array</I></TD><TD>A list of daemon sets.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="rollingupdatedaemonset-v1-apps">RollingUpdateDaemonSet v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption. This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.</TD></TR>
+<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-daemonset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-daemonset-v1-apps">Create</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-create-daemonset-v1-apps" aria-controls="req-kubectl-create-daemonset-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-create-daemonset-v1-apps" aria-controls="req-curl-create-daemonset-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-create-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: daemonset-example
+spec:
+  selector:
+    matchLabels:
+      app: daemonset-example
+  template:
+    metadata:
+      labels:
+        app: daemonset-example
+    spec:
+      containers:
+      - name: daemonset-example
+        image: ubuntu:trusty
+        command:
+        - /bin/sh
+        args:
+        - -c
+        - >-
+          while [ true ]; do
+          echo "DaemonSet running on $(hostname)" ;
+          sleep 10 ;
+          done
+' | kubectl create -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-create-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X POST -H 'Content-Type: application/yaml' --data '
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: daemonset-example
+spec:
+  selector:
+    matchLabels:
+      app: daemonset-example
+  template:
+    metadata:
+      labels:
+        app: daemonset-example
+    spec:
+      containers:
+      - name: daemonset-example
+        image: ubuntu:trusty
+        command:
+        - /bin/sh
+        args:
+        - -c
+        - >-
+          while [ true ]; do
+          echo "DaemonSet running on $(hostname)" ;
+          sleep 10 ;
+          done
+' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-create-daemonset-v1-apps" aria-controls="res-kubectl-create-daemonset-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-create-daemonset-v1-apps" aria-controls="res-curl-create-daemonset-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-create-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+daemonset "daemonset-example" created
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-create-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "DaemonSet",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "daemonset-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/daemonsets/daemonset-example",
+    "uid": "65552ced-b0e2-11e6-aef0-42010af00229",
+    "resourceVersion": "3558",
+    "generation": 1,
+    "creationTimestamp": "2016-11-22T18:35:09Z",
+    "labels": {
+      "app": "daemonset-example"
+    }
+  },
+  "spec": {
+    "selector": {
+      "matchLabels": {
+        "app": "daemonset-example"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "daemonset-example"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "daemonset-example",
+            "image": "ubuntu:trusty",
+            "command": [
+              "/bin/sh"
+            ],
+            "args": [
+              "-c",
+              "while [ true ]; do echo \"DaemonSet running on $(hostname)\" ; sleep 10 ; done"
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    }
+  },
+  "status": {
+    "currentNumberScheduled": 0,
+    "numberMisscheduled": 0,
+    "desiredNumberScheduled": 0
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>create a DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-daemonset-v1-apps">Patch</H2>
+<P>partially update the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-daemonset-v1-apps">Replace</H2>
+<P>replace the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-daemonset-v1-apps">Delete</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-delete-daemonset-v1-apps" aria-controls="req-kubectl-delete-daemonset-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-delete-daemonset-v1-apps" aria-controls="req-curl-delete-daemonset-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-delete-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl delete daemonset daemonset-example
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-delete-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
+gracePeriodSeconds: 0
+orphanDependents: false
+' 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-delete-daemonset-v1-apps" aria-controls="res-kubectl-delete-daemonset-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-delete-daemonset-v1-apps" aria-controls="res-curl-delete-daemonset-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-delete-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+daemonset "daemonset-example" deleted
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-delete-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Status",
+  "apiVersion": "v1",
+  "metadata": {},
+  "status": "Success",
+  "code": 200
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>delete a DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-daemonset-v1-apps">Delete Collection</H2>
+<P>delete collection of DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-daemonset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-daemonset-v1-apps">Read</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-read-daemonset-v1-apps" aria-controls="req-kubectl-read-daemonset-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-read-daemonset-v1-apps" aria-controls="req-curl-read-daemonset-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-read-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get daemonset daemonset-example -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-read-daemonset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
+</CODE></PRE></DIV></DIV></DIV>
+<P>read the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-daemonset-v1-apps">List</H2>
+<P>list or watch objects of kind DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonsetlist-v1-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-daemonset-v1-apps">List All Namespaces</H2>
+<P>list or watch objects of kind DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/daemonsets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonsetlist-v1-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-daemonset-v1-apps">Watch</H2>
+<P>watch changes to an object of kind DaemonSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-daemonset-v1-apps">Watch List</H2>
+<P>watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-daemonset-v1-apps">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/daemonsets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-daemonset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-daemonset-v1-apps">Patch Status</H2>
+<P>partially update status of the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-daemonset-v1-apps">Read Status</H2>
+<P>read status of the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-daemonset-v1-apps">Replace Status</H2>
+<P>replace status of the specified DaemonSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="deployment-v1-apps">Deployment v1 apps</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-deployment-v1-apps" aria-controls="example-deployment-v1-apps"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Deployment Config to run 3 nginx instances (max rollback set to 10 revisions).</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  # Unique key of the Deployment instance
+  name: deployment-example
+spec:
+  # 3 Pods should exist at all times.
+  replicas: 3
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        # Apply this label to pods and default
+        # the Deployment label selector to this value
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        # Run this image
+        image: nginx:1.14
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Deployment</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deploymentlist-v1-apps">DeploymentList [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#deploymentspec-v1-apps">DeploymentSpec</a></I></TD><TD>Specification of the desired behavior of the Deployment.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#deploymentstatus-v1-apps">DeploymentStatus</a></I></TD><TD>Most recently observed status of the Deployment.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="deploymentspec-v1-apps">DeploymentSpec v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
+<TR><TD><CODE>paused</CODE><BR /><I>boolean</I></TD><TD>Indicates that the deployment is paused.</TD></TR>
+<TR><TD><CODE>progressDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
+<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template&#39;s labels.</TD></TR>
+<TR><TD><CODE>strategy</CODE><BR /><I><a href="#deploymentstrategy-v1-apps">DeploymentStrategy</a></I><BR /><B>patch strategy</B>: <I>retainKeys</I></TD><TD>The deployment strategy to use to replace existing pods with new ones.</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template describes the pods that will be created.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="deploymentstatus-v1-apps">DeploymentStatus v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.</TD></TR>
+<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#deploymentcondition-v1-apps">DeploymentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a deployment&#39;s current state.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the deployment controller.</TD></TR>
+<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of pods targeted by this Deployment with a Ready Condition.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment (their labels match the selector).</TD></TR>
+<TR><TD><CODE>unavailableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.</TD></TR>
+<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment that have the desired template spec.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="deploymentlist-v1-apps">DeploymentList v1 apps</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#deployment-v1-apps">Deployment</a> array</I></TD><TD>Items is the list of Deployments.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="deploymentstrategy-v1-apps">DeploymentStrategy v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedeployment-v1-apps">RollingUpdateDeployment</a></I></TD><TD>Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment. Can be &#34;Recreate&#34; or &#34;RollingUpdate&#34;. Default is RollingUpdate.  Possible enum values:  - `&#34;Recreate&#34;` Kill all existing pods before creating new ones.  - `&#34;RollingUpdate&#34;` Replace the old ReplicaSets by new one using rolling update i.e gradually scale down the old ReplicaSets and scale up the new one.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="rollingupdatedeployment-v1-apps">RollingUpdateDeployment v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deploymentstrategy-v1-apps">DeploymentStrategy [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.</TD></TR>
+<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-deployment-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-deployment-v1-apps">Create</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-create-deployment-v1-apps" aria-controls="req-kubectl-create-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-create-deployment-v1-apps" aria-controls="req-curl-create-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-create-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: deployment-example
+spec:
+  replicas: 3
+  revisionHistoryLimit: 10
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.14
+        ports:
+        - containerPort: 80
+' | kubectl create -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-create-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X POST -H 'Content-Type: application/yaml' --data '
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: deployment-example
+spec:
+  replicas: 3
+  revisionHistoryLimit: 10
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.14
+        ports:
+        - containerPort: 80
+' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-create-deployment-v1-apps" aria-controls="res-kubectl-create-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-create-deployment-v1-apps" aria-controls="res-curl-create-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-create-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+deployment "deployment-example" created
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-create-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Deployment",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+    "uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
+    "resourceVersion": "2118306",
+    "generation": 1,
+    "creationTimestamp": "2016-10-28T01:53:19Z",
+    "labels": {
+      "app": "nginx"
+    }
+  },
+  "spec": {
+    "replicas": 3,
+    "selector": {
+      "matchLabels": {
+        "app": "nginx"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "nginx"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "nginx",
+            "image": "nginx:1.14",
+            "ports": [
+              {
+                "containerPort": 80,
+                "protocol": "TCP"
+              }
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    },
+    "strategy": {
+      "type": "RollingUpdate",
+      "rollingUpdate": {
+        "maxUnavailable": 1,
+        "maxSurge": 1
+      }
+    },
+    "revisionHistoryLimit": 10
+  },
+  "status": {}
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>create a Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-deployment-v1-apps">Patch</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-patch-deployment-v1-apps" aria-controls="req-kubectl-patch-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-patch-deployment-v1-apps" aria-controls="req-curl-patch-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-patch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl patch deployment deployment-example -p \
+	'{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.16"}]}}}}'
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-patch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
+{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.16"}]}}}}' \
+	'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-patch-deployment-v1-apps" aria-controls="res-kubectl-patch-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-patch-deployment-v1-apps" aria-controls="res-curl-patch-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-patch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+"deployment-example" patched
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-patch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Deployment",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+    "uid": "5dc3a8e6-b0ee-11e6-aef0-42010af00229",
+    "resourceVersion": "164489",
+    "generation": 11,
+    "creationTimestamp": "2016-11-22T20:00:50Z",
+    "labels": {
+      "app": "nginx"
+    },
+    "annotations": {
+      "deployment.kubernetes.io/revision": "5"
+    }
+  },
+  "spec": {
+    "replicas": 3,
+    "selector": {
+      "matchLabels": {
+        "app": "nginx"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "nginx"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "nginx",
+            "image": "nginx:1.16",
+            "ports": [
+              {
+                "containerPort": 80,
+                "protocol": "TCP"
+              }
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    },
+    "strategy": {
+      "type": "RollingUpdate",
+      "rollingUpdate": {
+        "maxUnavailable": 1,
+        "maxSurge": 1
+      }
+    },
+    "revisionHistoryLimit": 10
+  },
+  "status": {
+    "observedGeneration": 10,
+    "replicas": 3,
+    "updatedReplicas": 3,
+    "availableReplicas": 3
+  }
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>partially update the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-deployment-v1-apps">Replace</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-replace-deployment-v1-apps" aria-controls="req-kubectl-replace-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-replace-deployment-v1-apps" aria-controls="req-curl-replace-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-replace-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: deployment-example
+spec:
+  replicas: 3
+  revisionHistoryLimit: 10
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.16
+        ports:
+        - containerPort: 80
+' | kubectl replace -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-replace-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X PUT -H 'Content-Type: application/yaml' --data '
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: deployment-example
+spec:
+  replicas: 3
+  revisionHistoryLimit: 10
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.16
+        ports:
+        - containerPort: 80
+' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-replace-deployment-v1-apps" aria-controls="res-kubectl-replace-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-replace-deployment-v1-apps" aria-controls="res-curl-replace-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-replace-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+deployment "deployment-example" replaced
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-replace-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Deployment",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+    "uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
+    "resourceVersion": "2119082",
+    "generation": 5,
+    "creationTimestamp": "2016-10-28T01:53:19Z",
+    "labels": {
+      "app": "nginx"
+    }
+  },
+  "spec": {
+    "replicas": 3,
+    "selector": {
+      "matchLabels": {
+        "app": "nginx"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "nginx"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "nginx",
+            "image": "nginx:1.16",
+            "ports": [
+              {
+                "containerPort": 80,
+                "protocol": "TCP"
+              }
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    },
+    "strategy": {
+      "type": "RollingUpdate",
+      "rollingUpdate": {
+        "maxUnavailable": 1,
+        "maxSurge": 1
+      }
+    },
+    "revisionHistoryLimit": 10
+  },
+  "status": {
+    "observedGeneration": 4,
+    "replicas": 3,
+    "updatedReplicas": 3,
+    "availableReplicas": 3
+  }
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>replace the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-deployment-v1-apps">Delete</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-delete-deployment-v1-apps" aria-controls="req-kubectl-delete-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-delete-deployment-v1-apps" aria-controls="req-curl-delete-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-delete-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl delete deployment deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-delete-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
+gracePeriodSeconds: 0
+orphanDependents: false
+' 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-delete-deployment-v1-apps" aria-controls="res-kubectl-delete-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-delete-deployment-v1-apps" aria-controls="res-curl-delete-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-delete-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+deployment "deployment-example" deleted
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-delete-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Status",
+  "apiVersion": "v1",
+  "metadata": {},
+  "status": "Success",
+  "code": 200
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>delete a Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-deployment-v1-apps">Delete Collection</H2>
+<P>delete collection of Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-deployment-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-deployment-v1-apps">Read</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-read-deployment-v1-apps" aria-controls="req-kubectl-read-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-read-deployment-v1-apps" aria-controls="req-curl-read-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-read-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get deployment deployment-example -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-read-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-read-deployment-v1-apps" aria-controls="res-kubectl-read-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-read-deployment-v1-apps" aria-controls="res-curl-read-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-read-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+  "kind": "Deployment",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+    "uid": "1b33145a-9c63-11e6-9c54-42010a800148",
+    "resourceVersion": "2064726",
+    "generation": 4,
+    "creationTimestamp": "2016-10-27T16:33:35Z",
+    "labels": {
+      "app": "nginx"
+    },
+    "annotations": {
+      "deployment.kubernetes.io/revision": "1"
+    }
+  },
+  "spec": {
+    "replicas": 3,
+    "selector": {
+      "matchLabels": {
+        "app": "nginx"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "nginx"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "nginx",
+            "image": "nginx:1.14",
+            "ports": [
+              {
+                "containerPort": 80,
+                "protocol": "TCP"
+              }
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    },
+    "strategy": {
+      "type": "RollingUpdate",
+      "rollingUpdate": {
+        "maxUnavailable": 1,
+        "maxSurge": 1
+      }
+    }
+  },
+  "status": {
+    "observedGeneration": 4,
+    "replicas": 3,
+    "updatedReplicas": 3,
+    "availableReplicas": 3
+  }
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-read-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Deployment",
+  "apiVersion": "apps/v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+    "uid": "1b33145a-9c63-11e6-9c54-42010a800148",
+    "resourceVersion": "2064726",
+    "generation": 4,
+    "creationTimestamp": "2016-10-27T16:33:35Z",
+    "labels": {
+      "app": "nginx"
+    },
+    "annotations": {
+      "deployment.kubernetes.io/revision": "1"
+    }
+  },
+  "spec": {
+    "replicas": 3,
+    "selector": {
+      "matchLabels": {
+        "app": "nginx"
+      }
+    },
+    "template": {
+      "metadata": {
+        "creationTimestamp": null,
+        "labels": {
+          "app": "nginx"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "nginx",
+            "image": "nginx:1.14",
+            "ports": [
+              {
+                "containerPort": 80,
+                "protocol": "TCP"
+              }
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "IfNotPresent"
+          }
+        ],
+        "restartPolicy": "Always",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    },
+    "strategy": {
+      "type": "RollingUpdate",
+      "rollingUpdate": {
+        "maxUnavailable": 1,
+        "maxSurge": 1
+      }
+    }
+  },
+  "status": {
+    "observedGeneration": 4,
+    "replicas": 3,
+    "updatedReplicas": 3,
+    "availableReplicas": 3
+  }
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>read the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-deployment-v1-apps">List</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-list-deployment-v1-apps" aria-controls="req-kubectl-list-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-list-deployment-v1-apps" aria-controls="req-curl-list-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-list-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get deployment -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-list-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-list-deployment-v1-apps" aria-controls="res-kubectl-list-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-list-deployment-v1-apps" aria-controls="res-curl-list-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-list-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+  "kind": "List",
+  "apiVersion": "v1",
+  "metadata": {},
+  "items": [
+    {
+      "kind": "Deployment",
+      "apiVersion": "app/v1beta1",
+      "metadata": {
+        "name": "docs",
+        "namespace": "default",
+        "selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
+        "uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
+        "resourceVersion": "1924126",
+        "generation": 21,
+        "creationTimestamp": "2016-10-13T16:06:00Z",
+        "labels": {
+          "run": "docs"
+        },
+        "annotations": {
+          "deployment.kubernetes.io/revision": "10",
+          "replicatingperfection.net/push-image": "true"
+        }
+      },
+      "spec": {
+        "replicas": 1,
+        "selector": {
+          "matchLabels": {
+            "run": "docs"
+          }
+        },
+        "template": {
+          "metadata": {
+            "creationTimestamp": null,
+            "labels": {
+              "auto-pushed-image-pwittrock/api-docs": "1477496453",
+              "run": "docs"
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "docs",
+                "image": "pwittrock/api-docs:v9",
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "Always"
+              }
+            ],
+            "restartPolicy": "Always",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        },
+        "strategy": {
+          "type": "RollingUpdate",
+          "rollingUpdate": {
+            "maxUnavailable": 1,
+            "maxSurge": 1
+          }
+        }
+      },
+      "status": {
+        "observedGeneration": 21,
+        "replicas": 1,
+        "updatedReplicas": 1,
+        "availableReplicas": 1
+      }
+    },
+    {
+      "kind": "Deployment",
+      "apiVersion": "app/v1beta1",
+      "metadata": {
+        "name": "deployment-example",
+        "namespace": "default",
+        "selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
+        "uid": "1b33145a-9c63-11e6-9c54-42010a800148",
+        "resourceVersion": "2064726",
+        "generation": 4,
+        "creationTimestamp": "2016-10-27T16:33:35Z",
+        "labels": {
+          "app": "nginx"
+        },
+        "annotations": {
+          "deployment.kubernetes.io/revision": "1"
+        }
+      },
+      "spec": {
+        "replicas": 3,
+        "selector": {
+          "matchLabels": {
+            "app": "nginx"
+          }
+        },
+        "template": {
+          "metadata": {
+            "creationTimestamp": null,
+            "labels": {
+              "app": "nginx"
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "nginx",
+                "image": "nginx:1.14",
+                "ports": [
+                  {
+                    "containerPort": 80,
+                    "protocol": "TCP"
+                  }
+                ],
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "IfNotPresent"
+              }
+            ],
+            "restartPolicy": "Always",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        },
+        "strategy": {
+          "type": "RollingUpdate",
+          "rollingUpdate": {
+            "maxUnavailable": 1,
+            "maxSurge": 1
+          }
+        }
+      },
+      "status": {
+        "observedGeneration": 4,
+        "replicas": 3,
+        "updatedReplicas": 3,
+        "availableReplicas": 3
+      }
+    }
+  ]
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-list-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "List",
+  "apiVersion": "v1",
+  "metadata": {},
+  "items": [
+    {
+      "kind": "Deployment",
+      "apiVersion": "app/v1beta1",
+      "metadata": {
+        "name": "docs",
+        "namespace": "default",
+        "selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
+        "uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
+        "resourceVersion": "1924126",
+        "generation": 21,
+        "creationTimestamp": "2016-10-13T16:06:00Z",
+        "labels": {
+          "run": "docs"
+        },
+        "annotations": {
+          "deployment.kubernetes.io/revision": "10",
+          "replicatingperfection.net/push-image": "true"
+        }
+      },
+      "spec": {
+        "replicas": 1,
+        "selector": {
+          "matchLabels": {
+            "run": "docs"
+          }
+        },
+        "template": {
+          "metadata": {
+            "creationTimestamp": null,
+            "labels": {
+              "auto-pushed-image-pwittrock/api-docs": "1477496453",
+              "run": "docs"
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "docs",
+                "image": "pwittrock/api-docs:v9",
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "Always"
+              }
+            ],
+            "restartPolicy": "Always",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        },
+        "strategy": {
+          "type": "RollingUpdate",
+          "rollingUpdate": {
+            "maxUnavailable": 1,
+            "maxSurge": 1
+          }
+        }
+      },
+      "status": {
+        "observedGeneration": 21,
+        "replicas": 1,
+        "updatedReplicas": 1,
+        "availableReplicas": 1
+      }
+    },
+    {
+      "kind": "Deployment",
+      "apiVersion": "app/v1beta1",
+      "metadata": {
+        "name": "deployment-example",
+        "namespace": "default",
+        "selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
+        "uid": "1b33145a-9c63-11e6-9c54-42010a800148",
+        "resourceVersion": "2064726",
+        "generation": 4,
+        "creationTimestamp": "2016-10-27T16:33:35Z",
+        "labels": {
+          "app": "nginx"
+        },
+        "annotations": {
+          "deployment.kubernetes.io/revision": "1"
+        }
+      },
+      "spec": {
+        "replicas": 3,
+        "selector": {
+          "matchLabels": {
+            "app": "nginx"
+          }
+        },
+        "template": {
+          "metadata": {
+            "creationTimestamp": null,
+            "labels": {
+              "app": "nginx"
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "nginx",
+                "image": "nginx:1.14",
+                "ports": [
+                  {
+                    "containerPort": 80,
+                    "protocol": "TCP"
+                  }
+                ],
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "IfNotPresent"
+              }
+            ],
+            "restartPolicy": "Always",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        },
+        "strategy": {
+          "type": "RollingUpdate",
+          "rollingUpdate": {
+            "maxUnavailable": 1,
+            "maxSurge": 1
+          }
+        }
+      },
+      "status": {
+        "observedGeneration": 4,
+        "replicas": 3,
+        "updatedReplicas": 3,
+        "availableReplicas": 3
+      }
+    }
+  ]
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>list or watch objects of kind Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deploymentlist-v1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-deployment-v1-apps">List All Namespaces</H2>
+<P>list or watch objects of kind Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/deployments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deploymentlist-v1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-deployment-v1-apps">Watch</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-watch-deployment-v1-apps" aria-controls="req-kubectl-watch-deployment-v1-apps"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-watch-deployment-v1-apps" aria-controls="req-curl-watch-deployment-v1-apps"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-watch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get deployment deployment-example --watch -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-watch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/watch/namespaces/default/deployments/deployment-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-watch-deployment-v1-apps" aria-controls="res-kubectl-watch-deployment-v1-apps"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-watch-deployment-v1-apps" aria-controls="res-curl-watch-deployment-v1-apps"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-watch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Deployment",
+		"apiVersion": "apps/v1",
+		"metadata": {
+			"name": "deployment-example",
+			"namespace": "default",
+			"selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+			"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
+			"resourceVersion": "2128095",
+			"generation": 2,
+			"creationTimestamp": "2016-10-28T03:34:12Z",
+			"labels": {
+				"app": "nginx"
+			},
+			"annotations": {
+				"deployment.kubernetes.io/revision": "3"
+			}
+		},
+		"spec": {
+			"replicas": 3,
+			"selector": {
+				"matchLabels": {
+					"app": "nginx"
+				}
+			},
+			"template": {
+				"metadata": {
+					"creationTimestamp": null,
+					"labels": {
+						"app": "nginx"
+					}
+				},
+				"spec": {
+					"containers": [
+						{
+							"name": "nginx",
+							"image": "nginx:1.14",
+							"ports": [
+								{
+									"containerPort": 80,
+									"protocol": "TCP"
+								}
+							],
+							"resources": {
+							},
+							"terminationMessagePath": "/dev/termination-log",
+							"imagePullPolicy": "IfNotPresent"
+						}
+					],
+					"restartPolicy": "Always",
+					"terminationGracePeriodSeconds": 30,
+					"dnsPolicy": "ClusterFirst",
+					"securityContext": {
+					}
+				}
+			},
+			"strategy": {
+				"type": "RollingUpdate",
+				"rollingUpdate": {
+					"maxUnavailable": 1,
+					"maxSurge": 1
+				}
+			}
+		},
+		"status": {
+			"observedGeneration": 2,
+			"replicas": 3,
+			"updatedReplicas": 3,
+			"availableReplicas": 3
+		}
+	}
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-watch-deployment-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Deployment",
+		"apiVersion": "apps/v1",
+		"metadata": {
+			"name": "deployment-example",
+			"namespace": "default",
+			"selfLink": "/apis/apps/v1/namespaces/default/deployments/deployment-example",
+			"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
+			"resourceVersion": "2128095",
+			"generation": 2,
+			"creationTimestamp": "2016-10-28T03:34:12Z",
+			"labels": {
+				"app": "nginx"
+			},
+			"annotations": {
+				"deployment.kubernetes.io/revision": "3"
+			}
+		},
+		"spec": {
+			"replicas": 3,
+			"selector": {
+				"matchLabels": {
+					"app": "nginx"
+				}
+			},
+			"template": {
+				"metadata": {
+					"creationTimestamp": null,
+					"labels": {
+						"app": "nginx"
+					}
+				},
+				"spec": {
+					"containers": [
+						{
+							"name": "nginx",
+							"image": "nginx:1.14",
+							"ports": [
+								{
+									"containerPort": 80,
+									"protocol": "TCP"
+								}
+							],
+							"resources": {
+							},
+							"terminationMessagePath": "/dev/termination-log",
+							"imagePullPolicy": "IfNotPresent"
+						}
+					],
+					"restartPolicy": "Always",
+					"terminationGracePeriodSeconds": 30,
+					"dnsPolicy": "ClusterFirst",
+					"securityContext": {
+					}
+				}
+			},
+			"strategy": {
+				"type": "RollingUpdate",
+				"rollingUpdate": {
+					"maxUnavailable": 1,
+					"maxSurge": 1
+				}
+			}
+		},
+		"status": {
+			"observedGeneration": 2,
+			"replicas": 3,
+			"updatedReplicas": 3,
+			"availableReplicas": 3
+		}
+	}
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>watch changes to an object of kind Deployment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-deployment-v1-apps">Watch List</H2>
+<P>watch individual changes to a list of Deployment. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-deployment-v1-apps">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Deployment. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/deployments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-deployment-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-deployment-v1-apps">Patch Status</H2>
+<P>partially update status of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-deployment-v1-apps">Read Status</H2>
+<P>read status of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-deployment-v1-apps">Replace Status</H2>
+<P>replace status of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-misc-operations-deployment-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
+<H2 id="read-scale-deployment-v1-apps">Read Scale</H2>
+<P>read scale of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-scale-deployment-v1-apps">Replace Scale</H2>
+<P>replace scale of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-scale-deployment-v1-apps">Patch Scale</H2>
+<P>partially update scale of the specified Deployment</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="job-v1-batch">Job v1 batch</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-job-v1-batch" aria-controls="example-job-v1-batch"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Job Config to print pi up to 2000 digits (then exit).</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: batch/v1
+kind: Job
+metadata:
+  # Unique key of the Job instance
+  name: example-job
+spec:
+  template:
+    metadata:
+      name: example-job
+    spec:
+      containers:
+      - name: pi
+        image: perl
+        command: [&#34;perl&#34;]
+        args: [&#34;-Mbignum=bpi&#34;, &#34;-wle&#34;, &#34;print bpi(2000)&#34;]
+      # Do not restart containers after they exit
+      restartPolicy: Never
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Job</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#joblist-v1-batch">JobList [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of a job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#jobstatus-v1-batch">JobStatus</a></I></TD><TD>Current status of a job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="jobspec-v1-batch">JobSpec v1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
+  <LI><a href="#jobtemplatespec-v1-batch">JobTemplateSpec [batch/v1]</a></LI>
+  <LI><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec [batch/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>activeDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. If a Job is suspended (at creation or through an update), this timer will effectively be stopped and reset when the Job is resumed again.</TD></TR>
+<TR><TD><CODE>backoffLimit</CODE><BR /><I>integer</I></TD><TD>Specifies the number of retries before marking this job failed. Defaults to 6</TD></TR>
+<TR><TD><CODE>completionMode</CODE><BR /><I>string</I></TD><TD>CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.  `NonIndexed` means that the Job is considered complete when there have been .spec.completions successfully completed Pods. Each Pod completion is homologous to each other.  `Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5. In addition, The Pod name takes the form `$(job-name)-$(index)-$(random-string)`, the Pod hostname takes the form `$(job-name)-$(index)`.  This field is beta-level. More completion modes can be added in the future. If the Job controller observes a mode that it doesn&#39;t recognize, the controller skips updates for the Job.</TD></TR>
+<TR><TD><CODE>completions</CODE><BR /><I>integer</I></TD><TD>Specifies the desired number of successfully finished pods the job should be run with.  Setting to nil means that the success of any pod signals the success of all pods, and allows parallelism to have any positive value.  Setting to 1 means that parallelism is limited to 1 and the success of that pod signals the success of the job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
+<TR><TD><CODE>manualSelector</CODE><BR /><I>boolean</I></TD><TD>manualSelector controls generation of pod labels and pod selectors. Leave `manualSelector` unset unless you are certain what you are doing. When false or unset, the system pick labels unique to this job and appends those labels to the pod template.  When true, the user is responsible for picking unique labels and specifying the selector.  Failure to pick a unique label may cause this and other jobs to not function correctly.  However, You may see `manualSelector=true` in jobs that were created with the old `extensions/v1beta1` API. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector</TD></TR>
+<TR><TD><CODE>parallelism</CODE><BR /><I>integer</I></TD><TD>Specifies the maximum desired number of pods the job should run at any given time. The actual number of pods running in steady state will be less than this number when ((.spec.completions - .status.successful) &lt; .spec.parallelism), i.e. when the work left to do is less than max parallelism. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that should match the pod count. Normally, the system sets this field for you. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
+<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>Suspend specifies whether the Job controller should create Pods or not. If a Job is created with suspend set to true, no Pods are created by the Job controller. If a Job is suspended after creation (i.e. the flag goes from false to true), the Job controller will delete all active Pods associated with this Job. Users must design their workload to gracefully handle this. Suspending a Job will reset the StartTime field of the Job, effectively resetting the ActiveDeadlineSeconds timer too. Defaults to false.  This field is beta-level, gated by SuspendJob feature flag (enabled by default).</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
+<TR><TD><CODE>ttlSecondsAfterFinished</CODE><BR /><I>integer</I></TD><TD>ttlSecondsAfterFinished limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. When the Job is being deleted, its lifecycle guarantees (e.g. finalizers) will be honored. If this field is unset, the Job won&#39;t be automatically deleted. If this field is set to zero, the Job becomes eligible to be deleted immediately after it finishes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="jobstatus-v1-batch">JobStatus v1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>active</CODE><BR /><I>integer</I></TD><TD>The number of pending and running pods.</TD></TR>
+<TR><TD><CODE>completedIndexes</CODE><BR /><I>string</I></TD><TD>CompletedIndexes holds the completed indexes when .spec.completionMode = &#34;Indexed&#34; in a text format. The indexes are represented as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the completed indexes are 1, 3, 4, 5 and 7, they are represented as &#34;1,3-5,7&#34;.</TD></TR>
+<TR><TD><CODE>completionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Represents time when the job was completed. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC. The completion time is only set when the job finishes successfully.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#jobcondition-v1-batch">JobCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>The latest available observations of an object&#39;s current state. When a Job fails, one of the conditions will have type &#34;Failed&#34; and status true. When a Job is suspended, one of the conditions will have type &#34;Suspended&#34; and status true; when the Job is resumed, the status of this condition will become false. When a Job is completed, one of the conditions will have type &#34;Complete&#34; and status true. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
+<TR><TD><CODE>failed</CODE><BR /><I>integer</I></TD><TD>The number of pods which reached phase Failed.</TD></TR>
+<TR><TD><CODE>ready</CODE><BR /><I>integer</I></TD><TD>The number of pods which have a Ready condition.  This field is alpha-level. The job controller populates the field when the feature gate JobReadyPods is enabled (disabled by default).</TD></TR>
+<TR><TD><CODE>startTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Represents time when the job controller started processing a job. When a Job is created in the suspended state, this field is not set until the first time it is resumed. This field is reset every time a Job is resumed from suspension. It is represented in RFC3339 form and is in UTC.</TD></TR>
+<TR><TD><CODE>succeeded</CODE><BR /><I>integer</I></TD><TD>The number of pods which reached phase Succeeded.</TD></TR>
+<TR><TD><CODE>uncountedTerminatedPods</CODE><BR /><I><a href="#uncountedterminatedpods-v1-batch">UncountedTerminatedPods</a></I></TD><TD>UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn&#39;t yet accounted for in the status counters.  The job controller creates pods with a finalizer. When a pod terminates (succeeded or failed), the controller does three steps to account for it in the job status: (1) Add the pod UID to the arrays in this field. (2) Remove the pod finalizer. (3) Remove the pod UID from the arrays while increasing the corresponding     counter.  This field is beta-level. The job controller only makes use of this field when the feature gate JobTrackingWithFinalizers is enabled (enabled by default). Old jobs might not be tracked using this field, in which case the field remains null.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="joblist-v1-batch">JobList v1 batch</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#job-v1-batch">Job</a> array</I></TD><TD>items is the list of Jobs.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-job-v1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-job-v1-batch">Create</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-create-job-v1-batch" aria-controls="req-kubectl-create-job-v1-batch"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-create-job-v1-batch" aria-controls="req-curl-create-job-v1-batch"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-create-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'apiVersion: batch/v1
+kind: Job
+metadata:
+  name: example-job
+spec:
+  template:
+    metadata:
+      name: example-job
+    spec:
+      containers:
+      - name: pi
+        image: perl
+        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
+      restartPolicy: Never
+' | kubectl create -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-create-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X POST -H 'Content-Type: application/yaml' --data '
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: example-job
+spec:
+  template:
+    metadata:
+      name: example-job
+    spec:
+      containers:
+      - name: pi
+        image: perl
+        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
+      restartPolicy: Never
+' http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-create-job-v1-batch" aria-controls="res-kubectl-create-job-v1-batch"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-create-job-v1-batch" aria-controls="res-curl-create-job-v1-batch"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-create-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+job "example-job" created
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-create-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Job",
+  "apiVersion": "batch/v1",
+  "metadata": {
+    "name": "example-job",
+    "namespace": "default",
+    "selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
+    "uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+    "resourceVersion": "7479",
+    "creationTimestamp": "2016-11-04T18:45:25Z"
+  },
+  "spec": {
+    "parallelism": 1,
+    "completions": 1,
+    "selector": {
+      "matchLabels": {
+        "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+      }
+    },
+    "template": {
+      "metadata": {
+        "name": "example-job",
+        "creationTimestamp": null,
+        "labels": {
+          "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+          "job-name": "example-job"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "pi",
+            "image": "perl",
+            "command": [
+              "perl",
+              "-Mbignum=bpi",
+              "-wle",
+              "print bpi(2000)"
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "Always"
+          }
+        ],
+        "restartPolicy": "Never",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    }
+  },
+  "status": {}
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>create a Job</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-job-v1-batch">Patch</H2>
+<P>partially update the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-job-v1-batch">Replace</H2>
+<P>replace the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-job-v1-batch">Delete</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-delete-job-v1-batch" aria-controls="req-kubectl-delete-job-v1-batch"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-delete-job-v1-batch" aria-controls="req-curl-delete-job-v1-batch"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-delete-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl delete job example-job
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-delete-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
+gracePeriodSeconds: 0
+orphanDependents: false
+' 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs/example-job'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-delete-job-v1-batch" aria-controls="res-kubectl-delete-job-v1-batch"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-delete-job-v1-batch" aria-controls="res-curl-delete-job-v1-batch"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-delete-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+job "example-job" deleted
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-delete-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Status",
+  "apiVersion": "v1",
+  "metadata": {},
+  "status": "Success",
+  "code": 200
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>delete a Job</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-job-v1-batch">Delete Collection</H2>
+<P>delete collection of Job</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-job-v1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-job-v1-batch">Read</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-read-job-v1-batch" aria-controls="req-kubectl-read-job-v1-batch"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-read-job-v1-batch" aria-controls="req-curl-read-job-v1-batch"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-read-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get job example-job -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-read-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs/example-job
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-read-job-v1-batch" aria-controls="res-kubectl-read-job-v1-batch"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-read-job-v1-batch" aria-controls="res-curl-read-job-v1-batch"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-read-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+  "kind": "Job",
+  "apiVersion": "batch/v1",
+  "metadata": {
+    "name": "example-job",
+    "namespace": "default",
+    "selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
+    "uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+    "resourceVersion": "7482",
+    "creationTimestamp": "2016-11-04T18:45:25Z"
+  },
+  "spec": {
+    "parallelism": 1,
+    "completions": 1,
+    "selector": {
+      "matchLabels": {
+        "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+      }
+    },
+    "template": {
+      "metadata": {
+        "name": "example-job",
+        "creationTimestamp": null,
+        "labels": {
+          "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+          "job-name": "example-job"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "pi",
+            "image": "perl",
+            "command": [
+              "perl",
+              "-Mbignum=bpi",
+              "-wle",
+              "print bpi(2000)"
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "Always"
+          }
+        ],
+        "restartPolicy": "Never",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    }
+  },
+  "status": {
+    "startTime": "2016-11-04T18:45:25Z",
+    "active": 1
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-read-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Job",
+  "apiVersion": "batch/v1",
+  "metadata": {
+    "name": "example-job",
+    "namespace": "default",
+    "selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
+    "uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+    "resourceVersion": "7482",
+    "creationTimestamp": "2016-11-04T18:45:25Z"
+  },
+  "spec": {
+    "parallelism": 1,
+    "completions": 1,
+    "selector": {
+      "matchLabels": {
+        "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+      }
+    },
+    "template": {
+      "metadata": {
+        "name": "example-job",
+        "creationTimestamp": null,
+        "labels": {
+          "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+          "job-name": "example-job"
+        }
+      },
+      "spec": {
+        "containers": [
+          {
+            "name": "pi",
+            "image": "perl",
+            "command": [
+              "perl",
+              "-Mbignum=bpi",
+              "-wle",
+              "print bpi(2000)"
+            ],
+            "resources": {},
+            "terminationMessagePath": "/dev/termination-log",
+            "imagePullPolicy": "Always"
+          }
+        ],
+        "restartPolicy": "Never",
+        "terminationGracePeriodSeconds": 30,
+        "dnsPolicy": "ClusterFirst",
+        "securityContext": {}
+      }
+    }
+  },
+  "status": {
+    "startTime": "2016-11-04T18:45:25Z",
+    "active": 1
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>read the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-job-v1-batch">List</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-list-job-v1-batch" aria-controls="req-kubectl-list-job-v1-batch"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-list-job-v1-batch" aria-controls="req-curl-list-job-v1-batch"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-list-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get job -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-list-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-list-job-v1-batch" aria-controls="res-kubectl-list-job-v1-batch"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-list-job-v1-batch" aria-controls="res-curl-list-job-v1-batch"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-list-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+  "kind": "JobList",
+  "apiVersion": "batch/v1",
+  "metadata": {
+    "selfLink": "/apis/batch/v1/namespaces/default/jobs",
+    "resourceVersion": "7589"
+  },
+  "items": [
+    {
+      "metadata": {
+        "name": "",
+        "namespace": "default",
+        "selfLink": "/apis/batch/v1/namespaces/default/jobs/",
+        "uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+        "resourceVersion": "7482",
+        "creationTimestamp": "2016-11-04T18:45:25Z"
+      },
+      "spec": {
+        "parallelism": 1,
+        "completions": 1,
+        "selector": {
+          "matchLabels": {
+            "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+          }
+        },
+        "template": {
+          "metadata": {
+            "name": "",
+            "creationTimestamp": null,
+            "labels": {
+              "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+              "job-name": ""
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "pi",
+                "image": "perl",
+                "command": [
+                  "perl",
+                  "-Mbignum=bpi",
+                  "-wle",
+                  "print bpi(2000)"
+                ],
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "Always"
+              }
+            ],
+            "restartPolicy": "Never",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        }
+      },
+      "status": {
+        "startTime": "2016-11-04T18:45:25Z",
+        "active": 1
+      }
+    }
+  ]
+}
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-list-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "JobList",
+  "apiVersion": "batch/v1",
+  "metadata": {
+    "selfLink": "/apis/batch/v1/namespaces/default/jobs",
+    "resourceVersion": "7589"
+  },
+  "items": [
+    {
+      "metadata": {
+        "name": "",
+        "namespace": "default",
+        "selfLink": "/apis/batch/v1/namespaces/default/jobs/",
+        "uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+        "resourceVersion": "7482",
+        "creationTimestamp": "2016-11-04T18:45:25Z"
+      },
+      "spec": {
+        "parallelism": 1,
+        "completions": 1,
+        "selector": {
+          "matchLabels": {
+            "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+          }
+        },
+        "template": {
+          "metadata": {
+            "name": "",
+            "creationTimestamp": null,
+            "labels": {
+              "controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+              "job-name": ""
+            }
+          },
+          "spec": {
+            "containers": [
+              {
+                "name": "pi",
+                "image": "perl",
+                "command": [
+                  "perl",
+                  "-Mbignum=bpi",
+                  "-wle",
+                  "print bpi(2000)"
+                ],
+                "resources": {},
+                "terminationMessagePath": "/dev/termination-log",
+                "imagePullPolicy": "Always"
+              }
+            ],
+            "restartPolicy": "Never",
+            "terminationGracePeriodSeconds": 30,
+            "dnsPolicy": "ClusterFirst",
+            "securityContext": {}
+          }
+        }
+      },
+      "status": {
+        "startTime": "2016-11-04T18:45:25Z",
+        "active": 1
+      }
+    }
+  ]
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>list or watch objects of kind Job</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#joblist-v1-batch">JobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-job-v1-batch">List All Namespaces</H2>
+<P>list or watch objects of kind Job</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/jobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#joblist-v1-batch">JobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-job-v1-batch">Watch</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-watch-job-v1-batch" aria-controls="req-kubectl-watch-job-v1-batch"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-watch-job-v1-batch" aria-controls="req-curl-watch-job-v1-batch"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-watch-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get job example-job --watch -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-watch-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/watch/namespaces/default/jobs/example-job'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-watch-job-v1-batch" aria-controls="res-kubectl-watch-job-v1-batch"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-watch-job-v1-batch" aria-controls="res-curl-watch-job-v1-batch"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-watch-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Job",
+		"apiVersion": "batch/v1",
+		"metadata": {
+			"name": "example-job",
+			"namespace": "default",
+			"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
+			"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+			"resourceVersion": "7482",
+			"creationTimestamp": "2016-11-04T18:45:25Z"
+		},
+		"spec": {
+			"parallelism": 1,
+			"completions": 1,
+			"selector": {
+				"matchLabels": {
+					"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+				}
+			},
+			"template": {
+				"metadata": {
+					"name": "example-job",
+					"creationTimestamp": null,
+					"labels": {
+						"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+						"job-name": "example-job"
+					}
+				},
+				"spec": {
+					"containers": [
+						{
+							"name": "pi",
+							"image": "perl",
+							"command": [
+								"perl",
+								"-Mbignum=bpi",
+								"-wle",
+								"print bpi(2000)"
+							],
+							"resources": {
+							},
+							"terminationMessagePath": "/dev/termination-log",
+							"imagePullPolicy": "Always"
+						}
+					],
+					"restartPolicy": "Never",
+					"terminationGracePeriodSeconds": 30,
+					"dnsPolicy": "ClusterFirst",
+					"securityContext": {
+					}
+				}
+			}
+		},
+		"status": {
+			"startTime": "2016-11-04T18:45:25Z",
+			"active": 1
+		}
+	}
+}
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-watch-job-v1-batch">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Job",
+		"apiVersion": "batch/v1",
+		"metadata": {
+			"name": "example-job",
+			"namespace": "default",
+			"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
+			"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+			"resourceVersion": "7482",
+			"creationTimestamp": "2016-11-04T18:45:25Z"
+		},
+		"spec": {
+			"parallelism": 1,
+			"completions": 1,
+			"selector": {
+				"matchLabels": {
+					"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
+				}
+			},
+			"template": {
+				"metadata": {
+					"name": "example-job",
+					"creationTimestamp": null,
+					"labels": {
+						"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
+						"job-name": "example-job"
+					}
+				},
+				"spec": {
+					"containers": [
+						{
+							"name": "pi",
+							"image": "perl",
+							"command": [
+								"perl",
+								"-Mbignum=bpi",
+								"-wle",
+								"print bpi(2000)"
+							],
+							"resources": {
+							},
+							"terminationMessagePath": "/dev/termination-log",
+							"imagePullPolicy": "Always"
+						}
+					],
+					"restartPolicy": "Never",
+					"terminationGracePeriodSeconds": 30,
+					"dnsPolicy": "ClusterFirst",
+					"securityContext": {
+					}
+				}
+			}
+		},
+		"status": {
+			"startTime": "2016-11-04T18:45:25Z",
+			"active": 1
+		}
+	}
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>watch changes to an object of kind Job. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-job-v1-batch">Watch List</H2>
+<P>watch individual changes to a list of Job. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-job-v1-batch">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Job. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/watch/jobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-job-v1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-job-v1-batch">Patch Status</H2>
+<P>partially update status of the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-job-v1-batch">Read Status</H2>
+<P>read status of the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-job-v1-batch">Replace Status</H2>
+<P>replace status of the specified Job</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="pod-v1-core">Pod v1 core</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-pod-v1-core" aria-controls="example-pod-v1-core"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-pod-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Pod Config to print "Hello World".</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: v1
+kind: Pod
+metadata:
+  name: pod-example
+spec:
+  containers:
+  - name: ubuntu
+    image: ubuntu:trusty
+    command: [&#34;echo&#34;]
+    args: [&#34;Hello World&#34;]
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Pod</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>It is recommended that users create Pods only through a Controller, and not directly.  See Controllers: <a href="#deployment-v1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1-apps">StatefulSet</a>.</P></DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podlist-v1-core">PodList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#podspec-v1-core">PodSpec</a></I></TD><TD>Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#podstatus-v1-core">PodStatus</a></I></TD><TD>Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podspec-v1-core">PodSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
+  <LI><a href="#podtemplatespec-v1-core">PodTemplateSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>activeDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.</TD></TR>
+<TR><TD><CODE>affinity</CODE><BR /><I><a href="#affinity-v1-core">Affinity</a></I></TD><TD>If specified, the pod&#39;s scheduling constraints</TD></TR>
+<TR><TD><CODE>automountServiceAccountToken</CODE><BR /><I>boolean</I></TD><TD>AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.</TD></TR>
+<TR><TD><CODE>containers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.</TD></TR>
+<TR><TD><CODE>dnsConfig</CODE><BR /><I><a href="#poddnsconfig-v1-core">PodDNSConfig</a></I></TD><TD>Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.</TD></TR>
+<TR><TD><CODE>dnsPolicy</CODE><BR /><I>string</I></TD><TD>Set DNS policy for the pod. Defaults to &#34;ClusterFirst&#34;. Valid values are &#39;ClusterFirstWithHostNet&#39;, &#39;ClusterFirst&#39;, &#39;Default&#39; or &#39;None&#39;. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to &#39;ClusterFirstWithHostNet&#39;.  Possible enum values:  - `&#34;ClusterFirst&#34;` indicates that the pod should use cluster DNS first unless hostNetwork is true, if it is available, then fall back on the default (as determined by kubelet) DNS settings.  - `&#34;ClusterFirstWithHostNet&#34;` indicates that the pod should use cluster DNS first, if it is available, then fall back on the default (as determined by kubelet) DNS settings.  - `&#34;Default&#34;` indicates that the pod should use the default (as determined by kubelet) DNS settings.  - `&#34;None&#34;` indicates that the pod should use empty DNS settings. DNS parameters such as nameservers and search paths should be defined via DNSConfig.</TD></TR>
+<TR><TD><CODE>enableServiceLinks</CODE><BR /><I>boolean</I></TD><TD>EnableServiceLinks indicates whether information about services should be injected into pod&#39;s environment variables, matching the syntax of Docker links. Optional: Defaults to true.</TD></TR>
+<TR><TD><CODE>ephemeralContainers</CODE><BR /><I><a href="#ephemeralcontainer-v1-core">EphemeralContainer</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod&#39;s ephemeralcontainers subresource. This field is beta-level and available on clusters that haven&#39;t disabled the EphemeralContainers feature gate.</TD></TR>
+<TR><TD><CODE>hostAliases</CODE><BR /><I><a href="#hostalias-v1-core">HostAlias</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>ip</I></TD><TD>HostAliases is an optional list of hosts and IPs that will be injected into the pod&#39;s hosts file if specified. This is only valid for non-hostNetwork pods.</TD></TR>
+<TR><TD><CODE>hostIPC</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s ipc namespace. Optional: Default to false.</TD></TR>
+<TR><TD><CODE>hostNetwork</CODE><BR /><I>boolean</I></TD><TD>Host networking requested for this pod. Use the host&#39;s network namespace. If this option is set, the ports that will be used must be specified. Default to false.</TD></TR>
+<TR><TD><CODE>hostPID</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s pid namespace. Optional: Default to false.</TD></TR>
+<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>Specifies the hostname of the Pod If not specified, the pod&#39;s hostname will be set to a system-defined value.</TD></TR>
+<TR><TD><CODE>imagePullSecrets</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod</TD></TR>
+<TR><TD><CODE>initContainers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</TD></TR>
+<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.</TD></TR>
+<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node&#39;s labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</TD></TR>
+<TR><TD><CODE>os</CODE><BR /><I><a href="#podos-v1-core">PodOS</a></I></TD><TD>Specifies the OS of the containers in the pod. Some pod and container fields are restricted if this is set.  If the OS field is set to linux, the following fields must be unset: -securityContext.windowsOptions  If the OS field is set to windows, following fields must be unset: - spec.hostPID - spec.hostIPC - spec.securityContext.seLinuxOptions - spec.securityContext.seccompProfile - spec.securityContext.fsGroup - spec.securityContext.fsGroupChangePolicy - spec.securityContext.sysctls - spec.shareProcessNamespace - spec.securityContext.runAsUser - spec.securityContext.runAsGroup - spec.securityContext.supplementalGroups - spec.containers[*].securityContext.seLinuxOptions - spec.containers[*].securityContext.seccompProfile - spec.containers[*].securityContext.capabilities - spec.containers[*].securityContext.readOnlyRootFilesystem - spec.containers[*].securityContext.privileged - spec.containers[*].securityContext.allowPrivilegeEscalation - spec.containers[*].securityContext.procMount - spec.containers[*].securityContext.runAsUser - spec.containers[*].securityContext.runAsGroup This is an alpha field and requires the IdentifyPodOS feature</TD></TR>
+<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.</TD></TR>
+<TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.</TD></TR>
+<TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.</TD></TR>
+<TR><TD><CODE>priorityClassName</CODE><BR /><I>string</I></TD><TD>If specified, indicates the pod&#39;s priority. &#34;system-node-critical&#34; and &#34;system-cluster-critical&#34; are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.</TD></TR>
+<TR><TD><CODE>readinessGates</CODE><BR /><I><a href="#podreadinessgate-v1-core">PodReadinessGate</a> array</I></TD><TD>If specified, all readiness gates will be evaluated for pod readiness. A pod is ready when all its containers are ready AND all conditions specified in the readiness gates have status equal to &#34;True&#34; More info: https://git.k8s.io/enhancements/keps/sig-network/580-pod-readiness-gates</TD></TR>
+<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>Restart policy for all containers within the pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy  Possible enum values:  - `&#34;Always&#34;`  - `&#34;Never&#34;`  - `&#34;OnFailure&#34;`</TD></TR>
+<TR><TD><CODE>runtimeClassName</CODE><BR /><I>string</I></TD><TD>RuntimeClassName refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.  If no RuntimeClass resource matches the named class, the pod will not be run. If unset or empty, the &#34;legacy&#34; RuntimeClass will be used, which is an implicit class with an empty definition that uses the default runtime handler. More info: https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class This is a beta feature as of Kubernetes v1.14.</TD></TR>
+<TR><TD><CODE>schedulerName</CODE><BR /><I>string</I></TD><TD>If specified, the pod will be dispatched by specified scheduler. If not specified, the pod will be dispatched by default scheduler.</TD></TR>
+<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#podsecuritycontext-v1-core">PodSecurityContext</a></I></TD><TD>SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty.  See type description for default values of each field.</TD></TR>
+<TR><TD><CODE>serviceAccount</CODE><BR /><I>string</I></TD><TD>DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.</TD></TR>
+<TR><TD><CODE>serviceAccountName</CODE><BR /><I>string</I></TD><TD>ServiceAccountName is the name of the ServiceAccount to use to run this pod. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/</TD></TR>
+<TR><TD><CODE>setHostnameAsFQDN</CODE><BR /><I>boolean</I></TD><TD>If true the pod&#39;s hostname will be configured as the pod&#39;s FQDN, rather than the leaf name (the default). In Linux containers, this means setting the FQDN in the hostname field of the kernel (the nodename field of struct utsname). In Windows containers, this means setting the registry value of hostname for the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters to FQDN. If a pod does not have FQDN, this has no effect. Default to false.</TD></TR>
+<TR><TD><CODE>shareProcessNamespace</CODE><BR /><I>boolean</I></TD><TD>Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false.</TD></TR>
+<TR><TD><CODE>subdomain</CODE><BR /><I>string</I></TD><TD>If specified, the fully qualified Pod hostname will be &#34;&lt;hostname&gt;.&lt;subdomain&gt;.&lt;pod namespace&gt;.svc.&lt;cluster domain&gt;&#34;. If not specified, the pod will not have a domainname at all.</TD></TR>
+<TR><TD><CODE>terminationGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.</TD></TR>
+<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>If specified, the pod&#39;s tolerations.</TD></TR>
+<TR><TD><CODE>topologySpreadConstraints</CODE><BR /><I><a href="#topologyspreadconstraint-v1-core">TopologySpreadConstraint</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>topologyKey</I></TD><TD>TopologySpreadConstraints describes how a group of pods ought to spread across topology domains. Scheduler will schedule pods in a way which abides by the constraints. All topologySpreadConstraints are ANDed.</TD></TR>
+<TR><TD><CODE>volumes</CODE><BR /><I><a href="#volume-v1-core">Volume</a> array</I><BR /><B>patch strategy</B>: <I>merge,retainKeys</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of volumes that can be mounted by containers belonging to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podstatus-v1-core">PodStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#podcondition-v1-core">PodCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state of pod. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions</TD></TR>
+<TR><TD><CODE>containerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>The list has one entry per container in the manifest. Each entry is currently the output of `docker inspect`. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status</TD></TR>
+<TR><TD><CODE>ephemeralContainerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>Status for any ephemeral containers that have run in this pod. This field is beta-level and available on clusters that haven&#39;t disabled the EphemeralContainers feature gate.</TD></TR>
+<TR><TD><CODE>hostIP</CODE><BR /><I>string</I></TD><TD>IP address of the host to which the pod is assigned. Empty if not yet scheduled.</TD></TR>
+<TR><TD><CODE>initContainerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>The list has one entry per init container in the manifest. The most recent successful init container will have ready = true, the most recently started container will have startTime set. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about why the pod is in this condition.</TD></TR>
+<TR><TD><CODE>nominatedNodeName</CODE><BR /><I>string</I></TD><TD>nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.</TD></TR>
+<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>The phase of a Pod is a simple, high-level summary of where the Pod is in its lifecycle. The conditions array, the reason and message fields, and the individual container status arrays contain more detail about the pod&#39;s status. There are five possible phase values:  Pending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.  More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase  Possible enum values:  - `&#34;Failed&#34;` means that all containers in the pod have terminated, and at least one container has terminated in a failure (exited with a non-zero exit code or was stopped by the system).  - `&#34;Pending&#34;` means the pod has been accepted by the system, but one or more of the containers has not been started. This includes time before being bound to a node, as well as time spent pulling images onto the host.  - `&#34;Running&#34;` means the pod has been bound to a node and all of the containers have been started. At least one container is still running or is in the process of being restarted.  - `&#34;Succeeded&#34;` means that all containers in the pod have voluntarily terminated with a container exit code of 0, and the system is not going to restart any of these containers.  - `&#34;Unknown&#34;` means that for some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod. Deprecated: It isn&#39;t being set since 2015 (74da3b14b0c0f658b3bb8d2def5094686d0e9095)</TD></TR>
+<TR><TD><CODE>podIP</CODE><BR /><I>string</I></TD><TD>IP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.</TD></TR>
+<TR><TD><CODE>podIPs</CODE><BR /><I><a href="#podip-v1-core">PodIP</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>ip</I></TD><TD>podIPs holds the IP addresses allocated to the pod. If this field is specified, the 0th entry must match the podIP field. Pods may be allocated at most 1 value for each of IPv4 and IPv6. This list is empty if no IPs have been allocated yet.</TD></TR>
+<TR><TD><CODE>qosClass</CODE><BR /><I>string</I></TD><TD>The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://git.k8s.io/community/contributors/design-proposals/node/resource-qos.md  Possible enum values:  - `&#34;BestEffort&#34;` is the BestEffort qos class.  - `&#34;Burstable&#34;` is the Burstable qos class.  - `&#34;Guaranteed&#34;` is the Guaranteed qos class.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A brief CamelCase message indicating details about why the pod is in this state. e.g. &#39;Evicted&#39;</TD></TR>
+<TR><TD><CODE>startTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>RFC 3339 date and time at which the object was acknowledged by the Kubelet. This is before the Kubelet pulled the container image(s) for the pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podlist-v1-core">PodList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#pod-v1-core">Pod</a> array</I></TD><TD>List of pods. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-pod-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-pod-v1-core">Create</H2>
+<P>create a Pod</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/pods</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="create-eviction-pod-v1-core">Create Eviction</H2>
+<P>create eviction of a Pod</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/eviction</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Eviction</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-pod-v1-core">Patch</H2>
+<P>partially update the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-pod-v1-core">Replace</H2>
+<P>replace the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-pod-v1-core">Delete</H2>
+<P>delete a Pod</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-pod-v1-core">Delete Collection</H2>
+<P>delete collection of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/pods</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-pod-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-pod-v1-core">Read</H2>
+<P>read the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-pod-v1-core">List</H2>
+<P>list or watch objects of kind Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podlist-v1-core">PodList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-pod-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/pods</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podlist-v1-core">PodList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-pod-v1-core">Watch</H2>
+<P>watch changes to an object of kind Pod. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/pods/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-pod-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Pod. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/pods</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-pod-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Pod. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/pods</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-pod-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-pod-v1-core">Patch Status</H2>
+<P>partially update status of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-pod-v1-core">Read Status</H2>
+<P>read status of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-pod-v1-core">Replace Status</H2>
+<P>replace status of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-ephemeralcontainers-operations-pod-v1-core-strong-"><STRONG>EphemeralContainers Operations</STRONG></H2>
+<H2 id="patch-ephemeralcontainers-pod-v1-core">Patch EphemeralContainers</H2>
+<P>partially update ephemeralcontainers of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-ephemeralcontainers-pod-v1-core">Read EphemeralContainers</H2>
+<P>read ephemeralcontainers of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-ephemeralcontainers-pod-v1-core">Replace EphemeralContainers</H2>
+<P>replace ephemeralcontainers of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-proxy-operations-pod-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
+<H2 id="create-connect-portforward-pod-v1-core">Create Connect Portforward</H2>
+<P>connect POST requests to portforward of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodPortForwardOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ports</CODE></TD><TD>List of ports to forward Required when using WebSockets</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="create-connect-proxy-pod-v1-core">Create Connect Proxy</H2>
+<P>connect POST requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="create-connect-proxy-path-pod-v1-core">Create Connect Proxy Path</H2>
+<P>connect POST requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-pod-v1-core">Delete Connect Proxy</H2>
+<P>connect DELETE requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-path-pod-v1-core">Delete Connect Proxy Path</H2>
+<P>connect DELETE requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-portforward-pod-v1-core">Get Connect Portforward</H2>
+<P>connect GET requests to portforward of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodPortForwardOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ports</CODE></TD><TD>List of ports to forward Required when using WebSockets</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-pod-v1-core">Get Connect Proxy</H2>
+<P>connect GET requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-path-pod-v1-core">Get Connect Proxy Path</H2>
+<P>connect GET requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-pod-v1-core">Head Connect Proxy</H2>
+<P>connect HEAD requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-path-pod-v1-core">Head Connect Proxy Path</H2>
+<P>connect HEAD requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-pod-v1-core">Replace Connect Proxy</H2>
+<P>connect PUT requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-path-pod-v1-core">Replace Connect Proxy Path</H2>
+<P>connect PUT requests to proxy of Pod</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-misc-operations-pod-v1-core-strong-"><STRONG>Misc Operations</STRONG></H2>
+<H2 id="read-log-pod-v1-core">Read Log</H2>
+<P>read log of the specified Pod</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/log</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE></TD><TD>The container for which to stream logs. Defaults to only container if there is one container in the pod.</TD></TR>
+<TR><TD><CODE>follow</CODE></TD><TD>Follow the log stream of the pod. Defaults to false.</TD></TR>
+<TR><TD><CODE>insecureSkipTLSVerifyBackend</CODE></TD><TD>insecureSkipTLSVerifyBackend indicates that the apiserver should not confirm the validity of the serving certificate of the backend it is connecting to.  This will make the HTTPS connection between the apiserver and the backend insecure. This means the apiserver cannot verify the log data it is receiving came from the real kubelet.  If the kubelet is configured to verify the apiserver's TLS credentials, it does not mean the connection to the real kubelet is vulnerable to a man in the middle attack (e.g. an attacker could not intercept the actual log data coming from the real kubelet).</TD></TR>
+<TR><TD><CODE>limitBytes</CODE></TD><TD>If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>previous</CODE></TD><TD>Return previous terminated container logs. Defaults to false.</TD></TR>
+<TR><TD><CODE>sinceSeconds</CODE></TD><TD>A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.</TD></TR>
+<TR><TD><CODE>tailLines</CODE></TD><TD>If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime</TD></TR>
+<TR><TD><CODE>timestamps</CODE></TD><TD>If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="replicaset-v1-apps">ReplicaSet v1 apps</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-replicaset-v1-apps" aria-controls="example-replicaset-v1-apps"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-replicaset-v1-apps">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">ReplicaSet Config to run 3 nginx instances.</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: apps/v1
+kind: ReplicaSet
+metadata:
+  # Unique key of the ReplicaSet instance
+  name: replicaset-example
+spec:
+  # 3 Pods should exist at all times.
+  replicas: 3
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      # Run the nginx image
+      - name: nginx
+        image: nginx:1.14
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicaSet</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>In many cases it is recommended to create a <a href="#deployment-v1-apps">Deployment</a> instead of ReplicaSet.</P></DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicasetlist-v1-apps">ReplicaSetList [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicasetspec-v1-apps">ReplicaSetSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#replicasetstatus-v1-apps">ReplicaSetStatus</a></I></TD><TD>Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicasetspec-v1-apps">ReplicaSetSpec v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selector is a label query over pods that should match the replica count. Label keys and values that must match in order to be controlled by this replica set. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicasetstatus-v1-apps">ReplicaSetStatus v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replica set.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicasetcondition-v1-apps">ReplicaSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replica set&#39;s current state.</TD></TR>
+<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replicaset.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed ReplicaSet.</TD></TR>
+<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of pods targeted by this ReplicaSet with a Ready Condition.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicasetlist-v1-apps">ReplicaSetList v1 apps</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#replicaset-v1-apps">ReplicaSet</a> array</I></TD><TD>List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-replicaset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-replicaset-v1-apps">Create</H2>
+<P>create a ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-replicaset-v1-apps">Patch</H2>
+<P>partially update the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-replicaset-v1-apps">Replace</H2>
+<P>replace the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-replicaset-v1-apps">Delete</H2>
+<P>delete a ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-replicaset-v1-apps">Delete Collection</H2>
+<P>delete collection of ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-replicaset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-replicaset-v1-apps">Read</H2>
+<P>read the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-replicaset-v1-apps">List</H2>
+<P>list or watch objects of kind ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicasetlist-v1-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-replicaset-v1-apps">List All Namespaces</H2>
+<P>list or watch objects of kind ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/replicasets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicasetlist-v1-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-replicaset-v1-apps">Watch</H2>
+<P>watch changes to an object of kind ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-replicaset-v1-apps">Watch List</H2>
+<P>watch individual changes to a list of ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-replicaset-v1-apps">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/replicasets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-replicaset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-replicaset-v1-apps">Patch Status</H2>
+<P>partially update status of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-replicaset-v1-apps">Read Status</H2>
+<P>read status of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-replicaset-v1-apps">Replace Status</H2>
+<P>replace status of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-misc-operations-replicaset-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
+<H2 id="read-scale-replicaset-v1-apps">Read Scale</H2>
+<P>read scale of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-scale-replicaset-v1-apps">Replace Scale</H2>
+<P>replace scale of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-scale-replicaset-v1-apps">Patch Scale</H2>
+<P>partially update scale of the specified ReplicaSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="replicationcontroller-v1-core">ReplicationController v1 core</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-replicationcontroller-v1-core" aria-controls="example-replicationcontroller-v1-core"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-replicationcontroller-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">ReplicationController Config to run 3 nginx instances.</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+apiVersion: v1
+kind: ReplicationController
+metadata:
+  # Unique key of the ReplicationController instance
+  name: replicationcontroller-example
+spec:
+  # 3 Pods should exist at all times.
+  replicas: 3
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      # Run the nginx image
+      - name: nginx
+        image: nginx:1.14
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicationController</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>In many cases it is recommended to create a <a href="#deployment-v1-apps">Deployment</a> instead of a ReplicationController.</P></DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicationController are empty, they are defaulted to be the same as the Pod(s) that the replication controller manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicationcontrollerspec-v1-core">ReplicationControllerSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the replication controller. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#replicationcontrollerstatus-v1-core">ReplicationControllerStatus</a></I></TD><TD>Status is the most recently observed status of the replication controller. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicationcontrollerspec-v1-core">ReplicationControllerSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>Selector is a label query over pods that should match the Replicas count. If Selector is empty, it is defaulted to the labels present on the Pod template. Label keys and values that must match in order to be controlled by this replication controller, if empty defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. This takes precedence over a TemplateRef. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicationcontrollerstatus-v1-core">ReplicationControllerStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replication controller.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicationcontrollercondition-v1-core">ReplicationControllerCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replication controller&#39;s current state.</TD></TR>
+<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replication controller.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed replication controller.</TD></TR>
+<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>The number of ready replicas for this replication controller.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="replicationcontrollerlist-v1-core">ReplicationControllerList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#replicationcontroller-v1-core">ReplicationController</a> array</I></TD><TD>List of replication controllers. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-replicationcontroller-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-replicationcontroller-v1-core">Create</H2>
+<P>create a ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-replicationcontroller-v1-core">Patch</H2>
+<P>partially update the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-replicationcontroller-v1-core">Replace</H2>
+<P>replace the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-replicationcontroller-v1-core">Delete</H2>
+<P>delete a ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-replicationcontroller-v1-core">Delete Collection</H2>
+<P>delete collection of ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-replicationcontroller-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-replicationcontroller-v1-core">Read</H2>
+<P>read the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-replicationcontroller-v1-core">List</H2>
+<P>list or watch objects of kind ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-replicationcontroller-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/replicationcontrollers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-replicationcontroller-v1-core">Watch</H2>
+<P>watch changes to an object of kind ReplicationController. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-replicationcontroller-v1-core">Watch List</H2>
+<P>watch individual changes to a list of ReplicationController. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-replicationcontroller-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ReplicationController. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/replicationcontrollers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-replicationcontroller-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-replicationcontroller-v1-core">Patch Status</H2>
+<P>partially update status of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-replicationcontroller-v1-core">Read Status</H2>
+<P>read status of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-replicationcontroller-v1-core">Replace Status</H2>
+<P>replace status of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-misc-operations-replicationcontroller-v1-core-strong-"><STRONG>Misc Operations</STRONG></H2>
+<H2 id="read-scale-replicationcontroller-v1-core">Read Scale</H2>
+<P>read scale of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-scale-replicationcontroller-v1-core">Replace Scale</H2>
+<P>replace scale of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-scale-replicationcontroller-v1-core">Patch Scale</H2>
+<P>partially update scale of the specified ReplicationController</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="statefulset-v1-apps">StatefulSet v1 apps</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSet</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulsetlist-v1-apps">StatefulSetList [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#statefulsetspec-v1-apps">StatefulSetSpec</a></I></TD><TD>Spec defines the desired identities of pods in this set.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#statefulsetstatus-v1-apps">StatefulSetStatus</a></I></TD><TD>Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="statefulsetspec-v1-apps">StatefulSetSpec v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready) This is an alpha field and requires enabling StatefulSetMinReadySeconds feature gate.</TD></TR>
+<TR><TD><CODE>persistentVolumeClaimRetentionPolicy</CODE><BR /><I><a href="#statefulsetpersistentvolumeclaimretentionpolicy-v1-apps">StatefulSetPersistentVolumeClaimRetentionPolicy</a></I></TD><TD>persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows the lifecycle to be altered, for example by deleting persistent volume claims when their stateful set is deleted, or when their pod is scaled down. This requires the StatefulSetAutoDeletePVC feature gate to be enabled, which is alpha.  +optional</TD></TR>
+<TR><TD><CODE>podManagementPolicy</CODE><BR /><I>string</I></TD><TD>podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.  Possible enum values:  - `&#34;OrderedReady&#34;` will create pods in strictly increasing order on scale up and strictly decreasing order on scale down, progressing only when the previous pod is ready or terminated. At most one pod will be changed at any time.  - `&#34;Parallel&#34;` will create and delete pods as soon as the stateful set replica count is changed, and will not wait for pods to be ready or complete termination.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.</TD></TR>
+<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet&#39;s revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is a label query over pods that should match the replica count. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
+<TR><TD><CODE>serviceName</CODE><BR /><I>string</I></TD><TD>serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where &#34;pod-specific-string&#34; is managed by the StatefulSet controller.</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.</TD></TR>
+<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy</a></I></TD><TD>updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.</TD></TR>
+<TR><TD><CODE>volumeClaimTemplates</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="statefulsetstatus-v1-apps">StatefulSetStatus v1 apps</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this statefulset. This is a beta field and enabled/disabled by StatefulSetMinReadySeconds feature gate.</TD></TR>
+<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#statefulsetcondition-v1-apps">StatefulSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a statefulset&#39;s current state.</TD></TR>
+<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.</TD></TR>
+<TR><TD><CODE>currentRevision</CODE><BR /><I>string</I></TD><TD>currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet&#39;s generation, which is updated on mutation by the API Server.</TD></TR>
+<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of pods created for this StatefulSet with a Ready Condition.</TD></TR>
+<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the number of Pods created by the StatefulSet controller.</TD></TR>
+<TR><TD><CODE>updateRevision</CODE><BR /><I>string</I></TD><TD>updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)</TD></TR>
+<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="statefulsetlist-v1-apps">StatefulSetList v1 apps</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#statefulset-v1-apps">StatefulSet</a> array</I></TD><TD>Items is the list of stateful sets.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-statefulset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-statefulset-v1-apps">Create</H2>
+<P>create a StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-statefulset-v1-apps">Patch</H2>
+<P>partially update the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-statefulset-v1-apps">Replace</H2>
+<P>replace the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-statefulset-v1-apps">Delete</H2>
+<P>delete a StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-statefulset-v1-apps">Delete Collection</H2>
+<P>delete collection of StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-statefulset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-statefulset-v1-apps">Read</H2>
+<P>read the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-statefulset-v1-apps">List</H2>
+<P>list or watch objects of kind StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulsetlist-v1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-statefulset-v1-apps">List All Namespaces</H2>
+<P>list or watch objects of kind StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/statefulsets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulsetlist-v1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-statefulset-v1-apps">Watch</H2>
+<P>watch changes to an object of kind StatefulSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-statefulset-v1-apps">Watch List</H2>
+<P>watch individual changes to a list of StatefulSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-statefulset-v1-apps">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of StatefulSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/statefulsets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-statefulset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-statefulset-v1-apps">Patch Status</H2>
+<P>partially update status of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-statefulset-v1-apps">Read Status</H2>
+<P>read status of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-statefulset-v1-apps">Replace Status</H2>
+<P>replace status of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-misc-operations-statefulset-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
+<H2 id="read-scale-statefulset-v1-apps">Read Scale</H2>
+<P>read scale of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-scale-statefulset-v1-apps">Replace Scale</H2>
+<P>replace scale of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-scale-statefulset-v1-apps">Patch Scale</H2>
+<P>partially update scale of the specified StatefulSet</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-service-apis-strong-"><STRONG>SERVICE APIs</STRONG></H1>
+
+<P>Service API resources are responsible for stitching your workloads together into an accessible Loadbalanced Service.  By default,
+<A href="#-strong-workloads-strong">Workloads</A> are only accessible within the cluster, and they must be exposed externally using a either
+a *LoadBalancer* or *NodePort* <A href="#service-v1-core">Service</A>.  For development, internally accessible
+Workloads can be accessed via proxy through the api master using the <code>kubectl proxy</code> command.</P>
+
+<P>Common resource types:</P>
+
+<UL>
+	<LI><A href="#service-v1-core">Services</A> for providing a single ip endpoint loadbalanced across multiple Workload replicas.</LI>
+	<LI><A href="#ingress-v1beta1-extensions">Ingress</A> for providing a https(s) endpoint http(s) routed to one or more *Services*.</LI>
+</UL>
+<HR />
+<H1 id="endpoints-v1-core">Endpoints v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Endpoints</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslist-v1-core">EndpointsList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>subsets</CODE><BR /><I><a href="#endpointsubset-v1-core">EndpointSubset</a> array</I></TD><TD>The set of all endpoints is the union of all subsets. Addresses are placed into subsets according to the IPs they share. A single address with multiple ports, some of which are ready and some of which are not (because they come from different containers) will result in the address being displayed in different subsets for the different ports. No address will appear in both Addresses and NotReadyAddresses in the same subset. Sets of addresses and ports that comprise a service.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="endpointslist-v1-core">EndpointsList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#endpoints-v1-core">Endpoints</a> array</I></TD><TD>List of endpoints.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-endpoints-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-endpoints-v1-core">Create</H2>
+<P>create Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/endpoints</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-endpoints-v1-core">Patch</H2>
+<P>partially update the specified Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-endpoints-v1-core">Replace</H2>
+<P>replace the specified Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-endpoints-v1-core">Delete</H2>
+<P>delete Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-endpoints-v1-core">Delete Collection</H2>
+<P>delete collection of Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/endpoints</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-endpoints-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-endpoints-v1-core">Read</H2>
+<P>read the specified Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-endpoints-v1-core">List</H2>
+<P>list or watch objects of kind Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/endpoints</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslist-v1-core">EndpointsList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-endpoints-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind Endpoints</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/endpoints</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslist-v1-core">EndpointsList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-endpoints-v1-core">Watch</H2>
+<P>watch changes to an object of kind Endpoints. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-endpoints-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Endpoints. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-endpoints-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Endpoints. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/endpoints</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointslice-v1-discovery-k8s-io">EndpointSlice v1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointSlice</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointslice-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addressType</CODE><BR /><I>string</I></TD><TD>addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.  Possible enum values:  - `&#34;FQDN&#34;` represents a FQDN.  - `&#34;IPv4&#34;` represents an IPv4 Address.  - `&#34;IPv6&#34;` represents an IPv6 Address.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>endpoints</CODE><BR /><I><a href="#endpoint-v1-discovery-k8s-io">Endpoint</a> array</I></TD><TD>endpoints is a list of unique endpoints in this slice. Each slice may include a maximum of 1000 endpoints.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#endpointport-v1-discovery-k8s-io">EndpointPort</a> array</I></TD><TD>ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates &#34;all ports&#34;. Each slice may include a maximum of 100 ports.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="endpointslicelist-v1-discovery-k8s-io">EndpointSliceList v1 discovery</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a> array</I></TD><TD>List of endpoint slices</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-endpointslice-v1-discovery-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-endpointslice-v1-discovery-k8s-io">Create</H2>
+<P>create an EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-endpointslice-v1-discovery-k8s-io">Patch</H2>
+<P>partially update the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-endpointslice-v1-discovery-k8s-io">Replace</H2>
+<P>replace the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-endpointslice-v1-discovery-k8s-io">Delete</H2>
+<P>delete an EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-endpointslice-v1-discovery-k8s-io">Delete Collection</H2>
+<P>delete collection of EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-endpointslice-v1-discovery-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-endpointslice-v1-discovery-k8s-io">Read</H2>
+<P>read the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-endpointslice-v1-discovery-k8s-io">List</H2>
+<P>list or watch objects of kind EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-endpointslice-v1-discovery-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/endpointslices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-endpointslice-v1-discovery-k8s-io">Watch</H2>
+<P>watch changes to an object of kind EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/watch/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-endpointslice-v1-discovery-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/watch/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1/watch/endpointslices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="ingress-v1-networking-k8s-io">Ingress v1 networking.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Ingress</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingresslist-v1-networking-k8s-io">IngressList [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#ingressspec-v1-networking-k8s-io">IngressSpec</a></I></TD><TD>Spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#ingressstatus-v1-networking-k8s-io">IngressStatus</a></I></TD><TD>Status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ingressspec-v1-networking-k8s-io">IngressSpec v1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>defaultBackend</CODE><BR /><I><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend</a></I></TD><TD>DefaultBackend is the backend that should handle requests that don&#39;t match any rule. If Rules are not specified, DefaultBackend must be specified. If DefaultBackend is not set, the handling of requests that do not match any of the rules will be up to the Ingress controller.</TD></TR>
+<TR><TD><CODE>ingressClassName</CODE><BR /><I>string</I></TD><TD>IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated `kubernetes.io/ingress.class` annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#ingressrule-v1-networking-k8s-io">IngressRule</a> array</I></TD><TD>A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.</TD></TR>
+<TR><TD><CODE>tls</CODE><BR /><I><a href="#ingresstls-v1-networking-k8s-io">IngressTLS</a> array</I></TD><TD>TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ingressstatus-v1-networking-k8s-io">IngressStatus v1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>loadBalancer</CODE><BR /><I><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus</a></I></TD><TD>LoadBalancer contains the current status of the load-balancer.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ingresslist-v1-networking-k8s-io">IngressList v1 networking</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a> array</I></TD><TD>Items is the list of Ingress.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-ingress-v1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-ingress-v1-networking-k8s-io">Create</H2>
+<P>create an Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-ingress-v1-networking-k8s-io">Patch</H2>
+<P>partially update the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-ingress-v1-networking-k8s-io">Replace</H2>
+<P>replace the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-ingress-v1-networking-k8s-io">Delete</H2>
+<P>delete an Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-ingress-v1-networking-k8s-io">Delete Collection</H2>
+<P>delete collection of Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-ingress-v1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-ingress-v1-networking-k8s-io">Read</H2>
+<P>read the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-ingress-v1-networking-k8s-io">List</H2>
+<P>list or watch objects of kind Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingresslist-v1-networking-k8s-io">IngressList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-ingress-v1-networking-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/ingresses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingresslist-v1-networking-k8s-io">IngressList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-ingress-v1-networking-k8s-io">Watch</H2>
+<P>watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/ingresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-ingress-v1-networking-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of Ingress. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/ingresses</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-ingress-v1-networking-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Ingress. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/ingresses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-ingress-v1-networking-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-ingress-v1-networking-k8s-io">Patch Status</H2>
+<P>partially update status of the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-ingress-v1-networking-k8s-io">Read Status</H2>
+<P>read status of the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-ingress-v1-networking-k8s-io">Replace Status</H2>
+<P>replace status of the specified Ingress</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="ingressclass-v1-networking-k8s-io">IngressClass v1 networking.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressclasslist-v1-networking-k8s-io">IngressClassList [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#ingressclassspec-v1-networking-k8s-io">IngressClassSpec</a></I></TD><TD>Spec is the desired state of the IngressClass. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ingressclassspec-v1-networking-k8s-io">IngressClassSpec v1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressclass-v1-networking-k8s-io">IngressClass [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>controller</CODE><BR /><I>string</I></TD><TD>Controller refers to the name of the controller that should handle this class. This allows for different &#34;flavors&#34; that are controlled by the same controller. For example, you may have different Parameters for the same implementing controller. This should be specified as a domain-prefixed path no more than 250 characters in length, e.g. &#34;acme.io/ingress-controller&#34;. This field is immutable.</TD></TR>
+<TR><TD><CODE>parameters</CODE><BR /><I><a href="#ingressclassparametersreference-v1-networking-k8s-io">IngressClassParametersReference</a></I></TD><TD>Parameters is a link to a custom resource containing additional configuration for the controller. This is optional if the controller does not require extra parameters.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ingressclasslist-v1-networking-k8s-io">IngressClassList v1 networking</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a> array</I></TD><TD>Items is the list of IngressClasses.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-ingressclass-v1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-ingressclass-v1-networking-k8s-io">Create</H2>
+<P>create an IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/networking.k8s.io/v1/ingressclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-ingressclass-v1-networking-k8s-io">Patch</H2>
+<P>partially update the specified IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-ingressclass-v1-networking-k8s-io">Replace</H2>
+<P>replace the specified IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-ingressclass-v1-networking-k8s-io">Delete</H2>
+<P>delete an IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-ingressclass-v1-networking-k8s-io">Delete Collection</H2>
+<P>delete collection of IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/ingressclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-ingressclass-v1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-ingressclass-v1-networking-k8s-io">Read</H2>
+<P>read the specified IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-ingressclass-v1-networking-k8s-io">List</H2>
+<P>list or watch objects of kind IngressClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/ingressclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ingressclasslist-v1-networking-k8s-io">IngressClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-ingressclass-v1-networking-k8s-io">Watch</H2>
+<P>watch changes to an object of kind IngressClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/ingressclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-ingressclass-v1-networking-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of IngressClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/ingressclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="service-v1-core">Service v1 core</H1>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#example-service-v1-core" aria-controls="example-service-v1-core"
+  aria-expanded="false">example</BUTTON>
+<DIV class="collapse" id="example-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Service Config to load balance traffic across all Pods with the app=nginx label.  Receives on and sends to port 80.  Exposes an externally accessible endpoint.</DIV>
+  <DIV class="panel-body">
+<PRE class="example"><CODE class="lang-yaml">
+kind: Service
+apiVersion: v1
+metadata:
+  # Unique key of the Service instance
+  name: service-example
+spec:
+  ports:
+    # Accept traffic sent to port 80
+    - name: http
+      port: 80
+      targetPort: 80
+  selector:
+    # Loadbalance traffic across Pods matching
+    # this label selector
+    app: nginx
+  # Create an HA proxy in the cloud provider
+  # with an External IP address - *Only supported
+  # by some cloud providers*
+  type: LoadBalancer
+
+</CODE></PRE></DIV></DIV></DIV>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Service</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#servicelist-v1-core">ServiceList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#servicespec-v1-core">ServiceSpec</a></I></TD><TD>Spec defines the behavior of a service. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#servicestatus-v1-core">ServiceStatus</a></I></TD><TD>Most recently observed status of the service. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="servicespec-v1-core">ServiceSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#service-v1-core">Service [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocateLoadBalancerNodePorts</CODE><BR /><I>boolean</I></TD><TD>allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer.  Default is &#34;true&#34;. It may be set to &#34;false&#34; if the cluster load-balancer does not rely on NodePorts.  If the caller requests specific NodePorts (by specifying a value), those requests will be respected, regardless of this field. This field may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type. This field is beta-level and is only honored by servers that enable the ServiceLBNodePortControl feature.</TD></TR>
+<TR><TD><CODE>clusterIP</CODE><BR /><I>string</I></TD><TD>clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be blank) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above).  Valid values are &#34;None&#34;, empty string (&#34;&#34;), or a valid IP address. Setting this to &#34;None&#34; makes a &#34;headless service&#34; (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required.  Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
+<TR><TD><CODE>clusterIPs</CODE><BR /><I>string array</I></TD><TD>ClusterIPs is a list of IP addresses assigned to this service, and are usually assigned randomly.  If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be empty) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above).  Valid values are &#34;None&#34;, empty string (&#34;&#34;), or a valid IP address.  Setting this to &#34;None&#34; makes a &#34;headless service&#34; (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required.  Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName.  If this field is not specified, it will be initialized from the clusterIP field.  If this field is specified, clients must ensure that clusterIPs[0] and clusterIP have the same value.  This field may hold a maximum of two entries (dual-stack IPs, in either order). These IPs must correspond to the values of the ipFamilies field. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
+<TR><TD><CODE>externalIPs</CODE><BR /><I>string array</I></TD><TD>externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service.  These IPs are not managed by Kubernetes.  The user is responsible for ensuring that traffic arrives at a node with this IP.  A common example is external load-balancers that are not part of the Kubernetes system.</TD></TR>
+<TR><TD><CODE>externalName</CODE><BR /><I>string</I></TD><TD>externalName is the external reference that discovery mechanisms will return as an alias for this service (e.g. a DNS CNAME record). No proxying will be involved.  Must be a lowercase RFC-1123 hostname (https://tools.ietf.org/html/rfc1123) and requires `type` to be &#34;ExternalName&#34;.</TD></TR>
+<TR><TD><CODE>externalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>externalTrafficPolicy denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. &#34;Local&#34; preserves the client source IP and avoids a second hop for LoadBalancer and Nodeport type services, but risks potentially imbalanced traffic spreading. &#34;Cluster&#34; obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading.  Possible enum values:  - `&#34;Cluster&#34;` specifies node-global (legacy) behavior.  - `&#34;Local&#34;` specifies node-local endpoints behavior.</TD></TR>
+<TR><TD><CODE>healthCheckNodePort</CODE><BR /><I>integer</I></TD><TD>healthCheckNodePort specifies the healthcheck nodePort for the service. This only applies when type is set to LoadBalancer and externalTrafficPolicy is set to Local. If a value is specified, is in-range, and is not in use, it will be used.  If not specified, a value will be automatically allocated.  External systems (e.g. load-balancers) can use this port to determine if a given node holds endpoints for this service or not.  If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type).</TD></TR>
+<TR><TD><CODE>internalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>InternalTrafficPolicy specifies if the cluster internal traffic should be routed to all endpoints or node-local endpoints only. &#34;Cluster&#34; routes internal traffic to a Service to all endpoints. &#34;Local&#34; routes traffic to node-local endpoints only, traffic is dropped if no node-local endpoints are ready. The default value is &#34;Cluster&#34;.</TD></TR>
+<TR><TD><CODE>ipFamilies</CODE><BR /><I>string array</I></TD><TD>IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. If this field is specified manually, the requested family is available in the cluster, and ipFamilyPolicy allows it, it will be used; otherwise creation of the service will fail. This field is conditionally mutable: it allows for adding or removing a secondary IP family, but it does not allow changing the primary IP family of the Service. Valid values are &#34;IPv4&#34; and &#34;IPv6&#34;.  This field only applies to Services of types ClusterIP, NodePort, and LoadBalancer, and does apply to &#34;headless&#34; services. This field will be wiped when updating a Service to type ExternalName.  This field may hold a maximum of two entries (dual-stack families, in either order).  These families must correspond to the values of the clusterIPs field, if specified. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.</TD></TR>
+<TR><TD><CODE>ipFamilyPolicy</CODE><BR /><I>string</I></TD><TD>IPFamilyPolicy represents the dual-stack-ness requested or required by this Service. If there is no value provided, then this field will be set to SingleStack. Services can be &#34;SingleStack&#34; (a single IP family), &#34;PreferDualStack&#34; (two IP families on dual-stack configured clusters or a single IP family on single-stack clusters), or &#34;RequireDualStack&#34; (two IP families on dual-stack configured clusters, otherwise fail). The ipFamilies and clusterIPs fields depend on the value of this field. This field will be wiped when updating a service to type ExternalName.</TD></TR>
+<TR><TD><CODE>loadBalancerClass</CODE><BR /><I>string</I></TD><TD>loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. &#34;internal-vip&#34; or &#34;example.com/internal-vip&#34;. Unprefixed names are reserved for end-users. This field can only be set when the Service type is &#39;LoadBalancer&#39;. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type &#39;LoadBalancer&#39;. Once set, it can not be changed. This field will be wiped when a service is updated to a non &#39;LoadBalancer&#39; type.</TD></TR>
+<TR><TD><CODE>loadBalancerIP</CODE><BR /><I>string</I></TD><TD>Only applies to Service Type: LoadBalancer LoadBalancer will get created with the IP specified in this field. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature.</TD></TR>
+<TR><TD><CODE>loadBalancerSourceRanges</CODE><BR /><I>string array</I></TD><TD>If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature.&#34; More info: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#serviceport-v1-core">ServicePort</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>port</I></TD><TD>The list of ports that are exposed by this service. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
+<TR><TD><CODE>publishNotReadyAddresses</CODE><BR /><I>boolean</I></TD><TD>publishNotReadyAddresses indicates that any agent which deals with endpoints for this Service should disregard any indications of ready/not-ready. The primary use case for setting this field is for a StatefulSet&#39;s Headless Service to propagate SRV DNS records for its Pods for the purpose of peer discovery. The Kubernetes controllers that generate Endpoints and EndpointSlice resources for Services interpret this to mean that all endpoints are considered &#34;ready&#34; even if the Pods themselves are not. Agents which consume only Kubernetes generated endpoints through the Endpoints or EndpointSlice resources can safely assume this behavior.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>Route service traffic to pods with label keys and values matching this selector. If empty or not present, the service is assumed to have an external process managing its endpoints, which Kubernetes will not modify. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/</TD></TR>
+<TR><TD><CODE>sessionAffinity</CODE><BR /><I>string</I></TD><TD>Supports &#34;ClientIP&#34; and &#34;None&#34;. Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies  Possible enum values:  - `&#34;ClientIP&#34;` is the Client IP based.  - `&#34;None&#34;` - no session affinity.</TD></TR>
+<TR><TD><CODE>sessionAffinityConfig</CODE><BR /><I><a href="#sessionaffinityconfig-v1-core">SessionAffinityConfig</a></I></TD><TD>sessionAffinityConfig contains the configurations of session affinity.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. &#34;ClusterIP&#34; allocates a cluster-internal IP address for load-balancing to endpoints. Endpoints are determined by the selector or if that is not specified, by manual construction of an Endpoints object or EndpointSlice objects. If clusterIP is &#34;None&#34;, no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. &#34;NodePort&#34; builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. &#34;LoadBalancer&#34; builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. &#34;ExternalName&#34; aliases this service to the specified externalName. Several other fields do not apply to ExternalName services. More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types  Possible enum values:  - `&#34;ClusterIP&#34;` means a service will only be accessible inside the cluster, via the cluster IP.  - `&#34;ExternalName&#34;` means a service consists of only a reference to an external name that kubedns or equivalent will return as a CNAME record, with no exposing or proxying of any pods involved.  - `&#34;LoadBalancer&#34;` means a service will be exposed via an external load balancer (if the cloud provider supports it), in addition to &#39;NodePort&#39; type.  - `&#34;NodePort&#34;` means a service will be exposed on one port of every node, in addition to &#39;ClusterIP&#39; type.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="servicestatus-v1-core">ServiceStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#service-v1-core">Service [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#condition-v1-meta">Condition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state</TD></TR>
+<TR><TD><CODE>loadBalancer</CODE><BR /><I><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus</a></I></TD><TD>LoadBalancer contains the current status of the load-balancer, if one is present.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="servicelist-v1-core">ServiceList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#service-v1-core">Service</a> array</I></TD><TD>List of services</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-service-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-service-v1-core">Create</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-create-service-v1-core" aria-controls="req-kubectl-create-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-create-service-v1-core" aria-controls="req-curl-create-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-create-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'kind: Service
+apiVersion: v1
+metadata:
+  name: service-example
+spec:
+  ports:
+    - name: http
+      port: 80
+      targetPort: 80
+  selector:
+      app: nginx
+  type: LoadBalancer
+' | kubectl create -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-create-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X POST -H 'Content-Type: application/yaml' --data '
+kind: Service
+apiVersion: v1
+metadata:
+  name: service-example
+spec:
+  ports:
+    - name: http
+      port: 80
+      targetPort: 80
+  selector:
+      app: nginx
+  type: LoadBalancer
+' http://127.0.0.1:8001/api/v1/namespaces/default/services
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-create-service-v1-core" aria-controls="res-kubectl-create-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-create-service-v1-core" aria-controls="res-curl-create-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-create-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+service "service-example" created
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-create-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Service",
+  "apiVersion": "v1",
+  "metadata": {
+    "name": "service-example",
+    "namespace": "default",
+    "selfLink": "/api/v1/namespaces/default/services/service-example",
+    "uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+    "resourceVersion": "2205767",
+    "creationTimestamp": "2016-10-28T17:04:24Z"
+  },
+  "spec": {
+    "ports": [
+      {
+        "name": "http",
+        "protocol": "TCP",
+        "port": 80,
+        "targetPort": 80,
+        "nodePort": 32417
+      }
+    ],
+    "selector": {
+      "app": "nginx"
+    },
+    "clusterIP": "10.183.250.161",
+    "type": "LoadBalancer",
+    "sessionAffinity": "None"
+  },
+  "status": {
+    "loadBalancer": {}
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>create a Service</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/services</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-service-v1-core">Patch</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-patch-service-v1-core" aria-controls="req-kubectl-patch-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-patch-service-v1-core" aria-controls="req-curl-patch-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-patch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl patch service  -p \
+	'{"spec":{"ports":[{"name":"http","port":80,"targetPort":8080}]}}'
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-patch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
+{"spec":{"ports":[{"name":"http","port":80,"targetPort":8080}]}}' \
+	'http://127.0.0.1:8001/api/v1/namespaces/default/services/'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-patch-service-v1-core" aria-controls="res-kubectl-patch-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-patch-service-v1-core" aria-controls="res-curl-patch-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-patch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+"" patched
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-patch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Service",
+  "apiVersion": "v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/api/v1/namespaces/default/services/deployment-example",
+    "uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+    "resourceVersion": "2205995",
+    "creationTimestamp": "2016-10-28T17:04:24Z"
+  },
+  "spec": {
+    "ports": [
+      {
+        "name": "http",
+        "protocol": "TCP",
+        "port": 80,
+        "targetPort": 8080,
+        "nodePort": 32417
+      }
+    ],
+    "selector": {
+      "app": "nginx"
+    },
+    "clusterIP": "10.183.250.161",
+    "type": "LoadBalancer",
+    "sessionAffinity": "None"
+  },
+  "status": {
+    "loadBalancer": {
+      "ingress": [
+        {
+          "ip": "104.198.186.106"
+        }
+      ]
+    }
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>partially update the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-service-v1-core">Replace</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-replace-service-v1-core" aria-controls="req-kubectl-replace-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-replace-service-v1-core" aria-controls="req-curl-replace-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-replace-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ echo 'apiVersion: v1
+kind: Service
+metadata:
+  name: deployment-example
+  resourceVersion: "2205995"
+spec:
+  clusterIP: 10.183.250.161
+  ports:
+  - name: http
+    nodePort: 32417
+    port: 80
+    protocol: TCP
+    targetPort: 8080
+  selector:
+    app: nginx
+  sessionAffinity: None
+  type: LoadBalancer
+' | kubectl replace -f -
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-replace-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X PUT -H 'Content-Type: application/yaml' --data '
+apiVersion: v1
+kind: Service
+metadata:
+  name: deployment-example
+  resourceVersion: "2205995"
+spec:
+  clusterIP: 10.183.250.161
+  ports:
+  - name: http
+    nodePort: 32417
+    port: 80
+    protocol: TCP
+    targetPort: 8080
+  selector:
+    app: nginx
+  sessionAffinity: None
+  type: LoadBalancer
+' http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-replace-service-v1-core" aria-controls="res-kubectl-replace-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-replace-service-v1-core" aria-controls="res-curl-replace-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-replace-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+service "deployment-example" replaced
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-replace-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Service",
+  "apiVersion": "v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/api/v1/namespaces/default/services/deployment-example",
+    "uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+    "resourceVersion": "2208672",
+    "creationTimestamp": "2016-10-28T17:04:24Z"
+  },
+  "spec": {
+    "ports": [
+      {
+        "name": "http",
+        "protocol": "TCP",
+        "port": 80,
+        "targetPort": 8080,
+        "nodePort": 32417
+      }
+    ],
+    "selector": {
+      "app": "nginx"
+    },
+    "clusterIP": "10.183.250.161",
+    "type": "LoadBalancer",
+    "sessionAffinity": "None"
+  },
+  "status": {
+    "loadBalancer": {
+      "ingress": [
+        {
+          "ip": "104.198.186.106"
+        }
+      ]
+    }
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>replace the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-service-v1-core">Delete</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-delete-service-v1-core" aria-controls="req-kubectl-delete-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-delete-service-v1-core" aria-controls="req-curl-delete-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-delete-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl delete service deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-delete-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
+gracePeriodSeconds: 0
+orphanDependents: false
+' 'http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-delete-service-v1-core" aria-controls="res-kubectl-delete-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-delete-service-v1-core" aria-controls="res-curl-delete-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-delete-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+service "deployment-example" deleted
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-delete-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Status",
+  "apiVersion": "v1",
+  "metadata": {},
+  "status": "Success",
+  "code": 200
+}
+
+</CODE></PRE></DIV></DIV></DIV>
+<P>delete a Service</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-service-v1-core">Delete Collection</H2>
+<P>delete collection of Service</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/services</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-service-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-service-v1-core">Read</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-read-service-v1-core" aria-controls="req-kubectl-read-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-read-service-v1-core" aria-controls="req-curl-read-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-read-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get service deployment-example -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-read-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-read-service-v1-core" aria-controls="res-kubectl-read-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-read-service-v1-core" aria-controls="res-curl-read-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-read-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+  "kind": "Service",
+  "apiVersion": "v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/api/v1/namespaces/default/services/deployment-example",
+    "uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+    "resourceVersion": "2205995",
+    "creationTimestamp": "2016-10-28T17:04:24Z"
+  },
+  "spec": {
+    "ports": [
+      {
+        "name": "http",
+        "protocol": "TCP",
+        "port": 80,
+        "targetPort": 8080,
+        "nodePort": 32417
+      }
+    ],
+    "selector": {
+      "app": "nginx"
+    },
+    "clusterIP": "10.183.250.161",
+    "type": "LoadBalancer",
+    "sessionAffinity": "None"
+  },
+  "status": {
+    "loadBalancer": {
+      "ingress": [
+        {
+          "ip": "104.198.186.106"
+        }
+      ]
+    }
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-read-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+  "kind": "Service",
+  "apiVersion": "v1",
+  "metadata": {
+    "name": "deployment-example",
+    "namespace": "default",
+    "selfLink": "/api/v1/namespaces/default/services/deployment-example",
+    "uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+    "resourceVersion": "2205995",
+    "creationTimestamp": "2016-10-28T17:04:24Z"
+  },
+  "spec": {
+    "ports": [
+      {
+        "name": "http",
+        "protocol": "TCP",
+        "port": 80,
+        "targetPort": 8080,
+        "nodePort": 32417
+      }
+    ],
+    "selector": {
+      "app": "nginx"
+    },
+    "clusterIP": "10.183.250.161",
+    "type": "LoadBalancer",
+    "sessionAffinity": "None"
+  },
+  "status": {
+    "loadBalancer": {
+      "ingress": [
+        {
+          "ip": "104.198.186.106"
+        }
+      ]
+    }
+  }
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>read the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/services/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-service-v1-core">List</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-list-service-v1-core" aria-controls="req-kubectl-list-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-list-service-v1-core" aria-controls="req-curl-list-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-list-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get service -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-list-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/api/v1/namespaces/default/services'
+</CODE></PRE></DIV></DIV></DIV>
+<P>list or watch objects of kind Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/services</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#servicelist-v1-core">ServiceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-service-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/services</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#servicelist-v1-core">ServiceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-service-v1-core">Watch</H2>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-kubectl-watch-service-v1-core" aria-controls="req-kubectl-watch-service-v1-core"
+  aria-expanded="false">kubectl request example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#req-curl-watch-service-v1-core" aria-controls="req-curl-watch-service-v1-core"
+  aria-expanded="false">curl request example</BUTTON>
+<DIV class="collapse" id="req-kubectl-watch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-shell">
+$ kubectl get service deployment-example --watch -o json
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="req-curl-watch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-shell">
+$ kubectl proxy
+$ curl -X GET 'http://127.0.0.1:8001/api/v1/watch/namespaces/default/services/deployment-example'
+</CODE></PRE></DIV></DIV></DIV>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-kubectl-watch-service-v1-core" aria-controls="res-kubectl-watch-service-v1-core"
+  aria-expanded="false">kubectl response example</BUTTON>
+<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
+  data-target="#res-curl-watch-service-v1-core" aria-controls="res-curl-watch-service-v1-core"
+  aria-expanded="false">curl response example</BUTTON>
+<DIV class="collapse" id="res-kubectl-watch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Output</DIV>
+  <DIV class="panel-body">
+<PRE class="kubectl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Service",
+		"apiVersion": "v1",
+		"metadata": {
+			"name": "deployment-example",
+			"namespace": "default",
+			"selfLink": "/api/v1/namespaces/default/services/deployment-example",
+			"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+			"resourceVersion": "2205995",
+			"creationTimestamp": "2016-10-28T17:04:24Z"
+		},
+		"spec": {
+			"ports": [
+				{
+					"name": "http",
+					"protocol": "TCP",
+					"port": 80,
+					"targetPort": 8080,
+					"nodePort": 32417
+				}
+			],
+			"selector": {
+				"app": "nginx"
+			},
+			"clusterIP": "10.183.250.161",
+			"type": "LoadBalancer",
+			"sessionAffinity": "None"
+		},
+		"status": {
+			"loadBalancer": {
+				"ingress": [
+					{
+						"ip": "104.198.186.106"
+					}
+				]
+			}
+		}
+	}
+}
+</CODE></PRE></DIV></DIV></DIV>
+<DIV class="collapse" id="res-curl-watch-service-v1-core">
+  <DIV class="panel panel-default">
+<DIV class="panel-heading">Response Body</DIV>
+  <DIV class="panel-body">
+<PRE class="curl"><CODE class="lang-json">
+{
+	"type": "ADDED",
+	"object": {
+		"kind": "Service",
+		"apiVersion": "v1",
+		"metadata": {
+			"name": "deployment-example",
+			"namespace": "default",
+			"selfLink": "/api/v1/namespaces/default/services/deployment-example",
+			"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
+			"resourceVersion": "2205995",
+			"creationTimestamp": "2016-10-28T17:04:24Z"
+		},
+		"spec": {
+			"ports": [
+				{
+					"name": "http",
+					"protocol": "TCP",
+					"port": 80,
+					"targetPort": 8080,
+					"nodePort": 32417
+				}
+			],
+			"selector": {
+				"app": "nginx"
+			},
+			"clusterIP": "10.183.250.161",
+			"type": "LoadBalancer",
+			"sessionAffinity": "None"
+		},
+		"status": {
+			"loadBalancer": {
+				"ingress": [
+					{
+						"ip": "104.198.186.106"
+					}
+				]
+			}
+		}
+	}
+}
+</CODE></PRE></DIV></DIV></DIV>
+<P>watch changes to an object of kind Service. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/services/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-service-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Service. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/services</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-service-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Service. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/services</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-service-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-service-v1-core">Patch Status</H2>
+<P>partially update status of the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-service-v1-core">Read Status</H2>
+<P>read status of the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-service-v1-core">Replace Status</H2>
+<P>replace status of the specified Service</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-proxy-operations-service-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
+<H2 id="create-connect-proxy-service-v1-core">Create Connect Proxy</H2>
+<P>connect POST requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="create-connect-proxy-path-service-v1-core">Create Connect Proxy Path</H2>
+<P>connect POST requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-service-v1-core">Delete Connect Proxy</H2>
+<P>connect DELETE requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-path-service-v1-core">Delete Connect Proxy Path</H2>
+<P>connect DELETE requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-service-v1-core">Get Connect Proxy</H2>
+<P>connect GET requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-path-service-v1-core">Get Connect Proxy Path</H2>
+<P>connect GET requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-service-v1-core">Head Connect Proxy</H2>
+<P>connect HEAD requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-path-service-v1-core">Head Connect Proxy Path</H2>
+<P>connect HEAD requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-service-v1-core">Replace Connect Proxy</H2>
+<P>connect PUT requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-path-service-v1-core">Replace Connect Proxy Path</H2>
+<P>connect PUT requests to proxy of Service</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-config-and-storage-apis-strong-"><STRONG>CONFIG & STORAGE</STRONG></H1>
+
+<P>Config and Storage resources are responsible for injecting data into your applications and persisting data externally to your container.</P>
+
+<P>Common resource types:</P>
+<UL>
+<LI><A href="#configmap-v1-core">ConfigMaps</A> for providing text key value pairs injected into the application through environment variables, command line arguments, or files</LI>
+<LI><A href="#secret-v1-core">Secrets</A> for providing binary data injected into the application through files</LI>
+<LI><A href="#volume-v1-core">Volumes</A> 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.</LI>
+</UL>
+<HR />
+<H1 id="configmap-v1-core">ConfigMap v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMap</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#configmaplist-v1-core">ConfigMapList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>binaryData</CODE><BR /><I>object</I></TD><TD>BinaryData contains the binary data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet.</TD></TR>
+<TR><TD><CODE>data</CODE><BR /><I>object</I></TD><TD>Data contains the configuration data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. Values with non-UTF-8 byte sequences must use the BinaryData field. The keys stored in Data must not overlap with the keys in the BinaryData field, this is enforced during validation process.</TD></TR>
+<TR><TD><CODE>immutable</CODE><BR /><I>boolean</I></TD><TD>Immutable, if set to true, ensures that data stored in the ConfigMap cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="configmaplist-v1-core">ConfigMapList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#configmap-v1-core">ConfigMap</a> array</I></TD><TD>Items is the list of ConfigMaps.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-configmap-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-configmap-v1-core">Create</H2>
+<P>create a ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/configmaps</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-configmap-v1-core">Patch</H2>
+<P>partially update the specified ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-configmap-v1-core">Replace</H2>
+<P>replace the specified ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-configmap-v1-core">Delete</H2>
+<P>delete a ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-configmap-v1-core">Delete Collection</H2>
+<P>delete collection of ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/configmaps</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-configmap-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-configmap-v1-core">Read</H2>
+<P>read the specified ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-configmap-v1-core">List</H2>
+<P>list or watch objects of kind ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/configmaps</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmaplist-v1-core">ConfigMapList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-configmap-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind ConfigMap</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/configmaps</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#configmaplist-v1-core">ConfigMapList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-configmap-v1-core">Watch</H2>
+<P>watch changes to an object of kind ConfigMap. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-configmap-v1-core">Watch List</H2>
+<P>watch individual changes to a list of ConfigMap. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-configmap-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ConfigMap. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/configmaps</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="csidriver-v1-storage-k8s-io">CSIDriver v1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSIDriver</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csidriverlist-v1-storage-k8s-io">CSIDriverList [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. metadata.Name indicates the name of the CSI driver that this object refers to; it MUST be the same name returned by the CSI GetPluginName() call for that driver. The driver name must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and alphanumerics between. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#csidriverspec-v1-storage-k8s-io">CSIDriverSpec</a></I></TD><TD>Specification of the CSI Driver.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csidriverspec-v1-storage-k8s-io">CSIDriverSpec v1 storage</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csidriver-v1-storage-k8s-io">CSIDriver [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>attachRequired</CODE><BR /><I>boolean</I></TD><TD>attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called.  This field is immutable.</TD></TR>
+<TR><TD><CODE>fsGroupPolicy</CODE><BR /><I>string</I></TD><TD>Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details.  This field is immutable.  Defaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume&#39;s access mode contains ReadWriteOnce.</TD></TR>
+<TR><TD><CODE>podInfoOnMount</CODE><BR /><I>boolean</I></TD><TD>If set to true, podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. &#34;csi.storage.k8s.io/pod.name&#34;: pod.Name &#34;csi.storage.k8s.io/pod.namespace&#34;: pod.Namespace &#34;csi.storage.k8s.io/pod.uid&#34;: string(pod.UID) &#34;csi.storage.k8s.io/ephemeral&#34;: &#34;true&#34; if the volume is an ephemeral inline volume                                 defined by a CSIVolumeSource, otherwise &#34;false&#34;  &#34;csi.storage.k8s.io/ephemeral&#34; is a new feature in Kubernetes 1.16. It is only required for drivers which support both the &#34;Persistent&#34; and &#34;Ephemeral&#34; VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn&#39;t support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver.  This field is immutable.</TD></TR>
+<TR><TD><CODE>requiresRepublish</CODE><BR /><I>boolean</I></TD><TD>RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.  Note: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.</TD></TR>
+<TR><TD><CODE>storageCapacity</CODE><BR /><I>boolean</I></TD><TD>If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.  The check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.  Alternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.  This field was immutable in Kubernetes &lt;= 1.22 and now is mutable.  This is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.</TD></TR>
+<TR><TD><CODE>tokenRequests</CODE><BR /><I><a href="#tokenrequest-v1-storage-k8s-io">TokenRequest</a> array</I></TD><TD>TokenRequests indicates the CSI driver needs pods&#39; service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: &#34;csi.storage.k8s.io/serviceAccount.tokens&#34;: {   &#34;&lt;audience&gt;&#34;: {     &#34;token&#34;: &lt;token&gt;,     &#34;expirationTimestamp&#34;: &lt;expiration timestamp in RFC3339&gt;,   },   ... }  Note: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.</TD></TR>
+<TR><TD><CODE>volumeLifecycleModes</CODE><BR /><I>string array</I></TD><TD>volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is &#34;Persistent&#34;, which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is &#34;Ephemeral&#34;. In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future. This field is beta.  This field is immutable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csidriverlist-v1-storage-k8s-io">CSIDriverList v1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a> array</I></TD><TD>items is the list of CSIDriver</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-csidriver-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-csidriver-v1-storage-k8s-io">Create</H2>
+<P>create a CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1/csidrivers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-csidriver-v1-storage-k8s-io">Patch</H2>
+<P>partially update the specified CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/csidrivers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-csidriver-v1-storage-k8s-io">Replace</H2>
+<P>replace the specified CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/csidrivers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-csidriver-v1-storage-k8s-io">Delete</H2>
+<P>delete a CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/csidrivers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-csidriver-v1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/csidrivers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-csidriver-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-csidriver-v1-storage-k8s-io">Read</H2>
+<P>read the specified CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/csidrivers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-csidriver-v1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind CSIDriver</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/csidrivers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csidriverlist-v1-storage-k8s-io">CSIDriverList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-csidriver-v1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CSIDriver. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/csidrivers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-csidriver-v1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CSIDriver. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/csidrivers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="csinode-v1-storage-k8s-io">CSINode v1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSINode</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csinodelist-v1-storage-k8s-io">CSINodeList [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>metadata.name must be the Kubernetes node name.</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#csinodespec-v1-storage-k8s-io">CSINodeSpec</a></I></TD><TD>spec is the specification of CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csinodespec-v1-storage-k8s-io">CSINodeSpec v1 storage</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csinode-v1-storage-k8s-io">CSINode [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>drivers</CODE><BR /><I><a href="#csinodedriver-v1-storage-k8s-io">CSINodeDriver</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>drivers is a list of information of all CSI Drivers existing on a node. If all drivers in the list are uninstalled, this can become empty.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csinodelist-v1-storage-k8s-io">CSINodeList v1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a> array</I></TD><TD>items is the list of CSINode</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-csinode-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-csinode-v1-storage-k8s-io">Create</H2>
+<P>create a CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1/csinodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-csinode-v1-storage-k8s-io">Patch</H2>
+<P>partially update the specified CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/csinodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-csinode-v1-storage-k8s-io">Replace</H2>
+<P>replace the specified CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/csinodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-csinode-v1-storage-k8s-io">Delete</H2>
+<P>delete a CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/csinodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-csinode-v1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/csinodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-csinode-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-csinode-v1-storage-k8s-io">Read</H2>
+<P>read the specified CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/csinodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-csinode-v1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind CSINode</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/csinodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csinodelist-v1-storage-k8s-io">CSINodeList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-csinode-v1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CSINode. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/csinodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-csinode-v1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CSINode. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/csinodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="secret-v1-core">Secret v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Secret</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#secretlist-v1-core">SecretList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>data</CODE><BR /><I>object</I></TD><TD>Data contains the secret data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4</TD></TR>
+<TR><TD><CODE>immutable</CODE><BR /><I>boolean</I></TD><TD>Immutable, if set to true, ensures that data stored in the Secret cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>stringData</CODE><BR /><I>object</I></TD><TD>stringData allows specifying non-binary secret data in string form. It is provided as a write-only input field for convenience. All keys and values are merged into the data field on write, overwriting any existing values. The stringData field is never output when reading from the API.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Used to facilitate programmatic handling of secret data. More info: https://kubernetes.io/docs/concepts/configuration/secret/#secret-types</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="secretlist-v1-core">SecretList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#secret-v1-core">Secret</a> array</I></TD><TD>Items is a list of secret objects. More info: https://kubernetes.io/docs/concepts/configuration/secret</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-secret-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-secret-v1-core">Create</H2>
+<P>create a Secret</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/secrets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-secret-v1-core">Patch</H2>
+<P>partially update the specified Secret</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-secret-v1-core">Replace</H2>
+<P>replace the specified Secret</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-secret-v1-core">Delete</H2>
+<P>delete a Secret</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-secret-v1-core">Delete Collection</H2>
+<P>delete collection of Secret</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/secrets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-secret-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-secret-v1-core">Read</H2>
+<P>read the specified Secret</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-secret-v1-core">List</H2>
+<P>list or watch objects of kind Secret</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/secrets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secretlist-v1-core">SecretList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-secret-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind Secret</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/secrets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#secretlist-v1-core">SecretList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-secret-v1-core">Watch</H2>
+<P>watch changes to an object of kind Secret. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/secrets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-secret-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Secret. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/secrets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-secret-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Secret. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/secrets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="persistentvolumeclaim-v1-core">PersistentVolumeClaim v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaim</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-bullhorn"></I> A <a href="#persistentvolume-v1-core">PersistentVolume</a> must be allocated in the cluster to use this.</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList [core/v1]</a></LI>
+  <LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec</a></I></TD><TD>Spec defines the desired characteristics of a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus</a></I></TD><TD>Status represents the current information/status of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1</TD></TR>
+<TR><TD><CODE>dataSource</CODE><BR /><I><a href="#typedlocalobjectreference-v1-core">TypedLocalObjectReference</a></I></TD><TD>This field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. If the AnyVolumeDataSource feature gate is enabled, this field will always have the same contents as the DataSourceRef field.</TD></TR>
+<TR><TD><CODE>dataSourceRef</CODE><BR /><I><a href="#typedlocalobjectreference-v1-core">TypedLocalObjectReference</a></I></TD><TD>Specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any local object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the DataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, both fields (DataSource and DataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. There are two important differences between DataSource and DataSourceRef: * While DataSource only allows two specific types of objects, DataSourceRef   allows any non-core object, as well as PersistentVolumeClaim objects. * While DataSource ignores disallowed values (dropping them), DataSourceRef   preserves all values, and generates an error if a disallowed value is   specified. (Alpha) Using this field requires the AnyVolumeDataSource feature gate to be enabled.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over volumes to consider for binding.</TD></TR>
+<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>Name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1</TD></TR>
+<TR><TD><CODE>volumeMode</CODE><BR /><I>string</I></TD><TD>volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the binding reference to the PersistentVolume backing this claim.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains the actual access modes the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1</TD></TR>
+<TR><TD><CODE>allocatedResources</CODE><BR /><I>object</I></TD><TD>The storage resource within AllocatedResources tracks the capacity allocated to a PVC. It may be larger than the actual capacity when a volume expansion operation is requested. For storage quota, the larger value from allocatedResources and PVC.spec.resources is used. If allocatedResources is not set, PVC.spec.resources alone is used for quota calculation. If a volume expansion capacity request is lowered, allocatedResources is only lowered if there are no expansion operations in progress and if the actual volume capacity is equal or lower than the requested capacity. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.</TD></TR>
+<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Represents the actual resources of the underlying volume.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to &#39;ResizeStarted&#39;.</TD></TR>
+<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase represents the current phase of PersistentVolumeClaim.  Possible enum values:  - `&#34;Bound&#34;` used for PersistentVolumeClaims that are bound  - `&#34;Lost&#34;` used for PersistentVolumeClaims that lost their underlying PersistentVolume. The claim was bound to a PersistentVolume and this volume does not exist any longer and all data on it was lost.  - `&#34;Pending&#34;` used for PersistentVolumeClaims that are not yet bound</TD></TR>
+<TR><TD><CODE>resizeStatus</CODE><BR /><I>string</I></TD><TD>ResizeStatus stores status of resize operation. ResizeStatus is not set by default but when expansion is complete resizeStatus is set to empty string by resize controller or kubelet. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>A list of persistent volume claims. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-persistentvolumeclaim-v1-core">Create</H2>
+<P>create a PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-persistentvolumeclaim-v1-core">Patch</H2>
+<P>partially update the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-persistentvolumeclaim-v1-core">Replace</H2>
+<P>replace the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-persistentvolumeclaim-v1-core">Delete</H2>
+<P>delete a PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-persistentvolumeclaim-v1-core">Delete Collection</H2>
+<P>delete collection of PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-persistentvolumeclaim-v1-core">Read</H2>
+<P>read the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-persistentvolumeclaim-v1-core">List</H2>
+<P>list or watch objects of kind PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-persistentvolumeclaim-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/persistentvolumeclaims</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-persistentvolumeclaim-v1-core">Watch</H2>
+<P>watch changes to an object of kind PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-persistentvolumeclaim-v1-core">Watch List</H2>
+<P>watch individual changes to a list of PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-persistentvolumeclaim-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/persistentvolumeclaims</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-persistentvolumeclaim-v1-core">Patch Status</H2>
+<P>partially update status of the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-persistentvolumeclaim-v1-core">Read Status</H2>
+<P>read status of the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-persistentvolumeclaim-v1-core">Replace Status</H2>
+<P>replace status of the specified PersistentVolumeClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="storageclass-v1-storage-k8s-io">StorageClass v1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowVolumeExpansion</CODE><BR /><I>boolean</I></TD><TD>AllowVolumeExpansion shows whether the storage class allow volume expand</TD></TR>
+<TR><TD><CODE>allowedTopologies</CODE><BR /><I><a href="#topologyselectorterm-v1-core">TopologySelectorTerm</a> array</I></TD><TD>Restrict the node topologies where volumes can be dynamically provisioned. Each volume plugin defines its own supported topology specifications. An empty TopologySelectorTerm list means there is no topology restriction. This field is only honored by servers that enable the VolumeScheduling feature.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [&#34;ro&#34;, &#34;soft&#34;]. Not validated - mount of the PVs will simply fail if one is invalid.</TD></TR>
+<TR><TD><CODE>parameters</CODE><BR /><I>object</I></TD><TD>Parameters holds the parameters for the provisioner that should create volumes of this storage class.</TD></TR>
+<TR><TD><CODE>provisioner</CODE><BR /><I>string</I></TD><TD>Provisioner indicates the type of the provisioner.</TD></TR>
+<TR><TD><CODE>reclaimPolicy</CODE><BR /><I>string</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.</TD></TR>
+<TR><TD><CODE>volumeBindingMode</CODE><BR /><I>string</I></TD><TD>VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound.  When unset, VolumeBindingImmediate is used. This field is only honored by servers that enable the VolumeScheduling feature.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="storageclasslist-v1-storage-k8s-io">StorageClassList v1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a> array</I></TD><TD>Items is the list of StorageClasses</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-storageclass-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-storageclass-v1-storage-k8s-io">Create</H2>
+<P>create a StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1/storageclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-storageclass-v1-storage-k8s-io">Patch</H2>
+<P>partially update the specified StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-storageclass-v1-storage-k8s-io">Replace</H2>
+<P>replace the specified StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-storageclass-v1-storage-k8s-io">Delete</H2>
+<P>delete a StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-storageclass-v1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/storageclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-storageclass-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-storageclass-v1-storage-k8s-io">Read</H2>
+<P>read the specified StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-storageclass-v1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind StorageClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/storageclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-storageclass-v1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind StorageClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-storageclass-v1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of StorageClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity v1beta1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CSIStorageCapacity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#csistoragecapacity-v1alpha1-storage-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csistoragecapacitylist-v1beta1-storage-k8s-io">CSIStorageCapacityList [storage/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>capacity</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.  The semantic is currently (CSI spec 1.2) defined as: The available capacity, in bytes, of the storage that can be used to provision volumes. If not set, that information is currently unavailable and treated like zero capacity.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>maximumVolumeSize</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.  This is defined since CSI spec 1.4.0 as the largest size that may be used in a CreateVolumeRequest.capacity_range.required_bytes field to create a volume with the same parameters as those in GetCapacityRequest. The corresponding value in the Kubernetes API is ResourceRequirements.Requests in a volume claim.</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. The name has no particular meaning. It must be be a DNS subdomain (dots allowed, 253 characters). To ensure that there are no conflicts with other CSI drivers on the cluster, the recommendation is to use csisc-&lt;uuid&gt;, a generated name, or a reverse-domain name which ends with the unique CSI driver name.  Objects are namespaced.  More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>nodeTopology</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>NodeTopology defines which nodes have access to the storage for which capacity was reported. If not set, the storage is not accessible from any node in the cluster. If empty, the storage is accessible from all nodes. This field is immutable.</TD></TR>
+<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>The name of the StorageClass that the reported capacity applies to. It must meet the same requirements as the name of a StorageClass object (non-empty, DNS subdomain). If that object no longer exists, the CSIStorageCapacity object is obsolete and should be removed by its creator. This field is immutable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csistoragecapacitylist-v1beta1-storage-k8s-io">CSIStorageCapacityList v1beta1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a> array</I></TD><TD>Items is the list of CSIStorageCapacity objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-csistoragecapacity-v1beta1-storage-k8s-io">Create</H2>
+<P>create a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-csistoragecapacity-v1beta1-storage-k8s-io">Patch</H2>
+<P>partially update the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-csistoragecapacity-v1beta1-storage-k8s-io">Replace</H2>
+<P>replace the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-csistoragecapacity-v1beta1-storage-k8s-io">Delete</H2>
+<P>delete a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-csistoragecapacity-v1beta1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-csistoragecapacity-v1beta1-storage-k8s-io">Read</H2>
+<P>read the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-csistoragecapacity-v1beta1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1beta1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/csistoragecapacities</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1beta1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-csistoragecapacity-v1beta1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/watch/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-csistoragecapacity-v1beta1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/watch/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1beta1/watch/csistoragecapacities</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="volume-v1-core">Volume v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Volume</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>awsElasticBlockStore</CODE><BR /><I><a href="#awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource</a></I></TD><TD>AWSElasticBlockStore represents an AWS Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+<TR><TD><CODE>azureDisk</CODE><BR /><I><a href="#azurediskvolumesource-v1-core">AzureDiskVolumeSource</a></I></TD><TD>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</TD></TR>
+<TR><TD><CODE>azureFile</CODE><BR /><I><a href="#azurefilevolumesource-v1-core">AzureFileVolumeSource</a></I></TD><TD>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</TD></TR>
+<TR><TD><CODE>cephfs</CODE><BR /><I><a href="#cephfsvolumesource-v1-core">CephFSVolumeSource</a></I></TD><TD>CephFS represents a Ceph FS mount on the host that shares a pod&#39;s lifetime</TD></TR>
+<TR><TD><CODE>cinder</CODE><BR /><I><a href="#cindervolumesource-v1-core">CinderVolumeSource</a></I></TD><TD>Cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapvolumesource-v1-core">ConfigMapVolumeSource</a></I></TD><TD>ConfigMap represents a configMap that should populate this volume</TD></TR>
+<TR><TD><CODE>csi</CODE><BR /><I><a href="#csivolumesource-v1-core">CSIVolumeSource</a></I></TD><TD>CSI (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).</TD></TR>
+<TR><TD><CODE>downwardAPI</CODE><BR /><I><a href="#downwardapivolumesource-v1-core">DownwardAPIVolumeSource</a></I></TD><TD>DownwardAPI represents downward API about the pod that should populate this volume</TD></TR>
+<TR><TD><CODE>emptyDir</CODE><BR /><I><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource</a></I></TD><TD>EmptyDir represents a temporary directory that shares a pod&#39;s lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir</TD></TR>
+<TR><TD><CODE>ephemeral</CODE><BR /><I><a href="#ephemeralvolumesource-v1-core">EphemeralVolumeSource</a></I></TD><TD>Ephemeral represents a volume that is handled by a cluster storage driver. The volume&#39;s lifecycle is tied to the pod that defines it - it will be created before the pod starts, and deleted when the pod is removed.  Use this if: a) the volume is only needed while the pod runs, b) features of normal volumes like restoring from snapshot or capacity    tracking are needed, c) the storage driver is specified through a storage class, and d) the storage driver supports dynamic volume provisioning through    a PersistentVolumeClaim (see EphemeralVolumeSource for more    information on the connection between this volume type    and PersistentVolumeClaim).  Use PersistentVolumeClaim or one of the vendor-specific APIs for volumes that persist for longer than the lifecycle of an individual pod.  Use CSI for light-weight local ephemeral volumes if the CSI driver is meant to be used that way - see the documentation of the driver for more information.  A pod can use both types of ephemeral volumes and persistent volumes at the same time.</TD></TR>
+<TR><TD><CODE>fc</CODE><BR /><I><a href="#fcvolumesource-v1-core">FCVolumeSource</a></I></TD><TD>FC represents a Fibre Channel resource that is attached to a kubelet&#39;s host machine and then exposed to the pod.</TD></TR>
+<TR><TD><CODE>flexVolume</CODE><BR /><I><a href="#flexvolumesource-v1-core">FlexVolumeSource</a></I></TD><TD>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</TD></TR>
+<TR><TD><CODE>flocker</CODE><BR /><I><a href="#flockervolumesource-v1-core">FlockerVolumeSource</a></I></TD><TD>Flocker represents a Flocker volume attached to a kubelet&#39;s host machine. This depends on the Flocker control service being running</TD></TR>
+<TR><TD><CODE>gcePersistentDisk</CODE><BR /><I><a href="#gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource</a></I></TD><TD>GCEPersistentDisk represents a GCE Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+<TR><TD><CODE>gitRepo</CODE><BR /><I><a href="#gitrepovolumesource-v1-core">GitRepoVolumeSource</a></I></TD><TD>GitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod&#39;s container.</TD></TR>
+<TR><TD><CODE>glusterfs</CODE><BR /><I><a href="#glusterfsvolumesource-v1-core">GlusterfsVolumeSource</a></I></TD><TD>Glusterfs represents a Glusterfs mount on the host that shares a pod&#39;s lifetime. More info: https://examples.k8s.io/volumes/glusterfs/README.md</TD></TR>
+<TR><TD><CODE>hostPath</CODE><BR /><I><a href="#hostpathvolumesource-v1-core">HostPathVolumeSource</a></I></TD><TD>HostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
+<TR><TD><CODE>iscsi</CODE><BR /><I><a href="#iscsivolumesource-v1-core">ISCSIVolumeSource</a></I></TD><TD>ISCSI represents an ISCSI Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://examples.k8s.io/volumes/iscsi/README.md</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Volume&#39;s name. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>nfs</CODE><BR /><I><a href="#nfsvolumesource-v1-core">NFSVolumeSource</a></I></TD><TD>NFS represents an NFS mount on the host that shares a pod&#39;s lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
+<TR><TD><CODE>persistentVolumeClaim</CODE><BR /><I><a href="#persistentvolumeclaimvolumesource-v1-core">PersistentVolumeClaimVolumeSource</a></I></TD><TD>PersistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
+<TR><TD><CODE>photonPersistentDisk</CODE><BR /><I><a href="#photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource</a></I></TD><TD>PhotonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine</TD></TR>
+<TR><TD><CODE>portworxVolume</CODE><BR /><I><a href="#portworxvolumesource-v1-core">PortworxVolumeSource</a></I></TD><TD>PortworxVolume represents a portworx volume attached and mounted on kubelets host machine</TD></TR>
+<TR><TD><CODE>projected</CODE><BR /><I><a href="#projectedvolumesource-v1-core">ProjectedVolumeSource</a></I></TD><TD>Items for all in one resources secrets, configmaps, and downward API</TD></TR>
+<TR><TD><CODE>quobyte</CODE><BR /><I><a href="#quobytevolumesource-v1-core">QuobyteVolumeSource</a></I></TD><TD>Quobyte represents a Quobyte mount on the host that shares a pod&#39;s lifetime</TD></TR>
+<TR><TD><CODE>rbd</CODE><BR /><I><a href="#rbdvolumesource-v1-core">RBDVolumeSource</a></I></TD><TD>RBD represents a Rados Block Device mount on the host that shares a pod&#39;s lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md</TD></TR>
+<TR><TD><CODE>scaleIO</CODE><BR /><I><a href="#scaleiovolumesource-v1-core">ScaleIOVolumeSource</a></I></TD><TD>ScaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.</TD></TR>
+<TR><TD><CODE>secret</CODE><BR /><I><a href="#secretvolumesource-v1-core">SecretVolumeSource</a></I></TD><TD>Secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret</TD></TR>
+<TR><TD><CODE>storageos</CODE><BR /><I><a href="#storageosvolumesource-v1-core">StorageOSVolumeSource</a></I></TD><TD>StorageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.</TD></TR>
+<TR><TD><CODE>vsphereVolume</CODE><BR /><I><a href="#vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource</a></I></TD><TD>VsphereVolume represents a vSphere volume attached and mounted on kubelets host machine</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="volumeattachment-v1-storage-k8s-io">VolumeAttachment v1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeAttachment</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec</a></I></TD><TD>Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#volumeattachmentstatus-v1-storage-k8s-io">VolumeAttachmentStatus</a></I></TD><TD>Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec v1 storage</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>attacher</CODE><BR /><I>string</I></TD><TD>Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().</TD></TR>
+<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>The node that the volume should be attached to.</TD></TR>
+<TR><TD><CODE>source</CODE><BR /><I><a href="#volumeattachmentsource-v1-storage-k8s-io">VolumeAttachmentSource</a></I></TD><TD>Source represents the volume that should be attached.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="volumeattachmentstatus-v1-storage-k8s-io">VolumeAttachmentStatus v1 storage</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>attachError</CODE><BR /><I><a href="#volumeerror-v1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
+<TR><TD><CODE>attached</CODE><BR /><I>boolean</I></TD><TD>Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
+<TR><TD><CODE>attachmentMetadata</CODE><BR /><I>object</I></TD><TD>Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
+<TR><TD><CODE>detachError</CODE><BR /><I><a href="#volumeerror-v1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList v1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a> array</I></TD><TD>Items is the list of VolumeAttachments</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-volumeattachment-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-volumeattachment-v1-storage-k8s-io">Create</H2>
+<P>create a VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1/volumeattachments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-volumeattachment-v1-storage-k8s-io">Patch</H2>
+<P>partially update the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-volumeattachment-v1-storage-k8s-io">Replace</H2>
+<P>replace the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-volumeattachment-v1-storage-k8s-io">Delete</H2>
+<P>delete a VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-volumeattachment-v1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/volumeattachments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-volumeattachment-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-volumeattachment-v1-storage-k8s-io">Read</H2>
+<P>read the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-volumeattachment-v1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/volumeattachments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-volumeattachment-v1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind VolumeAttachment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/volumeattachments/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-volumeattachment-v1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of VolumeAttachment. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/watch/volumeattachments</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-volumeattachment-v1-storage-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-volumeattachment-v1-storage-k8s-io">Patch Status</H2>
+<P>partially update status of the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-volumeattachment-v1-storage-k8s-io">Read Status</H2>
+<P>read status of the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-volumeattachment-v1-storage-k8s-io">Replace Status</H2>
+<P>replace status of the specified VolumeAttachment</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-metadata-apis-strong-"><STRONG>METADATA</STRONG></H1>
+
+<P>Metadata resources are responsible for configuring behavior of your other Resources within the Cluster.</P>
+
+<P>Common resource types:</P>
+<UL>
+<LI><A href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</A> (HPA) for automatically scaling the replicacount of your workloads in response to load.</LI>
+<LI><A href="#poddisruptionbudget-v1alpha1">PodDisruptionBudget</A> for configuring how many replicas in a given workload maybe made concurrently unavailable when performing maintenance.</LI>
+<LI><A href="#event-v1-core">Event</A> for notification of resource lifecycle events in the cluster.</LI>
+</UL>
+<HR />
+<H1 id="controllerrevision-v1-apps">ControllerRevision v1 apps</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ControllerRevision</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>data</CODE></TD><TD>Data is the serialized representation of the state.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>Revision indicates the revision of the state represented by Data.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="controllerrevisionlist-v1-apps">ControllerRevisionList v1 apps</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a> array</I></TD><TD>Items is the list of ControllerRevisions</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-controllerrevision-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-controllerrevision-v1-apps">Create</H2>
+<P>create a ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-controllerrevision-v1-apps">Patch</H2>
+<P>partially update the specified ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-controllerrevision-v1-apps">Replace</H2>
+<P>replace the specified ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-controllerrevision-v1-apps">Delete</H2>
+<P>delete a ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-controllerrevision-v1-apps">Delete Collection</H2>
+<P>delete collection of ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-controllerrevision-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-controllerrevision-v1-apps">Read</H2>
+<P>read the specified ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-controllerrevision-v1-apps">List</H2>
+<P>list or watch objects of kind ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-controllerrevision-v1-apps">List All Namespaces</H2>
+<P>list or watch objects of kind ControllerRevision</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/controllerrevisions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-controllerrevision-v1-apps">Watch</H2>
+<P>watch changes to an object of kind ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-controllerrevision-v1-apps">Watch List</H2>
+<P>watch individual changes to a list of ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-controllerrevision-v1-apps">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apps/v1/watch/controllerrevisions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition v1 apiextensions.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceDefinition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec</a></I></TD><TD>spec describes how the user wants the resources to appear</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus</a></I></TD><TD>status indicates the actual state of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec v1 apiextensions</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conversion</CODE><BR /><I><a href="#customresourceconversion-v1-apiextensions-k8s-io">CustomResourceConversion</a></I></TD><TD>conversion defines conversion settings for the CRD.</TD></TR>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>group is the API group of the defined custom resource. The custom resources are served under `/apis/&lt;group&gt;/...`. Must match the name of the CustomResourceDefinition (in the form `&lt;names.plural&gt;.&lt;group&gt;`).</TD></TR>
+<TR><TD><CODE>names</CODE><BR /><I><a href="#customresourcedefinitionnames-v1-apiextensions-k8s-io">CustomResourceDefinitionNames</a></I></TD><TD>names specify the resource and kind names for the custom resource.</TD></TR>
+<TR><TD><CODE>preserveUnknownFields</CODE><BR /><I>boolean</I></TD><TD>preserveUnknownFields indicates that object fields which are not specified in the OpenAPI schema should be preserved when persisting to storage. apiVersion, kind, metadata and known fields inside metadata are always preserved. This field is deprecated in favor of setting `x-preserve-unknown-fields` to true in `spec.versions[*].schema.openAPIV3Schema`. See https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#pruning-versus-preserving-unknown-fields for details.</TD></TR>
+<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope indicates whether the defined custom resource is cluster- or namespace-scoped. Allowed values are `Cluster` and `Namespaced`.</TD></TR>
+<TR><TD><CODE>versions</CODE><BR /><I><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion</a> array</I></TD><TD>versions is the list of all API versions of the defined custom resource. Version names are used to compute the order in which served versions are listed in API discovery. If the version string is &#34;kube-like&#34;, it will sort above non &#34;kube-like&#34; version strings, which are ordered lexicographically. &#34;Kube-like&#34; versions start with a &#34;v&#34;, then are followed by a number (the major version), then optionally the string &#34;alpha&#34; or &#34;beta&#34; and another number (the minor version). These are sorted first by GA &gt; beta &gt; alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus v1 apiextensions</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>acceptedNames</CODE><BR /><I><a href="#customresourcedefinitionnames-v1-apiextensions-k8s-io">CustomResourceDefinitionNames</a></I></TD><TD>acceptedNames are the names that are actually being used to serve discovery. They may be different than the names in spec.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#customresourcedefinitioncondition-v1-apiextensions-k8s-io">CustomResourceDefinitionCondition</a> array</I></TD><TD>conditions indicate state for particular aspects of a CustomResourceDefinition</TD></TR>
+<TR><TD><CODE>storedVersions</CODE><BR /><I>string array</I></TD><TD>storedVersions lists all versions of CustomResources that were ever persisted. Tracking these versions allows a migration path for stored versions in etcd. The field is mutable so a migration controller can finish a migration to another version (ensuring no old objects are left in storage), and then remove the rest of the versions from this list. Versions may not be removed from `spec.versions` while they exist in this list.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList v1 apiextensions</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a> array</I></TD><TD>items list individual CustomResourceDefinition objects</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-customresourcedefinition-v1-apiextensions-k8s-io">Create</H2>
+<P>create a CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-customresourcedefinition-v1-apiextensions-k8s-io">Patch</H2>
+<P>partially update the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-customresourcedefinition-v1-apiextensions-k8s-io">Replace</H2>
+<P>replace the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-customresourcedefinition-v1-apiextensions-k8s-io">Delete</H2>
+<P>delete a CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-customresourcedefinition-v1-apiextensions-k8s-io">Delete Collection</H2>
+<P>delete collection of CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-customresourcedefinition-v1-apiextensions-k8s-io">Read</H2>
+<P>read the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-customresourcedefinition-v1-apiextensions-k8s-io">List</H2>
+<P>list or watch objects of kind CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-customresourcedefinition-v1-apiextensions-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CustomResourceDefinition. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiextensions.k8s.io/v1/watch/customresourcedefinitions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-customresourcedefinition-v1-apiextensions-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CustomResourceDefinition. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiextensions.k8s.io/v1/watch/customresourcedefinitions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-customresourcedefinition-v1-apiextensions-k8s-io">Patch Status</H2>
+<P>partially update status of the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-customresourcedefinition-v1-apiextensions-k8s-io">Read Status</H2>
+<P>read status of the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-customresourcedefinition-v1-apiextensions-k8s-io">Replace Status</H2>
+<P>replace status of the specified CustomResourceDefinition</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="event-v1-events-k8s-io">Event v1 events.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Event</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#event-v1beta1-events-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#eventlist-v1-events-k8s-io">EventList [events/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>action</CODE><BR /><I>string</I></TD><TD>action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>deprecatedCount</CODE><BR /><I>integer</I></TD><TD>deprecatedCount is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedFirstTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>deprecatedFirstTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedLastTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>deprecatedLastTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedSource</CODE><BR /><I><a href="#eventsource-v1-core">EventSource</a></I></TD><TD>deprecatedSource is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>eventTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>eventTime is the time when this Event was first observed. It is required.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>note</CODE><BR /><I>string</I></TD><TD>note is a human-readable description of the status of this operation. Maximal length of the note is 1kB, but libraries should be prepared to handle values up to 64kB.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is why the action was taken. It is human-readable. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>regarding</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>regarding contains the object this Event is about. In most cases it&#39;s an Object reporting controller implements, e.g. ReplicaSetController implements ReplicaSets and this event is emitted because it acts on some changes in a ReplicaSet object.</TD></TR>
+<TR><TD><CODE>related</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>related is the optional secondary object for more complex actions. E.g. when regarding object triggers a creation or deletion of related object.</TD></TR>
+<TR><TD><CODE>reportingController</CODE><BR /><I>string</I></TD><TD>reportingController is the name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`. This field cannot be empty for new Events.</TD></TR>
+<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>reportingInstance is the ID of the controller instance, e.g. `kubelet-xyzf`. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1-events-k8s-io">EventSeries</a></I></TD><TD>series is data about the Event series this event represents or nil if it&#39;s a singleton Event.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of this event (Normal, Warning), new types could be added in the future. It is machine-readable. This field cannot be empty for new Events.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="eventlist-v1-events-k8s-io">EventList v1 events</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1-events-k8s-io">Event</a> array</I></TD><TD>items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-event-v1-events-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-event-v1-events-k8s-io">Create</H2>
+<P>create an Event</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-event-v1-events-k8s-io">Patch</H2>
+<P>partially update the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-event-v1-events-k8s-io">Replace</H2>
+<P>replace the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-event-v1-events-k8s-io">Delete</H2>
+<P>delete an Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-event-v1-events-k8s-io">Delete Collection</H2>
+<P>delete collection of Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-event-v1-events-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-event-v1-events-k8s-io">Read</H2>
+<P>read the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-event-v1-events-k8s-io">List</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-event-v1-events-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-event-v1-events-k8s-io">Watch</H2>
+<P>watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/watch/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-event-v1-events-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/watch/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-event-v1-events-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1/watch/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="limitrange-v1-core">LimitRange v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitRange</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitrangelist-v1-core">LimitRangeList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#limitrangespec-v1-core">LimitRangeSpec</a></I></TD><TD>Spec defines the limits enforced. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="limitrangespec-v1-core">LimitRangeSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitrange-v1-core">LimitRange [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>limits</CODE><BR /><I><a href="#limitrangeitem-v1-core">LimitRangeItem</a> array</I></TD><TD>Limits is the list of LimitRangeItem objects that are enforced.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="limitrangelist-v1-core">LimitRangeList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#limitrange-v1-core">LimitRange</a> array</I></TD><TD>Items is a list of LimitRange objects. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-limitrange-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-limitrange-v1-core">Create</H2>
+<P>create a LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/limitranges</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-limitrange-v1-core">Patch</H2>
+<P>partially update the specified LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-limitrange-v1-core">Replace</H2>
+<P>replace the specified LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-limitrange-v1-core">Delete</H2>
+<P>delete a LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-limitrange-v1-core">Delete Collection</H2>
+<P>delete collection of LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/limitranges</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-limitrange-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-limitrange-v1-core">Read</H2>
+<P>read the specified LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-limitrange-v1-core">List</H2>
+<P>list or watch objects of kind LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/limitranges</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrangelist-v1-core">LimitRangeList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-limitrange-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind LimitRange</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/limitranges</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#limitrangelist-v1-core">LimitRangeList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-limitrange-v1-core">Watch</H2>
+<P>watch changes to an object of kind LimitRange. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-limitrange-v1-core">Watch List</H2>
+<P>watch individual changes to a list of LimitRange. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-limitrange-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of LimitRange. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/limitranges</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler v1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscaler-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscaler-v2beta2-autoscaling">v2beta2</a>
+<a href="#horizontalpodautoscaler-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>current information about the autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec v1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.</TD></TR>
+<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.</TD></TR>
+<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource.</TD></TR>
+<TR><TD><CODE>targetCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus v1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>currentCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU.</TD></TR>
+<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>current number of replicas of pods managed by this autoscaler.</TD></TR>
+<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desired number of replicas of pods managed by this autoscaler.</TD></TR>
+<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>most recent generation observed by this autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList v1 autoscaling</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>list of horizontal pod autoscaler objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-horizontalpodautoscaler-v1-autoscaling">Create</H2>
+<P>create a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-horizontalpodautoscaler-v1-autoscaling">Patch</H2>
+<P>partially update the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-horizontalpodautoscaler-v1-autoscaling">Replace</H2>
+<P>replace the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-horizontalpodautoscaler-v1-autoscaling">Delete</H2>
+<P>delete a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-horizontalpodautoscaler-v1-autoscaling">Delete Collection</H2>
+<P>delete collection of HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-horizontalpodautoscaler-v1-autoscaling">Read</H2>
+<P>read the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-horizontalpodautoscaler-v1-autoscaling">List</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">List All Namespaces</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-horizontalpodautoscaler-v1-autoscaling">Watch</H2>
+<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-horizontalpodautoscaler-v1-autoscaling">Watch List</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-horizontalpodautoscaler-v1-autoscaling">Patch Status</H2>
+<P>partially update status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-horizontalpodautoscaler-v1-autoscaling">Read Status</H2>
+<P>read status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-horizontalpodautoscaler-v1-autoscaling">Replace Status</H2>
+<P>replace status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration v1 admissionregistration.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>MutatingWebhookConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.</TD></TR>
+<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Webhooks is a list of webhooks and the affected resources and operations.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList v1 admissionregistration</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a> array</I></TD><TD>List of MutatingWebhookConfiguration.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Create</H2>
+<P>create a MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Patch</H2>
+<P>partially update the specified MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Replace</H2>
+<P>replace the specified MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Delete</H2>
+<P>delete a MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Delete Collection</H2>
+<P>delete collection of MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Read</H2>
+<P>read the specified MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">List</H2>
+<P>list or watch objects of kind MutatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Watch</H2>
+<P>watch changes to an object of kind MutatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/watch/mutatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of MutatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/watch/mutatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration v1 admissionregistration.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ValidatingWebhookConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.</TD></TR>
+<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Webhooks is a list of webhooks and the affected resources and operations.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList v1 admissionregistration</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a> array</I></TD><TD>List of ValidatingWebhookConfiguration.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Create</H2>
+<P>create a ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Patch</H2>
+<P>partially update the specified ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Replace</H2>
+<P>replace the specified ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Delete</H2>
+<P>delete a ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Delete Collection</H2>
+<P>delete collection of ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Read</H2>
+<P>read the specified ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">List</H2>
+<P>list or watch objects of kind ValidatingWebhookConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ValidatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingwebhookconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ValidatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingwebhookconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podtemplate-v1-core">PodTemplate v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodTemplate</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podtemplatelist-v1-core">PodTemplateList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template defines the pods that will be created from this pod template. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podtemplatespec-v1-core">PodTemplateSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
+  <LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
+  <LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
+  <LI><a href="#podtemplate-v1-core">PodTemplate [core/v1]</a></LI>
+  <LI><a href="#replicasetspec-v1-apps">ReplicaSetSpec [apps/v1]</a></LI>
+  <LI><a href="#replicationcontrollerspec-v1-core">ReplicationControllerSpec [core/v1]</a></LI>
+  <LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#podspec-v1-core">PodSpec</a></I></TD><TD>Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podtemplatelist-v1-core">PodTemplateList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#podtemplate-v1-core">PodTemplate</a> array</I></TD><TD>List of pod templates</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-podtemplate-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-podtemplate-v1-core">Create</H2>
+<P>create a PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/podtemplates</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-podtemplate-v1-core">Patch</H2>
+<P>partially update the specified PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-podtemplate-v1-core">Replace</H2>
+<P>replace the specified PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-podtemplate-v1-core">Delete</H2>
+<P>delete a PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-podtemplate-v1-core">Delete Collection</H2>
+<P>delete collection of PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-podtemplate-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-podtemplate-v1-core">Read</H2>
+<P>read the specified PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-podtemplate-v1-core">List</H2>
+<P>list or watch objects of kind PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/podtemplates</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplatelist-v1-core">PodTemplateList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-podtemplate-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind PodTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/podtemplates</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podtemplatelist-v1-core">PodTemplateList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-podtemplate-v1-core">Watch</H2>
+<P>watch changes to an object of kind PodTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-podtemplate-v1-core">Watch List</H2>
+<P>watch individual changes to a list of PodTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-podtemplate-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of PodTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/podtemplates</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="poddisruptionbudget-v1-policy">PodDisruptionBudget v1 policy</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodDisruptionBudget</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#poddisruptionbudget-v1beta1-policy">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList [policy/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#poddisruptionbudgetspec-v1-policy">PodDisruptionBudgetSpec</a></I></TD><TD>Specification of the desired behavior of the PodDisruptionBudget.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus</a></I></TD><TD>Most recently observed status of the PodDisruptionBudget.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetspec-v1-policy">PodDisruptionBudgetSpec v1 policy</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxUnavailable</CODE></TD><TD>An eviction is allowed if at most &#34;maxUnavailable&#34; pods selected by &#34;selector&#34; are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with &#34;minAvailable&#34;.</TD></TR>
+<TR><TD><CODE>minAvailable</CODE></TD><TD>An eviction is allowed if at least &#34;minAvailable&#34; pods selected by &#34;selector&#34; will still be available after the eviction, i.e. even in the absence of the evicted pod.  So for example you can prevent all voluntary evictions by specifying &#34;100%&#34;.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I><BR /><B>patch strategy</B>: <I>replace</I></TD><TD>Label query over pods whose evictions are managed by the disruption budget. A null selector will match no pods, while an empty ({}) selector will select all pods within the namespace.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus v1 policy</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#condition-v1-meta">Condition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn&#39;t able to compute               the number of allowed disruptions. Therefore no disruptions are               allowed and the status of the condition will be False. - InsufficientPods: The number of pods are either at or below the number                     required by the PodDisruptionBudget. No disruptions are                     allowed and the status of the condition will be False. - SufficientPods: There are more pods than required by the PodDisruptionBudget.                   The condition will be True, and the number of allowed                   disruptions are provided by the disruptionsAllowed property.</TD></TR>
+<TR><TD><CODE>currentHealthy</CODE><BR /><I>integer</I></TD><TD>current number of healthy pods</TD></TR>
+<TR><TD><CODE>desiredHealthy</CODE><BR /><I>integer</I></TD><TD>minimum desired number of healthy pods</TD></TR>
+<TR><TD><CODE>disruptedPods</CODE><BR /><I>object</I></TD><TD>DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn&#39;t occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.</TD></TR>
+<TR><TD><CODE>disruptionsAllowed</CODE><BR /><I>integer</I></TD><TD>Number of pod disruptions that are currently allowed.</TD></TR>
+<TR><TD><CODE>expectedPods</CODE><BR /><I>integer</I></TD><TD>total number of pods counted by this disruption budget</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>Most recent generation observed when updating this PDB status. DisruptionsAllowed and other status information is valid only if observedGeneration equals to PDB&#39;s object generation.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList v1 policy</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a> array</I></TD><TD>Items is a list of PodDisruptionBudgets</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-poddisruptionbudget-v1-policy-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-poddisruptionbudget-v1-policy">Create</H2>
+<P>create a PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-poddisruptionbudget-v1-policy">Patch</H2>
+<P>partially update the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-poddisruptionbudget-v1-policy">Replace</H2>
+<P>replace the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-poddisruptionbudget-v1-policy">Delete</H2>
+<P>delete a PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-poddisruptionbudget-v1-policy">Delete Collection</H2>
+<P>delete collection of PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-poddisruptionbudget-v1-policy-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-poddisruptionbudget-v1-policy">Read</H2>
+<P>read the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-poddisruptionbudget-v1-policy">List</H2>
+<P>list or watch objects of kind PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-poddisruptionbudget-v1-policy">List All Namespaces</H2>
+<P>list or watch objects of kind PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/poddisruptionbudgets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-poddisruptionbudget-v1-policy">Watch</H2>
+<P>watch changes to an object of kind PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/watch/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-poddisruptionbudget-v1-policy">Watch List</H2>
+<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/watch/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-poddisruptionbudget-v1-policy">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/watch/poddisruptionbudgets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-poddisruptionbudget-v1-policy-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-poddisruptionbudget-v1-policy">Patch Status</H2>
+<P>partially update status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-poddisruptionbudget-v1-policy">Read Status</H2>
+<P>read status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-poddisruptionbudget-v1-policy">Replace Status</H2>
+<P>replace status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="priorityclass-v1-scheduling-k8s-io">PriorityClass v1 scheduling.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PriorityClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#priorityclasslist-v1-scheduling-k8s-io">PriorityClassList [scheduling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD>description is an arbitrary string that usually provides guidelines on when this priority class should be used.</TD></TR>
+<TR><TD><CODE>globalDefault</CODE><BR /><I>boolean</I></TD><TD>globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="priorityclasslist-v1-scheduling-k8s-io">PriorityClassList v1 scheduling</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a> array</I></TD><TD>items is the list of PriorityClasses</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-priorityclass-v1-scheduling-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-priorityclass-v1-scheduling-k8s-io">Create</H2>
+<P>create a PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/scheduling.k8s.io/v1/priorityclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-priorityclass-v1-scheduling-k8s-io">Patch</H2>
+<P>partially update the specified PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-priorityclass-v1-scheduling-k8s-io">Replace</H2>
+<P>replace the specified PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-priorityclass-v1-scheduling-k8s-io">Delete</H2>
+<P>delete a PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-priorityclass-v1-scheduling-k8s-io">Delete Collection</H2>
+<P>delete collection of PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/scheduling.k8s.io/v1/priorityclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-priorityclass-v1-scheduling-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-priorityclass-v1-scheduling-k8s-io">Read</H2>
+<P>read the specified PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-priorityclass-v1-scheduling-k8s-io">List</H2>
+<P>list or watch objects of kind PriorityClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/scheduling.k8s.io/v1/priorityclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#priorityclasslist-v1-scheduling-k8s-io">PriorityClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-priorityclass-v1-scheduling-k8s-io">Watch</H2>
+<P>watch changes to an object of kind PriorityClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/scheduling.k8s.io/v1/watch/priorityclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-priorityclass-v1-scheduling-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of PriorityClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/scheduling.k8s.io/v1/watch/priorityclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podsecuritypolicy-v1beta1-policy">PodSecurityPolicy v1beta1 policy</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PodSecurityPolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec</a></I></TD><TD>spec defines the policy enforced.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec v1beta1 policy</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>allowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.</TD></TR>
+<TR><TD><CODE>allowedCSIDrivers</CODE><BR /><I><a href="#allowedcsidriver-v1beta1-policy">AllowedCSIDriver</a> array</I></TD><TD>AllowedCSIDrivers is an allowlist of inline CSI drivers that must be explicitly set to be embedded within a pod spec. An empty value indicates that any CSI driver can be used for inline ephemeral volumes. This is a beta field, and is only honored if the API server enables the CSIInlineVolume feature gate.</TD></TR>
+<TR><TD><CODE>allowedCapabilities</CODE><BR /><I>string array</I></TD><TD>allowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author&#39;s discretion. You must not list a capability in both allowedCapabilities and requiredDropCapabilities.</TD></TR>
+<TR><TD><CODE>allowedFlexVolumes</CODE><BR /><I><a href="#allowedflexvolume-v1beta1-policy">AllowedFlexVolume</a> array</I></TD><TD>allowedFlexVolumes is an allowlist of Flexvolumes.  Empty or nil indicates that all Flexvolumes may be used.  This parameter is effective only when the usage of the Flexvolumes is allowed in the &#34;volumes&#34; field.</TD></TR>
+<TR><TD><CODE>allowedHostPaths</CODE><BR /><I><a href="#allowedhostpath-v1beta1-policy">AllowedHostPath</a> array</I></TD><TD>allowedHostPaths is an allowlist of host paths. Empty indicates that all host paths may be used.</TD></TR>
+<TR><TD><CODE>allowedProcMountTypes</CODE><BR /><I>string array</I></TD><TD>AllowedProcMountTypes is an allowlist of allowed ProcMountTypes. Empty or nil indicates that only the DefaultProcMountType may be used. This requires the ProcMountType feature flag to be enabled.</TD></TR>
+<TR><TD><CODE>allowedUnsafeSysctls</CODE><BR /><I>string array</I></TD><TD>allowedUnsafeSysctls is a list of explicitly allowed unsafe sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of allowed sysctls. Single * means all unsafe sysctls are allowed. Kubelet has to allowlist all allowed unsafe sysctls explicitly to avoid rejection.  Examples: e.g. &#34;foo/*&#34; allows &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; allows &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
+<TR><TD><CODE>defaultAddCapabilities</CODE><BR /><I>string array</I></TD><TD>defaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability.  You may not list a capability in both defaultAddCapabilities and requiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the allowedCapabilities list.</TD></TR>
+<TR><TD><CODE>defaultAllowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>defaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.</TD></TR>
+<TR><TD><CODE>forbiddenSysctls</CODE><BR /><I>string array</I></TD><TD>forbiddenSysctls is a list of explicitly forbidden sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of forbidden sysctls. Single * means all sysctls are forbidden.  Examples: e.g. &#34;foo/*&#34; forbids &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; forbids &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
+<TR><TD><CODE>fsGroup</CODE><BR /><I><a href="#fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions</a></I></TD><TD>fsGroup is the strategy that will dictate what fs group is used by the SecurityContext.</TD></TR>
+<TR><TD><CODE>hostIPC</CODE><BR /><I>boolean</I></TD><TD>hostIPC determines if the policy allows the use of HostIPC in the pod spec.</TD></TR>
+<TR><TD><CODE>hostNetwork</CODE><BR /><I>boolean</I></TD><TD>hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.</TD></TR>
+<TR><TD><CODE>hostPID</CODE><BR /><I>boolean</I></TD><TD>hostPID determines if the policy allows the use of HostPID in the pod spec.</TD></TR>
+<TR><TD><CODE>hostPorts</CODE><BR /><I><a href="#hostportrange-v1beta1-policy">HostPortRange</a> array</I></TD><TD>hostPorts determines which host port ranges are allowed to be exposed.</TD></TR>
+<TR><TD><CODE>privileged</CODE><BR /><I>boolean</I></TD><TD>privileged determines if a pod can request to be run as privileged.</TD></TR>
+<TR><TD><CODE>readOnlyRootFilesystem</CODE><BR /><I>boolean</I></TD><TD>readOnlyRootFilesystem when set to true will force containers to run with a read only root file system.  If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.</TD></TR>
+<TR><TD><CODE>requiredDropCapabilities</CODE><BR /><I>string array</I></TD><TD>requiredDropCapabilities are the capabilities that will be dropped from the container.  These are required to be dropped and cannot be added.</TD></TR>
+<TR><TD><CODE>runAsGroup</CODE><BR /><I><a href="#runasgroupstrategyoptions-v1beta1-policy">RunAsGroupStrategyOptions</a></I></TD><TD>RunAsGroup is the strategy that will dictate the allowable RunAsGroup values that may be set. If this field is omitted, the pod&#39;s RunAsGroup can take any value. This field requires the RunAsGroup feature gate to be enabled.</TD></TR>
+<TR><TD><CODE>runAsUser</CODE><BR /><I><a href="#runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions</a></I></TD><TD>runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
+<TR><TD><CODE>runtimeClass</CODE><BR /><I><a href="#runtimeclassstrategyoptions-v1beta1-policy">RuntimeClassStrategyOptions</a></I></TD><TD>runtimeClass is the strategy that will dictate the allowable RuntimeClasses for a pod. If this field is omitted, the pod&#39;s runtimeClassName field is unrestricted. Enforcement of this field depends on the RuntimeClass feature gate being enabled.</TD></TR>
+<TR><TD><CODE>seLinux</CODE><BR /><I><a href="#selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions</a></I></TD><TD>seLinux is the strategy that will dictate the allowable labels that may be set.</TD></TR>
+<TR><TD><CODE>supplementalGroups</CODE><BR /><I><a href="#supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions</a></I></TD><TD>supplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.</TD></TR>
+<TR><TD><CODE>volumes</CODE><BR /><I>string array</I></TD><TD>volumes is an allowlist of volume plugins. Empty indicates that no volumes may be used. To allow all volumes you may use &#39;\*&#39;.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList v1beta1 policy</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a> array</I></TD><TD>items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-podsecuritypolicy-v1beta1-policy">Create</H2>
+<P>create a PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/policy/v1beta1/podsecuritypolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-podsecuritypolicy-v1beta1-policy">Patch</H2>
+<P>partially update the specified PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-podsecuritypolicy-v1beta1-policy">Replace</H2>
+<P>replace the specified PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-podsecuritypolicy-v1beta1-policy">Delete</H2>
+<P>delete a PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-podsecuritypolicy-v1beta1-policy">Delete Collection</H2>
+<P>delete collection of PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1beta1/podsecuritypolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-podsecuritypolicy-v1beta1-policy">Read</H2>
+<P>read the specified PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-podsecuritypolicy-v1beta1-policy">List</H2>
+<P>list or watch objects of kind PodSecurityPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/podsecuritypolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-podsecuritypolicy-v1beta1-policy">Watch</H2>
+<P>watch changes to an object of kind PodSecurityPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/watch/podsecuritypolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-podsecuritypolicy-v1beta1-policy">Watch List</H2>
+<P>watch individual changes to a list of PodSecurityPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/watch/podsecuritypolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-cluster-apis-strong-"><strong>CLUSTER</strong></H1>
+
+<P>Cluster resources are responsible for defining configuration of the cluster itself, and are generally only used by cluster operators.</P>
+
+<HR />
+<H1 id="apiservice-v1-apiregistration-k8s-io">APIService v1 apiregistration.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIService</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList [apiregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec</a></I></TD><TD>Spec contains information for locating and communicating with a server</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus</a></I></TD><TD>Status contains derived information about an API server</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec v1 apiregistration</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>CABundle is a PEM encoded CA bundle which will be used to validate an API server&#39;s serving certificate. If unspecified, system trust roots on the apiserver are used.</TD></TR>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API group name this server hosts</TD></TR>
+<TR><TD><CODE>groupPriorityMinimum</CODE><BR /><I>integer</I></TD><TD>GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object.  (v1.bar before v1.foo) We&#39;d recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s</TD></TR>
+<TR><TD><CODE>insecureSkipTLSVerify</CODE><BR /><I>boolean</I></TD><TD>InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged.  You should use the CABundle instead.</TD></TR>
+<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-apiregistration-k8s-io">ServiceReference</a></I></TD><TD>Service is a reference to the service for this API server.  It must communicate on port 443. If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.</TD></TR>
+<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API version this server hosts.  For example, &#34;v1&#34;</TD></TR>
+<TR><TD><CODE>versionPriority</CODE><BR /><I>integer</I></TD><TD>VersionPriority controls the ordering of this API version inside of its group.  Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). Since it&#39;s inside of a group, the number can be small, probably in the 10s. In case of equal version priorities, the version string will be used to compute the order inside a group. If the version string is &#34;kube-like&#34;, it will sort above non &#34;kube-like&#34; version strings, which are ordered lexicographically. &#34;Kube-like&#34; versions start with a &#34;v&#34;, then are followed by a number (the major version), then optionally the string &#34;alpha&#34; or &#34;beta&#34; and another number (the minor version). These are sorted first by GA &gt; beta &gt; alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus v1 apiregistration</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state of apiService.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="apiservicelist-v1-apiregistration-k8s-io">APIServiceList v1 apiregistration</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a> array</I></TD><TD>Items is the list of APIService</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-apiservice-v1-apiregistration-k8s-io">Create</H2>
+<P>create an APIService</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/apiregistration.k8s.io/v1/apiservices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-apiservice-v1-apiregistration-k8s-io">Patch</H2>
+<P>partially update the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-apiservice-v1-apiregistration-k8s-io">Replace</H2>
+<P>replace the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-apiservice-v1-apiregistration-k8s-io">Delete</H2>
+<P>delete an APIService</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-apiservice-v1-apiregistration-k8s-io">Delete Collection</H2>
+<P>delete collection of APIService</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-apiservice-v1-apiregistration-k8s-io">Read</H2>
+<P>read the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-apiservice-v1-apiregistration-k8s-io">List</H2>
+<P>list or watch objects of kind APIService</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-apiservice-v1-apiregistration-k8s-io">Watch</H2>
+<P>watch changes to an object of kind APIService. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-apiservice-v1-apiregistration-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of APIService. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-apiservice-v1-apiregistration-k8s-io">Patch Status</H2>
+<P>partially update status of the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-apiservice-v1-apiregistration-k8s-io">Read Status</H2>
+<P>read status of the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-apiservice-v1-apiregistration-k8s-io">Replace Status</H2>
+<P>replace status of the specified APIService</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="binding-v1-core">Binding v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Binding</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>The target object that you want to bind to the standard object.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-binding-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-binding-v1-core">Create</H2>
+<P>create a Binding</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/bindings</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest v1 certificates.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CertificateSigningRequest</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#certificatesigningrequestspec-v1-certificates-k8s-io">CertificateSigningRequestSpec</a></I></TD><TD>spec contains the certificate request, and is immutable after creation. Only the request, signerName, expirationSeconds, and usages fields can be set on creation. Other fields are derived by Kubernetes and cannot be modified by users.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus</a></I></TD><TD>status contains information about whether the request is approved or denied, and the certificate issued by the signer, or the failure condition indicating signer failure.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="certificatesigningrequestspec-v1-certificates-k8s-io">CertificateSigningRequestSpec v1 certificates</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.  The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.  Certificate signers may not honor this field for various reasons:    1. Old signer that is unaware of the field (such as the in-tree      implementations prior to v1.22)   2. Signer whose configured maximum is shorter than the requested duration   3. Signer whose configured minimum is longer than the requested duration  The minimum valid value for expirationSeconds is 600, i.e. 10 minutes.  As of v1.22, this field is beta and is controlled via the CSRDuration feature gate.</TD></TR>
+<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
+<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>groups contains group membership of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
+<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>request contains an x509 certificate signing request encoded in a &#34;CERTIFICATE REQUEST&#34; PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.</TD></TR>
+<TR><TD><CODE>signerName</CODE><BR /><I>string</I></TD><TD>signerName indicates the requested signer, and is a qualified name.  List/watch requests for CertificateSigningRequests can filter on this field using a &#34;spec.signerName=NAME&#34; fieldSelector.  Well-known Kubernetes signers are:  1. &#34;kubernetes.io/kube-apiserver-client&#34;: issues client certificates that can be used to authenticate to kube-apiserver.   Requests for this signer are never auto-approved by kube-controller-manager, can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager.  2. &#34;kubernetes.io/kube-apiserver-client-kubelet&#34;: issues client certificates that kubelets use to authenticate to kube-apiserver.   Requests for this signer can be auto-approved by the &#34;csrapproving&#34; controller in kube-controller-manager, and can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager.  3. &#34;kubernetes.io/kubelet-serving&#34; issues serving certificates that kubelets use to serve TLS endpoints, which kube-apiserver can connect to securely.   Requests for this signer are never auto-approved by kube-controller-manager, and can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager.  More details are available at https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers  Custom signerNames can also be specified. The signer defines:  1. Trust distribution: how trust (CA bundles) are distributed.  2. Permitted subjects: and behavior when a disallowed subject is requested.  3. Required, permitted, or forbidden x509 extensions in the request (including whether subjectAltNames are allowed, which types, restrictions on allowed values) and behavior when a disallowed extension is requested.  4. Required, permitted, or forbidden key usages / extended key usages.  5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin.  6. Whether or not requests for CA certificates are allowed.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>uid contains the uid of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
+<TR><TD><CODE>usages</CODE><BR /><I>string array</I></TD><TD>usages specifies a set of key usages requested in the issued certificate.  Requests for TLS client certificates typically request: &#34;digital signature&#34;, &#34;key encipherment&#34;, &#34;client auth&#34;.  Requests for TLS serving certificates typically request: &#34;key encipherment&#34;, &#34;digital signature&#34;, &#34;server auth&#34;.  Valid values are:  &#34;signing&#34;, &#34;digital signature&#34;, &#34;content commitment&#34;,  &#34;key encipherment&#34;, &#34;key agreement&#34;, &#34;data encipherment&#34;,  &#34;cert sign&#34;, &#34;crl sign&#34;, &#34;encipher only&#34;, &#34;decipher only&#34;, &#34;any&#34;,  &#34;server auth&#34;, &#34;client auth&#34;,  &#34;code signing&#34;, &#34;email protection&#34;, &#34;s/mime&#34;,  &#34;ipsec end system&#34;, &#34;ipsec tunnel&#34;, &#34;ipsec user&#34;,  &#34;timestamping&#34;, &#34;ocsp signing&#34;, &#34;microsoft sgc&#34;, &#34;netscape sgc&#34;</TD></TR>
+<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>username contains the name of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus v1 certificates</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>certificate</CODE><BR /><I>string</I></TD><TD>certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable.  If the certificate signing request is denied, a condition of type &#34;Denied&#34; is added and this field remains empty. If the signer cannot issue the certificate, a condition of type &#34;Failed&#34; is added and this field remains empty.  Validation requirements:  1. certificate must contain one or more PEM blocks.  2. All PEM blocks must have the &#34;CERTIFICATE&#34; label, contain no headers, and the encoded data   must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280.  3. Non-PEM content may appear before or after the &#34;CERTIFICATE&#34; PEM blocks and is unvalidated,   to allow for explanatory text as described in section 5.2 of RFC7468.  If more than one PEM block is present, and the definition of the requested spec.signerName does not indicate otherwise, the first block is the issued certificate, and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.  The certificate is encoded in PEM format.  When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:      base64(     -----BEGIN CERTIFICATE-----     ...     -----END CERTIFICATE-----     )</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#certificatesigningrequestcondition-v1-certificates-k8s-io">CertificateSigningRequestCondition</a> array</I></TD><TD>conditions applied to the request. Known conditions are &#34;Approved&#34;, &#34;Denied&#34;, and &#34;Failed&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList v1 certificates</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a> array</I></TD><TD>items is a collection of CertificateSigningRequest objects</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-certificatesigningrequest-v1-certificates-k8s-io">Create</H2>
+<P>create a CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-certificatesigningrequest-v1-certificates-k8s-io">Patch</H2>
+<P>partially update the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-certificatesigningrequest-v1-certificates-k8s-io">Replace</H2>
+<P>replace the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-certificatesigningrequest-v1-certificates-k8s-io">Delete</H2>
+<P>delete a CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-certificatesigningrequest-v1-certificates-k8s-io">Delete Collection</H2>
+<P>delete collection of CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-certificatesigningrequest-v1-certificates-k8s-io">Read</H2>
+<P>read the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-certificatesigningrequest-v1-certificates-k8s-io">List</H2>
+<P>list or watch objects of kind CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-certificatesigningrequest-v1-certificates-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-certificatesigningrequest-v1-certificates-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1/watch/certificatesigningrequests</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-certificatesigningrequest-v1-certificates-k8s-io">Patch Status</H2>
+<P>partially update status of the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-certificatesigningrequest-v1-certificates-k8s-io">Read Status</H2>
+<P>read status of the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-certificatesigningrequest-v1-certificates-k8s-io">Replace Status</H2>
+<P>replace status of the specified CertificateSigningRequest</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="clusterrole-v1-rbac-authorization-k8s-io">ClusterRole v1 rbac.authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClusterRole</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>aggregationRule</CODE><BR /><I><a href="#aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule</a></I></TD><TD>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList v1 rbac</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a> array</I></TD><TD>Items is a list of ClusterRoles</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-clusterrole-v1-rbac-authorization-k8s-io">Create</H2>
+<P>create a ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-clusterrole-v1-rbac-authorization-k8s-io">Patch</H2>
+<P>partially update the specified ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-clusterrole-v1-rbac-authorization-k8s-io">Replace</H2>
+<P>replace the specified ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-clusterrole-v1-rbac-authorization-k8s-io">Delete</H2>
+<P>delete a ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-clusterrole-v1-rbac-authorization-k8s-io">Delete Collection</H2>
+<P>delete collection of ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-clusterrole-v1-rbac-authorization-k8s-io">Read</H2>
+<P>read the specified ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-clusterrole-v1-rbac-authorization-k8s-io">List</H2>
+<P>list or watch objects of kind ClusterRole</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-clusterrole-v1-rbac-authorization-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ClusterRole. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-clusterrole-v1-rbac-authorization-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ClusterRole. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding v1 rbac.authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClusterRoleBinding</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
+<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList v1 rbac</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a> array</I></TD><TD>Items is a list of ClusterRoleBindings</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-clusterrolebinding-v1-rbac-authorization-k8s-io">Create</H2>
+<P>create a ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-clusterrolebinding-v1-rbac-authorization-k8s-io">Patch</H2>
+<P>partially update the specified ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-clusterrolebinding-v1-rbac-authorization-k8s-io">Replace</H2>
+<P>replace the specified ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-clusterrolebinding-v1-rbac-authorization-k8s-io">Delete</H2>
+<P>delete a ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io">Delete Collection</H2>
+<P>delete collection of ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-clusterrolebinding-v1-rbac-authorization-k8s-io">Read</H2>
+<P>read the specified ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-clusterrolebinding-v1-rbac-authorization-k8s-io">List</H2>
+<P>list or watch objects of kind ClusterRoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-clusterrolebinding-v1-rbac-authorization-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="componentstatus-v1-core">ComponentStatus v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ComponentStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#componentstatuslist-v1-core">ComponentStatusList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#componentcondition-v1-core">ComponentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>List of component conditions observed</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="componentstatuslist-v1-core">ComponentStatusList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#componentstatus-v1-core">ComponentStatus</a> array</I></TD><TD>List of ComponentStatus objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-componentstatus-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-componentstatus-v1-core">Read</H2>
+<P>read the specified ComponentStatus</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/componentstatuses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ComponentStatus</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#componentstatus-v1-core">ComponentStatus</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-componentstatus-v1-core">List</H2>
+<P>list objects of kind ComponentStatus</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/componentstatuses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#componentstatuslist-v1-core">ComponentStatusList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FlowSchema</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#flowschemastatus-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus</a></I></TD><TD>`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>distinguisherMethod</CODE><BR /><I><a href="#flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod</a></I></TD><TD>`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.</TD></TR>
+<TR><TD><CODE>matchingPrecedence</CODE><BR /><I>integer</I></TD><TD>`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence.  Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.</TD></TR>
+<TR><TD><CODE>priorityLevelConfiguration</CODE><BR /><I><a href="#prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference</a></I></TD><TD>`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects</a> array</I></TD><TD>`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemastatus-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition</a> array</I></TD><TD>`conditions` is a list of the current states of FlowSchema.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList v1beta1 flowcontrol</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a> array</I></TD><TD>`items` is a list of FlowSchemas.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>`metadata` is the standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">List</H2>
+<P>list or watch objects of kind FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Watch</H2>
+<P>watch changes to an object of kind FlowSchema. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of FlowSchema. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Patch Status</H2>
+<P>partially update status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Read Status</H2>
+<P>read status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Replace Status</H2>
+<P>replace status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="lease-v1-coordination-k8s-io">Lease v1 coordination.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Lease</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#leaselist-v1-coordination-k8s-io">LeaseList [coordination/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#leasespec-v1-coordination-k8s-io">LeaseSpec</a></I></TD><TD>Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="leasespec-v1-coordination-k8s-io">LeaseSpec v1 coordination</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#lease-v1-coordination-k8s-io">Lease [coordination/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>acquireTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>acquireTime is a time when the current lease was acquired.</TD></TR>
+<TR><TD><CODE>holderIdentity</CODE><BR /><I>string</I></TD><TD>holderIdentity contains the identity of the holder of a current lease.</TD></TR>
+<TR><TD><CODE>leaseDurationSeconds</CODE><BR /><I>integer</I></TD><TD>leaseDurationSeconds is a duration that candidates for a lease need to wait to force acquire it. This is measure against time of last observed RenewTime.</TD></TR>
+<TR><TD><CODE>leaseTransitions</CODE><BR /><I>integer</I></TD><TD>leaseTransitions is the number of transitions of a lease between holders.</TD></TR>
+<TR><TD><CODE>renewTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>renewTime is a time when the current holder of a lease has last updated the lease.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="leaselist-v1-coordination-k8s-io">LeaseList v1 coordination</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#lease-v1-coordination-k8s-io">Lease</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-lease-v1-coordination-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-lease-v1-coordination-k8s-io">Create</H2>
+<P>create a Lease</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-lease-v1-coordination-k8s-io">Patch</H2>
+<P>partially update the specified Lease</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-lease-v1-coordination-k8s-io">Replace</H2>
+<P>replace the specified Lease</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-lease-v1-coordination-k8s-io">Delete</H2>
+<P>delete a Lease</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-lease-v1-coordination-k8s-io">Delete Collection</H2>
+<P>delete collection of Lease</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-lease-v1-coordination-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-lease-v1-coordination-k8s-io">Read</H2>
+<P>read the specified Lease</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-lease-v1-coordination-k8s-io">List</H2>
+<P>list or watch objects of kind Lease</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#leaselist-v1-coordination-k8s-io">LeaseList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-lease-v1-coordination-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind Lease</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/leases</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#leaselist-v1-coordination-k8s-io">LeaseList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-lease-v1-coordination-k8s-io">Watch</H2>
+<P>watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/watch/namespaces/{namespace}/leases/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-lease-v1-coordination-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of Lease. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/watch/namespaces/{namespace}/leases</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-lease-v1-coordination-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Lease. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/coordination.k8s.io/v1/watch/leases</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview v1 authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalSubjectAccessReview</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated.  spec.namespace must be equal to the namespace you made the request against.  If empty, it is defaulted.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-localsubjectaccessreview-v1-authorization-k8s-io">Create</H2>
+<P>create a LocalSubjectAccessReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authorization.k8s.io/v1/namespaces/{namespace}/localsubjectaccessreviews</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="namespace-v1-core">Namespace v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Namespace</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#namespacelist-v1-core">NamespaceList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#namespacespec-v1-core">NamespaceSpec</a></I></TD><TD>Spec defines the behavior of the Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#namespacestatus-v1-core">NamespaceStatus</a></I></TD><TD>Status describes the current status of a Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="namespacespec-v1-core">NamespaceSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>finalizers</CODE><BR /><I>string array</I></TD><TD>Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="namespacestatus-v1-core">NamespaceStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#namespacecondition-v1-core">NamespaceCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a namespace&#39;s current state.</TD></TR>
+<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/  Possible enum values:  - `&#34;Active&#34;` means the namespace is available for use in the system  - `&#34;Terminating&#34;` means the namespace is undergoing graceful termination</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="namespacelist-v1-core">NamespaceList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#namespace-v1-core">Namespace</a> array</I></TD><TD>Items is the list of Namespace objects in the list. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-namespace-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-namespace-v1-core">Create</H2>
+<P>create a Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-namespace-v1-core">Patch</H2>
+<P>partially update the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-namespace-v1-core">Replace</H2>
+<P>replace the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-namespace-v1-core">Delete</H2>
+<P>delete a Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-namespace-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-namespace-v1-core">Read</H2>
+<P>read the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-namespace-v1-core">List</H2>
+<P>list or watch objects of kind Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespacelist-v1-core">NamespaceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-namespace-v1-core">Watch</H2>
+<P>watch changes to an object of kind Namespace. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-namespace-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Namespace. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-namespace-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-namespace-v1-core">Patch Status</H2>
+<P>partially update status of the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-namespace-v1-core">Read Status</H2>
+<P>read status of the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-namespace-v1-core">Replace Status</H2>
+<P>replace status of the specified Namespace</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="node-v1-core">Node v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Node</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodelist-v1-core">NodeList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#nodespec-v1-core">NodeSpec</a></I></TD><TD>Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#nodestatus-v1-core">NodeStatus</a></I></TD><TD>Most recently observed status of the node. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="nodespec-v1-core">NodeSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#node-v1-core">Node [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>configSource</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>Deprecated. If specified, the source of the node&#39;s configuration. The DynamicKubeletConfig feature gate must be enabled for the Kubelet to use this field. This field is deprecated as of 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration</TD></TR>
+<TR><TD><CODE>externalID</CODE><BR /><I>string</I></TD><TD>Deprecated. Not all kubelets will set this field. Remove field after 1.13. see: https://issues.k8s.io/61966</TD></TR>
+<TR><TD><CODE>podCIDR</CODE><BR /><I>string</I></TD><TD>PodCIDR represents the pod IP range assigned to the node.</TD></TR>
+<TR><TD><CODE>podCIDRs</CODE><BR /><I>string array</I><BR /><B>patch strategy</B>: <I>merge</I></TD><TD>podCIDRs represents the IP ranges assigned to the node for usage by Pods on that node. If this field is specified, the 0th entry must match the podCIDR field. It may contain at most 1 value for each of IPv4 and IPv6.</TD></TR>
+<TR><TD><CODE>providerID</CODE><BR /><I>string</I></TD><TD>ID of the node assigned by the cloud provider in the format: &lt;ProviderName&gt;://&lt;ProviderSpecificNodeID&gt;</TD></TR>
+<TR><TD><CODE>taints</CODE><BR /><I><a href="#taint-v1-core">Taint</a> array</I></TD><TD>If specified, the node&#39;s taints.</TD></TR>
+<TR><TD><CODE>unschedulable</CODE><BR /><I>boolean</I></TD><TD>Unschedulable controls node schedulability of new pods. By default, node is schedulable. More info: https://kubernetes.io/docs/concepts/nodes/node/#manual-node-administration</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="nodestatus-v1-core">NodeStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#node-v1-core">Node [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addresses</CODE><BR /><I><a href="#nodeaddress-v1-core">NodeAddress</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>List of addresses reachable to the node. Queried from cloud provider, if available. More info: https://kubernetes.io/docs/concepts/nodes/node/#addresses Note: This field is declared as mergeable, but the merge key is not sufficiently unique, which can cause data corruption when it is merged. Callers should instead use a full-replacement patch. See http://pr.k8s.io/79391 for an example.</TD></TR>
+<TR><TD><CODE>allocatable</CODE><BR /><I>object</I></TD><TD>Allocatable represents the resources of a node that are available for scheduling. Defaults to Capacity.</TD></TR>
+<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Capacity represents the total resources of a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#nodecondition-v1-core">NodeCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Conditions is an array of current observed node conditions. More info: https://kubernetes.io/docs/concepts/nodes/node/#condition</TD></TR>
+<TR><TD><CODE>config</CODE><BR /><I><a href="#nodeconfigstatus-v1-core">NodeConfigStatus</a></I></TD><TD>Status of the config assigned to the node via the dynamic Kubelet config feature.</TD></TR>
+<TR><TD><CODE>daemonEndpoints</CODE><BR /><I><a href="#nodedaemonendpoints-v1-core">NodeDaemonEndpoints</a></I></TD><TD>Endpoints of daemons running on the Node.</TD></TR>
+<TR><TD><CODE>images</CODE><BR /><I><a href="#containerimage-v1-core">ContainerImage</a> array</I></TD><TD>List of container images on this node</TD></TR>
+<TR><TD><CODE>nodeInfo</CODE><BR /><I><a href="#nodesysteminfo-v1-core">NodeSystemInfo</a></I></TD><TD>Set of ids/uuids to uniquely identify the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#info</TD></TR>
+<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>NodePhase is the recently observed lifecycle phase of the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#phase The field is never populated, and now is deprecated.  Possible enum values:  - `&#34;Pending&#34;` means the node has been created/added by the system, but not configured.  - `&#34;Running&#34;` means the node has been configured and has Kubernetes components running.  - `&#34;Terminated&#34;` means the node has been removed from the cluster.</TD></TR>
+<TR><TD><CODE>volumesAttached</CODE><BR /><I><a href="#attachedvolume-v1-core">AttachedVolume</a> array</I></TD><TD>List of volumes that are attached to the node.</TD></TR>
+<TR><TD><CODE>volumesInUse</CODE><BR /><I>string array</I></TD><TD>List of attachable volumes in use (mounted) by the node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="nodelist-v1-core">NodeList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#node-v1-core">Node</a> array</I></TD><TD>List of nodes</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-node-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-node-v1-core">Create</H2>
+<P>create a Node</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/nodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-node-v1-core">Patch</H2>
+<P>partially update the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/nodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-node-v1-core">Replace</H2>
+<P>replace the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/nodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-node-v1-core">Delete</H2>
+<P>delete a Node</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/nodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-node-v1-core">Delete Collection</H2>
+<P>delete collection of Node</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/nodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-node-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-node-v1-core">Read</H2>
+<P>read the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/nodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-node-v1-core">List</H2>
+<P>list or watch objects of kind Node</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/nodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#nodelist-v1-core">NodeList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-node-v1-core">Watch</H2>
+<P>watch changes to an object of kind Node. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/nodes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-node-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Node. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/nodes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-node-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-node-v1-core">Patch Status</H2>
+<P>partially update status of the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/nodes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-node-v1-core">Read Status</H2>
+<P>read status of the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/nodes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-node-v1-core">Replace Status</H2>
+<P>replace status of the specified Node</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/nodes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-proxy-operations-node-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
+<H2 id="create-connect-proxy-node-v1-core">Create Connect Proxy</H2>
+<P>connect POST requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/nodes/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="create-connect-proxy-path-node-v1-core">Create Connect Proxy Path</H2>
+<P>connect POST requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/nodes/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-node-v1-core">Delete Connect Proxy</H2>
+<P>connect DELETE requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/nodes/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-connect-proxy-path-node-v1-core">Delete Connect Proxy Path</H2>
+<P>connect DELETE requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/nodes/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-node-v1-core">Get Connect Proxy</H2>
+<P>connect GET requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/nodes/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="get-connect-proxy-path-node-v1-core">Get Connect Proxy Path</H2>
+<P>connect GET requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/nodes/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-node-v1-core">Head Connect Proxy</H2>
+<P>connect HEAD requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/nodes/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="head-connect-proxy-path-node-v1-core">Head Connect Proxy Path</H2>
+<P>connect HEAD requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>HEAD /api/v1/nodes/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-node-v1-core">Replace Connect Proxy</H2>
+<P>connect PUT requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/nodes/{name}/proxy</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-connect-proxy-path-node-v1-core">Replace Connect Proxy Path</H2>
+<P>connect PUT requests to proxy of Node</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/nodes/{name}/proxy/{path}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</TD></TR>
+<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="persistentvolume-v1-core">PersistentVolume v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolume</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-bullhorn"></I> These are assigned to <a href="#pod-v1-core">Pods</a> using <a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaims</a>.</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumelist-v1-core">PersistentVolumeList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec</a></I></TD><TD>Spec defines a specification of a persistent volume owned by the cluster. Provisioned by an administrator. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#persistentvolumestatus-v1-core">PersistentVolumeStatus</a></I></TD><TD>Status represents the current information/status for the persistent volume. Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumespec-v1-core">PersistentVolumeSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
+  <LI><a href="#volumeattachmentsource-v1-storage-k8s-io">VolumeAttachmentSource [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains all ways the volume can be mounted. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes</TD></TR>
+<TR><TD><CODE>awsElasticBlockStore</CODE><BR /><I><a href="#awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource</a></I></TD><TD>AWSElasticBlockStore represents an AWS Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+<TR><TD><CODE>azureDisk</CODE><BR /><I><a href="#azurediskvolumesource-v1-core">AzureDiskVolumeSource</a></I></TD><TD>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</TD></TR>
+<TR><TD><CODE>azureFile</CODE><BR /><I><a href="#azurefilepersistentvolumesource-v1-core">AzureFilePersistentVolumeSource</a></I></TD><TD>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</TD></TR>
+<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>A description of the persistent volume&#39;s resources and capacity. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity</TD></TR>
+<TR><TD><CODE>cephfs</CODE><BR /><I><a href="#cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource</a></I></TD><TD>CephFS represents a Ceph FS mount on the host that shares a pod&#39;s lifetime</TD></TR>
+<TR><TD><CODE>cinder</CODE><BR /><I><a href="#cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource</a></I></TD><TD>Cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>claimRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>ClaimRef is part of a bi-directional binding between PersistentVolume and PersistentVolumeClaim. Expected to be non-nil when bound. claim.VolumeName is the authoritative bind between PV and PVC. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#binding</TD></TR>
+<TR><TD><CODE>csi</CODE><BR /><I><a href="#csipersistentvolumesource-v1-core">CSIPersistentVolumeSource</a></I></TD><TD>CSI represents storage that is handled by an external CSI driver (Beta feature).</TD></TR>
+<TR><TD><CODE>fc</CODE><BR /><I><a href="#fcvolumesource-v1-core">FCVolumeSource</a></I></TD><TD>FC represents a Fibre Channel resource that is attached to a kubelet&#39;s host machine and then exposed to the pod.</TD></TR>
+<TR><TD><CODE>flexVolume</CODE><BR /><I><a href="#flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource</a></I></TD><TD>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</TD></TR>
+<TR><TD><CODE>flocker</CODE><BR /><I><a href="#flockervolumesource-v1-core">FlockerVolumeSource</a></I></TD><TD>Flocker represents a Flocker volume attached to a kubelet&#39;s host machine and exposed to the pod for its usage. This depends on the Flocker control service being running</TD></TR>
+<TR><TD><CODE>gcePersistentDisk</CODE><BR /><I><a href="#gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource</a></I></TD><TD>GCEPersistentDisk represents a GCE Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+<TR><TD><CODE>glusterfs</CODE><BR /><I><a href="#glusterfspersistentvolumesource-v1-core">GlusterfsPersistentVolumeSource</a></I></TD><TD>Glusterfs represents a Glusterfs volume that is attached to a host and exposed to the pod. Provisioned by an admin. More info: https://examples.k8s.io/volumes/glusterfs/README.md</TD></TR>
+<TR><TD><CODE>hostPath</CODE><BR /><I><a href="#hostpathvolumesource-v1-core">HostPathVolumeSource</a></I></TD><TD>HostPath represents a directory on the host. Provisioned by a developer or tester. This is useful for single-node development and testing only! On-host storage is not supported in any way and WILL NOT WORK in a multi-node cluster. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
+<TR><TD><CODE>iscsi</CODE><BR /><I><a href="#iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource</a></I></TD><TD>ISCSI represents an ISCSI Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. Provisioned by an admin.</TD></TR>
+<TR><TD><CODE>local</CODE><BR /><I><a href="#localvolumesource-v1-core">LocalVolumeSource</a></I></TD><TD>Local represents directly-attached storage with node affinity</TD></TR>
+<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>A list of mount options, e.g. [&#34;ro&#34;, &#34;soft&#34;]. Not validated - mount will simply fail if one is invalid. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#mount-options</TD></TR>
+<TR><TD><CODE>nfs</CODE><BR /><I><a href="#nfsvolumesource-v1-core">NFSVolumeSource</a></I></TD><TD>NFS represents an NFS mount on the host. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
+<TR><TD><CODE>nodeAffinity</CODE><BR /><I><a href="#volumenodeaffinity-v1-core">VolumeNodeAffinity</a></I></TD><TD>NodeAffinity defines constraints that limit what nodes this volume can be accessed from. This field influences the scheduling of pods that use this volume.</TD></TR>
+<TR><TD><CODE>persistentVolumeReclaimPolicy</CODE><BR /><I>string</I></TD><TD>What happens to a persistent volume when released from its claim. Valid options are Retain (default for manually created PersistentVolumes), Delete (default for dynamically provisioned PersistentVolumes), and Recycle (deprecated). Recycle must be supported by the volume plugin underlying this PersistentVolume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#reclaiming  Possible enum values:  - `&#34;Delete&#34;` means the volume will be deleted from Kubernetes on release from its claim. The volume plugin must support Deletion.  - `&#34;Recycle&#34;` means the volume will be recycled back into the pool of unbound persistent volumes on release from its claim. The volume plugin must support Recycling.  - `&#34;Retain&#34;` means the volume will be left in its current phase (Released) for manual reclamation by the administrator. The default policy is Retain.</TD></TR>
+<TR><TD><CODE>photonPersistentDisk</CODE><BR /><I><a href="#photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource</a></I></TD><TD>PhotonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine</TD></TR>
+<TR><TD><CODE>portworxVolume</CODE><BR /><I><a href="#portworxvolumesource-v1-core">PortworxVolumeSource</a></I></TD><TD>PortworxVolume represents a portworx volume attached and mounted on kubelets host machine</TD></TR>
+<TR><TD><CODE>quobyte</CODE><BR /><I><a href="#quobytevolumesource-v1-core">QuobyteVolumeSource</a></I></TD><TD>Quobyte represents a Quobyte mount on the host that shares a pod&#39;s lifetime</TD></TR>
+<TR><TD><CODE>rbd</CODE><BR /><I><a href="#rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource</a></I></TD><TD>RBD represents a Rados Block Device mount on the host that shares a pod&#39;s lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md</TD></TR>
+<TR><TD><CODE>scaleIO</CODE><BR /><I><a href="#scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource</a></I></TD><TD>ScaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.</TD></TR>
+<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>Name of StorageClass to which this persistent volume belongs. Empty value means that this volume does not belong to any StorageClass.</TD></TR>
+<TR><TD><CODE>storageos</CODE><BR /><I><a href="#storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource</a></I></TD><TD>StorageOS represents a StorageOS volume that is attached to the kubelet&#39;s host machine and mounted into the pod More info: https://examples.k8s.io/volumes/storageos/README.md</TD></TR>
+<TR><TD><CODE>volumeMode</CODE><BR /><I>string</I></TD><TD>volumeMode defines if a volume is intended to be used with a formatted filesystem or to remain in raw block state. Value of Filesystem is implied when not included in spec.</TD></TR>
+<TR><TD><CODE>vsphereVolume</CODE><BR /><I><a href="#vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource</a></I></TD><TD>VsphereVolume represents a vSphere volume attached and mounted on kubelets host machine</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumestatus-v1-core">PersistentVolumeStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable message indicating details about why the volume is in this state.</TD></TR>
+<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase indicates if a volume is available, bound to a claim, or released by a claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#phase  Possible enum values:  - `&#34;Available&#34;` used for PersistentVolumes that are not yet bound Available volumes are held by the binder and matched to PersistentVolumeClaims  - `&#34;Bound&#34;` used for PersistentVolumes that are bound  - `&#34;Failed&#34;` used for PersistentVolumes that failed to be correctly recycled or deleted after being released from a claim  - `&#34;Pending&#34;` used for PersistentVolumes that are not available  - `&#34;Released&#34;` used for PersistentVolumes where the bound PersistentVolumeClaim was deleted released volumes must be recycled before becoming available again this phase is used by the persistent volume claim binder to signal to another process to reclaim the resource</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason is a brief CamelCase string that describes any failure and is meant for machine parsing and tidy display in the CLI.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="persistentvolumelist-v1-core">PersistentVolumeList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolume-v1-core">PersistentVolume</a> array</I></TD><TD>List of persistent volumes. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-persistentvolume-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-persistentvolume-v1-core">Create</H2>
+<P>create a PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/persistentvolumes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-persistentvolume-v1-core">Patch</H2>
+<P>partially update the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/persistentvolumes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-persistentvolume-v1-core">Replace</H2>
+<P>replace the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/persistentvolumes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-persistentvolume-v1-core">Delete</H2>
+<P>delete a PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/persistentvolumes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-persistentvolume-v1-core">Delete Collection</H2>
+<P>delete collection of PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/persistentvolumes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-persistentvolume-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-persistentvolume-v1-core">Read</H2>
+<P>read the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/persistentvolumes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-persistentvolume-v1-core">List</H2>
+<P>list or watch objects of kind PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/persistentvolumes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolumelist-v1-core">PersistentVolumeList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-persistentvolume-v1-core">Watch</H2>
+<P>watch changes to an object of kind PersistentVolume. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/persistentvolumes/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-persistentvolume-v1-core">Watch List</H2>
+<P>watch individual changes to a list of PersistentVolume. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/persistentvolumes</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-persistentvolume-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-persistentvolume-v1-core">Patch Status</H2>
+<P>partially update status of the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/persistentvolumes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-persistentvolume-v1-core">Read Status</H2>
+<P>read status of the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/persistentvolumes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-persistentvolume-v1-core">Replace Status</H2>
+<P>replace status of the specified PersistentVolume</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/persistentvolumes/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PriorityLevelConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#prioritylevelconfigurationspec-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#prioritylevelconfigurationstatus-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus</a></I></TD><TD>`status` is the current status of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationspec-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>limited</CODE><BR /><I><a href="#limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration</a></I></TD><TD>`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `&#34;Limited&#34;`.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` indicates whether this priority level is subject to limitation on request execution.  A value of `&#34;Exempt&#34;` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels.  A value of `&#34;Limited&#34;` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server&#39;s limited capacity is made available exclusively to this priority level. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationstatus-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition</a> array</I></TD><TD>`conditions` is the current state of &#34;request-priority&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList v1beta1 flowcontrol</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a> array</I></TD><TD>`items` is a list of request-priorities.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">List</H2>
+<P>list or watch objects of kind PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Watch</H2>
+<P>watch changes to an object of kind PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Patch Status</H2>
+<P>partially update status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Read Status</H2>
+<P>read status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Replace Status</H2>
+<P>replace status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcequota-v1-core">ResourceQuota v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceQuota</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourcequotalist-v1-core">ResourceQuotaList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourcequotaspec-v1-core">ResourceQuotaSpec</a></I></TD><TD>Spec defines the desired quota. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#resourcequotastatus-v1-core">ResourceQuotaStatus</a></I></TD><TD>Status defines the actual enforced quota and its current usage. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourcequotaspec-v1-core">ResourceQuotaSpec v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hard</CODE><BR /><I>object</I></TD><TD>hard is the set of desired hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
+<TR><TD><CODE>scopeSelector</CODE><BR /><I><a href="#scopeselector-v1-core">ScopeSelector</a></I></TD><TD>scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.</TD></TR>
+<TR><TD><CODE>scopes</CODE><BR /><I>string array</I></TD><TD>A collection of filters that must match each object tracked by a quota. If not specified, the quota matches all objects.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourcequotastatus-v1-core">ResourceQuotaStatus v1 core</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hard</CODE><BR /><I>object</I></TD><TD>Hard is the set of enforced hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
+<TR><TD><CODE>used</CODE><BR /><I>object</I></TD><TD>Used is the current observed total usage of the resource in the namespace.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourcequotalist-v1-core">ResourceQuotaList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#resourcequota-v1-core">ResourceQuota</a> array</I></TD><TD>Items is a list of ResourceQuota objects. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-resourcequota-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-resourcequota-v1-core">Create</H2>
+<P>create a ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/resourcequotas</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-resourcequota-v1-core">Patch</H2>
+<P>partially update the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-resourcequota-v1-core">Replace</H2>
+<P>replace the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-resourcequota-v1-core">Delete</H2>
+<P>delete a ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-resourcequota-v1-core">Delete Collection</H2>
+<P>delete collection of ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-resourcequota-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-resourcequota-v1-core">Read</H2>
+<P>read the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-resourcequota-v1-core">List</H2>
+<P>list or watch objects of kind ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequotalist-v1-core">ResourceQuotaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-resourcequota-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/resourcequotas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequotalist-v1-core">ResourceQuotaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-resourcequota-v1-core">Watch</H2>
+<P>watch changes to an object of kind ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-resourcequota-v1-core">Watch List</H2>
+<P>watch individual changes to a list of ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-resourcequota-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/resourcequotas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-resourcequota-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-resourcequota-v1-core">Patch Status</H2>
+<P>partially update status of the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-resourcequota-v1-core">Read Status</H2>
+<P>read status of the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-resourcequota-v1-core">Replace Status</H2>
+<P>replace status of the specified ResourceQuota</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="role-v1-rbac-authorization-k8s-io">Role v1 rbac.authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Role</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this Role</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="rolelist-v1-rbac-authorization-k8s-io">RoleList v1 rbac</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a> array</I></TD><TD>Items is a list of Roles</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-role-v1-rbac-authorization-k8s-io">Create</H2>
+<P>create a Role</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-role-v1-rbac-authorization-k8s-io">Patch</H2>
+<P>partially update the specified Role</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-role-v1-rbac-authorization-k8s-io">Replace</H2>
+<P>replace the specified Role</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-role-v1-rbac-authorization-k8s-io">Delete</H2>
+<P>delete a Role</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-role-v1-rbac-authorization-k8s-io">Delete Collection</H2>
+<P>delete collection of Role</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-role-v1-rbac-authorization-k8s-io">Read</H2>
+<P>read the specified Role</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-role-v1-rbac-authorization-k8s-io">List</H2>
+<P>list or watch objects of kind Role</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-role-v1-rbac-authorization-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind Role</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/roles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-role-v1-rbac-authorization-k8s-io">Watch</H2>
+<P>watch changes to an object of kind Role. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-role-v1-rbac-authorization-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/roles</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="rolebinding-v1-rbac-authorization-k8s-io">RoleBinding v1 rbac.authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RoleBinding</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
+<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList v1 rbac</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a> array</I></TD><TD>Items is a list of RoleBindings</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-rolebinding-v1-rbac-authorization-k8s-io">Create</H2>
+<P>create a RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-rolebinding-v1-rbac-authorization-k8s-io">Patch</H2>
+<P>partially update the specified RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-rolebinding-v1-rbac-authorization-k8s-io">Replace</H2>
+<P>replace the specified RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-rolebinding-v1-rbac-authorization-k8s-io">Delete</H2>
+<P>delete a RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-rolebinding-v1-rbac-authorization-k8s-io">Delete Collection</H2>
+<P>delete collection of RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-rolebinding-v1-rbac-authorization-k8s-io">Read</H2>
+<P>read the specified RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-rolebinding-v1-rbac-authorization-k8s-io">List</H2>
+<P>list or watch objects of kind RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind RoleBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/rolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-rolebinding-v1-rbac-authorization-k8s-io">Watch</H2>
+<P>watch changes to an object of kind RoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-rolebinding-v1-rbac-authorization-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/rolebindings</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="runtimeclass-v1-node-k8s-io">RuntimeClass v1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RuntimeClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#runtimeclass-v1beta1-node-k8s-io">v1beta1</a>
+<a href="#runtimeclass-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList [node/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node &amp; CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called &#34;runc&#34; might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see  https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/ This field is in beta starting v1.18 and is only honored by servers that enable the PodOverhead feature.</TD></TR>
+<TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="runtimeclasslist-v1-node-k8s-io">RuntimeClassList v1 node</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-runtimeclass-v1-node-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-runtimeclass-v1-node-k8s-io">Create</H2>
+<P>create a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/node.k8s.io/v1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-runtimeclass-v1-node-k8s-io">Patch</H2>
+<P>partially update the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-runtimeclass-v1-node-k8s-io">Replace</H2>
+<P>replace the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-runtimeclass-v1-node-k8s-io">Delete</H2>
+<P>delete a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-runtimeclass-v1-node-k8s-io">Delete Collection</H2>
+<P>delete collection of RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-runtimeclass-v1-node-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-runtimeclass-v1-node-k8s-io">Read</H2>
+<P>read the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-runtimeclass-v1-node-k8s-io">List</H2>
+<P>list or watch objects of kind RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-runtimeclass-v1-node-k8s-io">Watch</H2>
+<P>watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1/watch/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-runtimeclass-v1-node-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1/watch/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview v1 authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SelfSubjectAccessReview</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated.  user and groups must be empty</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec v1 authorization</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
+<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-selfsubjectaccessreview-v1-authorization-k8s-io">Create</H2>
+<P>create a SelfSubjectAccessReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview v1 authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SelfSubjectRulesReview</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectrulesreviewspec-v1-authorization-k8s-io">SelfSubjectRulesReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates the set of actions a user can perform.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="selfsubjectrulesreviewspec-v1-authorization-k8s-io">SelfSubjectRulesReviewSpec v1 authorization</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace to evaluate rules for. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-selfsubjectrulesreview-v1-authorization-k8s-io">Create</H2>
+<P>create a SelfSubjectRulesReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="serviceaccount-v1-core">ServiceAccount v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceAccount</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#serviceaccountlist-v1-core">ServiceAccountList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>automountServiceAccountToken</CODE><BR /><I>boolean</I></TD><TD>AutomountServiceAccountToken indicates whether pods running as this service account should have an API token automatically mounted. Can be overridden at the pod level.</TD></TR>
+<TR><TD><CODE>imagePullSecrets</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a> array</I></TD><TD>ImagePullSecrets is a list of references to secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. ImagePullSecrets are distinct from Secrets because Secrets can be mounted in the pod, but ImagePullSecrets are only accessed by the kubelet. More info: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>secrets</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Secrets is the list of secrets allowed to be used by pods running using this ServiceAccount. More info: https://kubernetes.io/docs/concepts/configuration/secret</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="serviceaccountlist-v1-core">ServiceAccountList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#serviceaccount-v1-core">ServiceAccount</a> array</I></TD><TD>List of ServiceAccounts. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-serviceaccount-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-serviceaccount-v1-core">Create</H2>
+<P>create a ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-serviceaccount-v1-core">Patch</H2>
+<P>partially update the specified ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-serviceaccount-v1-core">Replace</H2>
+<P>replace the specified ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-serviceaccount-v1-core">Delete</H2>
+<P>delete a ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-serviceaccount-v1-core">Delete Collection</H2>
+<P>delete collection of ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-serviceaccount-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-serviceaccount-v1-core">Read</H2>
+<P>read the specified ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-serviceaccount-v1-core">List</H2>
+<P>list or watch objects of kind ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccountlist-v1-core">ServiceAccountList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-serviceaccount-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind ServiceAccount</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/serviceaccounts</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#serviceaccountlist-v1-core">ServiceAccountList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-serviceaccount-v1-core">Watch</H2>
+<P>watch changes to an object of kind ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-serviceaccount-v1-core">Watch List</H2>
+<P>watch individual changes to a list of ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-serviceaccount-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/serviceaccounts</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion v1alpha1 internal.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersion</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList [apiserverinternal/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>The name is &lt;group&gt;.&lt;resource&gt;.</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#storageversionspec-v1alpha1-internal-apiserver-k8s-io">StorageVersionSpec</a></I></TD><TD>Spec is an empty spec. It is here to comply with Kubernetes API style.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus</a></I></TD><TD>API server instances report the version they can decode and the version they encode objects to when persisting objects in the backend.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="storageversionspec-v1alpha1-internal-apiserver-k8s-io">StorageVersionSpec v1alpha1 apiserverinternal</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H3 id="storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus v1alpha1 apiserverinternal</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>commonEncodingVersion</CODE><BR /><I>string</I></TD><TD>If all API server instances agree on the same encoding storage version, then this field is set to that version. Otherwise this field is left empty. API servers should finish updating its storageVersionStatus entry before serving write operations, so that this field will be in sync with the reality.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io">StorageVersionCondition</a> array</I></TD><TD>The latest available observations of the storageVersion&#39;s state.</TD></TR>
+<TR><TD><CODE>storageVersions</CODE><BR /><I><a href="#serverstorageversion-v1alpha1-internal-apiserver-k8s-io">ServerStorageVersion</a> array</I></TD><TD>The reported versions per API server instance.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList v1alpha1 apiserverinternal</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a> array</I></TD><TD>Items holds a list of StorageVersion</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-storageversion-v1alpha1-internal-apiserver-k8s-io">Create</H2>
+<P>create a StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-storageversion-v1alpha1-internal-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-storageversion-v1alpha1-internal-apiserver-k8s-io">Replace</H2>
+<P>replace the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-storageversion-v1alpha1-internal-apiserver-k8s-io">Delete</H2>
+<P>delete a StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-storageversion-v1alpha1-internal-apiserver-k8s-io">Read</H2>
+<P>read the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-storageversion-v1alpha1-internal-apiserver-k8s-io">List</H2>
+<P>list or watch objects of kind StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-storageversion-v1alpha1-internal-apiserver-k8s-io">Watch</H2>
+<P>watch changes to an object of kind StorageVersion. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/watch/storageversions/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of StorageVersion. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/watch/storageversions</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io">Patch Status</H2>
+<P>partially update status of the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-storageversion-v1alpha1-internal-apiserver-k8s-io">Read Status</H2>
+<P>read status of the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io">Replace Status</H2>
+<P>replace status of the specified StorageVersion</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview v1 authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SubjectAccessReview</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec v1 authorization</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Extra corresponds to the user.Info.GetExtra() method from the authenticator.  Since that is input to the authorizer it needs a reflection here.</TD></TR>
+<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>Groups is the groups you&#39;re testing for.</TD></TR>
+<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
+<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID information about the requesting user.</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User is the user you&#39;re testing for. If you specify &#34;User&#34; but not &#34;Groups&#34;, then is it interpreted as &#34;What if User were not a member of any groups</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus v1 authorization</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowed</CODE><BR /><I>boolean</I></TD><TD>Allowed is required. True if the action would be allowed, false otherwise.</TD></TR>
+<TR><TD><CODE>denied</CODE><BR /><I>boolean</I></TD><TD>Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.</TD></TR>
+<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason is optional.  It indicates why a request was allowed or denied.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-subjectaccessreview-v1-authorization-k8s-io">Create</H2>
+<P>create a SubjectAccessReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authorization.k8s.io/v1/subjectaccessreviews</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="tokenrequest-v1-authentication-k8s-io">TokenRequest v1 authentication.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TokenRequest</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the token can be authenticated.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec v1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences are the intendend audiences of the token. A recipient of a token must identitfy themself with an identifier in the list of audiences of the token, and otherwise should reject the token. A token issued for multiple audiences may be used to authenticate against any of the audiences listed but implies a high degree of trust between the target audiences.</TD></TR>
+<TR><TD><CODE>boundObjectRef</CODE><BR /><I><a href="#boundobjectreference-v1-authentication-k8s-io">BoundObjectReference</a></I></TD><TD>BoundObjectRef is a reference to an object that the token will be bound to. The token will only be valid for as long as the bound object exists. NOTE: The API server&#39;s TokenReview endpoint will validate the BoundObjectRef, but other audiences may not. Keep ExpirationSeconds small if you want prompt revocation.</TD></TR>
+<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>ExpirationSeconds is the requested duration of validity of the request. The token issuer may return a token with a different validity duration so a client needs to check the &#39;expiration&#39; field in a response.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus v1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>expirationTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>ExpirationTimestamp is the time of expiration of the returned token.</TD></TR>
+<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="tokenreview-v1-authentication-k8s-io">TokenReview v1 authentication.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TokenReview</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#tokenreviewspec-v1-authentication-k8s-io">TokenReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request can be authenticated.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="tokenreviewspec-v1-authentication-k8s-io">TokenReviewSpec v1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences is a list of the identifiers that the resource server presented with the token identifies as. Audience-aware token authenticators will verify that the token was intended for at least one of the audiences in this list. If no audiences are provided, the audience will default to the audience of the Kubernetes apiserver.</TD></TR>
+<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus v1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences are audience identifiers chosen by the authenticator that are compatible with both the TokenReview and token. An identifier is any identifier in the intersection of the TokenReviewSpec audiences and the token&#39;s audiences. A client of the TokenReview API that sets the spec.audiences field should validate that a compatible audience identifier is returned in the status.audiences field to ensure that the TokenReview server is audience aware. If a TokenReview returns an empty status.audience field where status.authenticated is &#34;true&#34;, the token is valid against the audience of the Kubernetes API server.</TD></TR>
+<TR><TD><CODE>authenticated</CODE><BR /><I>boolean</I></TD><TD>Authenticated indicates that the token was associated with a known user.</TD></TR>
+<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error indicates that the token couldn&#39;t be checked</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User is the UserInfo associated with the provided token.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-tokenreview-v1-authentication-k8s-io">Create</H2>
+<P>create a TokenReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authentication.k8s.io/v1/tokenreviews</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="networkpolicy-v1-networking-k8s-io">NetworkPolicy v1 networking.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec</a></I></TD><TD>Specification of the desired behavior for this NetworkPolicy.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec v1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>egress</CODE><BR /><I><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule</a> array</I></TD><TD>List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8</TD></TR>
+<TR><TD><CODE>ingress</CODE><BR /><I><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule</a> array</I></TD><TD>List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod&#39;s local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)</TD></TR>
+<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.</TD></TR>
+<TR><TD><CODE>policyTypes</CODE><BR /><I>string array</I></TD><TD>List of rule types that the NetworkPolicy relates to. Valid options are [&#34;Ingress&#34;], [&#34;Egress&#34;], or [&#34;Ingress&#34;, &#34;Egress&#34;]. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ &#34;Egress&#34; ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include &#34;Egress&#34; (since such a policy would not include an Egress section and would otherwise default to just [ &#34;Ingress&#34; ]). This field is beta-level in 1.8</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="networkpolicylist-v1-networking-k8s-io">NetworkPolicyList v1 networking</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-networkpolicy-v1-networking-k8s-io">Create</H2>
+<P>create a NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-networkpolicy-v1-networking-k8s-io">Patch</H2>
+<P>partially update the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-networkpolicy-v1-networking-k8s-io">Replace</H2>
+<P>replace the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-networkpolicy-v1-networking-k8s-io">Delete</H2>
+<P>delete a NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-networkpolicy-v1-networking-k8s-io">Delete Collection</H2>
+<P>delete collection of NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-networkpolicy-v1-networking-k8s-io">Read</H2>
+<P>read the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-networkpolicy-v1-networking-k8s-io">List</H2>
+<P>list or watch objects of kind NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-networkpolicy-v1-networking-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/networkpolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-networkpolicy-v1-networking-k8s-io">Watch</H2>
+<P>watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-networkpolicy-v1-networking-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/watch/networkpolicies</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-definitions-strong-"><STRONG>DEFINITIONS</STRONG></H1>
+
+<P>This section contains definitions for objects used in the Kubernetes APIs.</P>
+<H2 id="apigroup-v1-meta">APIGroup v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIGroup</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>APIGroup contains the name, the supported versions, and the preferred version of a group.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apigrouplist-v1-meta">APIGroupList [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the group.</TD></TR>
+<TR><TD><CODE>preferredVersion</CODE><BR /><I><a href="#groupversionfordiscovery-v1-meta">GroupVersionForDiscovery</a></I></TD><TD>preferredVersion is the version preferred by the API server, which probably is the storage version.</TD></TR>
+<TR><TD><CODE>serverAddressByClientCIDRs</CODE><BR /><I><a href="#serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR</a> array</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>versions</CODE><BR /><I><a href="#groupversionfordiscovery-v1-meta">GroupVersionForDiscovery</a> array</I></TD><TD>versions are the versions supported in this group.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="apiresource-v1-meta">APIResource v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIResource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>APIResource specifies the name of a resource and whether it is namespaced.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiresourcelist-v1-meta">APIResourceList [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>categories</CODE><BR /><I>string array</I></TD><TD>categories is a list of the grouped resources this resource belongs to (e.g. &#39;all&#39;)</TD></TR>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>group is the preferred group of the resource.  Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale&#34;.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the kind for the resource (e.g. &#39;Foo&#39; is the kind for a resource &#39;foo&#39;)</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the plural name of the resource.</TD></TR>
+<TR><TD><CODE>namespaced</CODE><BR /><I>boolean</I></TD><TD>namespaced indicates if a resource is namespaced or not.</TD></TR>
+<TR><TD><CODE>shortNames</CODE><BR /><I>string array</I></TD><TD>shortNames is a list of suggested short names of the resource.</TD></TR>
+<TR><TD><CODE>singularName</CODE><BR /><I>string</I></TD><TD>singularName is the singular name of the resource.  This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.</TD></TR>
+<TR><TD><CODE>storageVersionHash</CODE><BR /><I>string</I></TD><TD>The hash value of the storage version, the version this resource is converted to when written to the data store. Value must be treated as opaque by clients. Only equality comparison on the value is valid. This is an alpha feature and may change or be removed in the future. The field is populated by the apiserver only if the StorageVersionHash feature gate is enabled. This field will remain optional even if it graduates.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)</TD></TR>
+<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>version is the preferred version of the resource.  Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource&#39;s group)&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition v1 apiregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIServiceCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>APIServiceCondition describes the state of an APIService at a particular point</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus [apiregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="apiversions-v1-meta">APIVersions v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIVersions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>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.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>serverAddressByClientCIDRs</CODE><BR /><I><a href="#serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR</a> array</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>versions</CODE><BR /><I>string array</I></TD><TD>versions are the api versions that are available.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AWSElasticBlockStoreVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>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.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>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 &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty).</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Specify &#34;true&#34; to force and set the ReadOnly property in VolumeMounts to &#34;true&#34;. If omitted, the default is &#34;false&#34;. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>Unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="affinity-v1-core">Affinity v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Affinity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Affinity is a group of affinity scheduling rules.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nodeAffinity</CODE><BR /><I><a href="#nodeaffinity-v1-core">NodeAffinity</a></I></TD><TD>Describes node affinity scheduling rules for the pod.</TD></TR>
+<TR><TD><CODE>podAffinity</CODE><BR /><I><a href="#podaffinity-v1-core">PodAffinity</a></I></TD><TD>Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).</TD></TR>
+<TR><TD><CODE>podAntiAffinity</CODE><BR /><I><a href="#podantiaffinity-v1-core">PodAntiAffinity</a></I></TD><TD>Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule v1 rbac.authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AggregationRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>clusterRoleSelectors</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a> array</I></TD><TD>ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole&#39;s permissions will be added</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="allowedcsidriver-v1beta1-policy">AllowedCSIDriver v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedCSIDriver</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AllowedCSIDriver represents a single inline CSI Driver that is allowed to be used.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the registered name of the CSI driver</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="allowedflexvolume-v1beta1-policy">AllowedFlexVolume v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedFlexVolume</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AllowedFlexVolume represents a single Flexvolume that is allowed to be used.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>driver is the name of the Flexvolume driver.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="allowedhostpath-v1beta1-policy">AllowedHostPath v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedHostPath</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AllowedHostPath defines the host volume conditions that will be enabled by a policy for pods to use. It requires the path prefix to be defined.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pathPrefix</CODE><BR /><I>string</I></TD><TD>pathPrefix is the path prefix that the host volume must match. It does not support `*`. Trailing slashes are trimmed when validating the path prefix with a host path.  Examples: `/foo` would allow `/foo`, `/foo/` and `/foo/bar` `/foo` would not allow `/food` or `/etc/foo`</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>when set to true, will allow host volumes matching the pathPrefix only if all volume mounts are readOnly.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="attachedvolume-v1-core">AttachedVolume v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AttachedVolume</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AttachedVolume describes a volume attached to a node</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>devicePath</CODE><BR /><I>string</I></TD><TD>DevicePath represents the device path where the volume should be available</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the attached volume</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="azurediskvolumesource-v1-core">AzureDiskVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureDiskVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>cachingMode</CODE><BR /><I>string</I></TD><TD>Host Caching mode: None, Read Only, Read Write.</TD></TR>
+<TR><TD><CODE>diskName</CODE><BR /><I>string</I></TD><TD>The Name of the data disk in the blob storage</TD></TR>
+<TR><TD><CODE>diskURI</CODE><BR /><I>string</I></TD><TD>The URI the data disk in the blob storage</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Expected values Shared: multiple blob disks per storage account  Dedicated: single blob disk per storage account  Managed: azure managed data disk (only in managed availability set). defaults to shared</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="azurefilepersistentvolumesource-v1-core">AzureFilePersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureFilePersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>the name of secret that contains Azure Storage Account Name and Key</TD></TR>
+<TR><TD><CODE>secretNamespace</CODE><BR /><I>string</I></TD><TD>the namespace of the secret that contains Azure Storage Account Name and Key default is the same as the Pod</TD></TR>
+<TR><TD><CODE>shareName</CODE><BR /><I>string</I></TD><TD>Share Name</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="azurefilevolumesource-v1-core">AzureFileVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureFileVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>the name of secret that contains Azure Storage Account Name and Key</TD></TR>
+<TR><TD><CODE>shareName</CODE><BR /><I>string</I></TD><TD>Share Name</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="boundobjectreference-v1-authentication-k8s-io">BoundObjectReference v1 authentication.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>BoundObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>BoundObjectReference is a reference to an object that a token is bound to.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent. Valid kinds are &#39;Pod&#39; and &#39;Secret&#39;.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="csinodedriver-v1-storage-k8s-io">CSINodeDriver v1 storage.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSINodeDriver</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CSINodeDriver holds information about the specification of one CSI driver installed on a node</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csinodespec-v1-storage-k8s-io">CSINodeSpec [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocatable</CODE><BR /><I><a href="#volumenoderesources-v1-storage-k8s-io">VolumeNodeResources</a></I></TD><TD>allocatable represents the volume resources of a node that are available for scheduling. This field is beta.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>This is the name of the CSI driver that this object refers to. This MUST be the same name returned by the CSI GetPluginName() call for that driver.</TD></TR>
+<TR><TD><CODE>nodeID</CODE><BR /><I>string</I></TD><TD>nodeID of the node from the driver point of view. This field enables Kubernetes to communicate with storage systems that do not share the same nomenclature for nodes. For example, Kubernetes may refer to a given node as &#34;node1&#34;, but the storage system may refer to the same node as &#34;nodeA&#34;. When Kubernetes issues a command to the storage system to attach a volume to a specific node, it can use this field to refer to the node name using the ID that the storage system will understand, e.g. &#34;nodeA&#34; instead of &#34;node1&#34;. This field is required.</TD></TR>
+<TR><TD><CODE>topologyKeys</CODE><BR /><I>string array</I></TD><TD>topologyKeys is the list of keys supported by the driver. When a driver is initialized on a cluster, it provides a set of topology keys that it understands (e.g. &#34;company.com/zone&#34;, &#34;company.com/region&#34;). When a driver is initialized on a node, it provides the same topology keys along with values. Kubelet will expose these topology keys as labels on its own node object. When Kubernetes does topology aware provisioning, it can use this list to determine which labels it should retrieve from the node object and pass back to the driver. It is possible for different nodes to use different topology keys. This can be empty if driver does not support topology.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="csipersistentvolumesource-v1-core">CSIPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSIPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents storage that is managed by an external CSI volume driver (Beta feature)</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>controllerExpandSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>ControllerExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerExpandVolume call. This is an alpha field and requires enabling ExpandCSIVolumes feature gate. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
+<TR><TD><CODE>controllerPublishSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>ControllerPublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerPublishVolume and ControllerUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
+<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume. Required.</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;.</TD></TR>
+<TR><TD><CODE>nodePublishSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>NodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
+<TR><TD><CODE>nodeStageSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>NodeStageSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeStageVolume and NodeStageVolume and NodeUnstageVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: The value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).</TD></TR>
+<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>Attributes of the volume to publish.</TD></TR>
+<TR><TD><CODE>volumeHandle</CODE><BR /><I>string</I></TD><TD>VolumeHandle is the unique volume name returned by the CSI volume plugin’s CreateVolume to refer to the volume on all subsequent calls. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="csivolumesource-v1-core">CSIVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSIVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a source location of a volume to mount, managed by an external CSI driver</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster.</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply.</TD></TR>
+<TR><TD><CODE>nodePublishSecretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>NodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and  may be empty if no secret is required. If the secret object contains more than one secret, all secret references are passed.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Specifies a read-only configuration for the volume. Defaults to false (read/write).</TD></TR>
+<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>VolumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver&#39;s documentation for supported values.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="capabilities-v1-core">Capabilities v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Capabilities</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Adds and removes POSIX capabilities from running containers.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>add</CODE><BR /><I>string array</I></TD><TD>Added capabilities</TD></TR>
+<TR><TD><CODE>drop</CODE><BR /><I>string array</I></TD><TD>Removed capabilities</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CephFSPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Optional: Used as the mounted root, rather than the full Ceph tree, default is /</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>Optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="cephfsvolumesource-v1-core">CephFSVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CephFSVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Optional: Used as the mounted root, rather than the full Ceph tree, default is /</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>Optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="certificatesigningrequestcondition-v1-certificates-k8s-io">CertificateSigningRequestCondition v1 certificates.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CertificateSigningRequestCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus [certificates/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition&#39;s status is changed, the server defaults this to the current time.</TD></TR>
+<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastUpdateTime is the time of the last update to this condition</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message contains a human readable message with details about the request state</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason indicates a brief reason for the request state</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be &#34;False&#34; or &#34;Unknown&#34;.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type of the condition. Known conditions are &#34;Approved&#34;, &#34;Denied&#34;, and &#34;Failed&#34;.  An &#34;Approved&#34; condition is added via the /approval subresource, indicating the request was approved and should be issued by the signer.  A &#34;Denied&#34; condition is added via the /approval subresource, indicating the request was denied and should not be issued by the signer.  A &#34;Failed&#34; condition is added via the /status subresource, indicating the signer failed to issue the certificate.  Approved and Denied conditions are mutually exclusive. Approved, Denied, and Failed conditions cannot be removed once added.  Only one condition of a given type is allowed.  Possible enum values:  - `&#34;Approved&#34;` Approved indicates the request was approved and should be issued by the signer.  - `&#34;Denied&#34;` Denied indicates the request was denied and should not be issued by the signer.  - `&#34;Failed&#34;` Failed indicates the signer failed to issue the certificate.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CinderPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>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.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: points to a secret object containing parameters used to connect to OpenStack.</TD></TR>
+<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="cindervolumesource-v1-core">CinderVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CinderVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>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.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: points to a secret object containing parameters used to connect to OpenStack.</TD></TR>
+<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="clientipconfig-v1-core">ClientIPConfig v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClientIPConfig</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ClientIPConfig represents the configurations of Client IP based session affinity.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#sessionaffinityconfig-v1-core">SessionAffinityConfig [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be &gt;0 &amp;&amp; &lt;=86400(for 1 day) if ServiceAffinity == &#34;ClientIP&#34;. Default value is 10800(for 3 hours).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="componentcondition-v1-core">ComponentCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ComponentCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Information about the condition of a component.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#componentstatus-v1-core">ComponentStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Condition error code for a component. For example, a health check error code.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message about the condition for a component. For example, information about a health check.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition for a component. Valid values for &#34;Healthy&#34;: &#34;True&#34;, &#34;False&#34;, or &#34;Unknown&#34;.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of condition for a component. Valid value: &#34;Healthy&#34;</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="condition-v1-meta">Condition v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Condition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Condition contains details for one aspect of the current state of this API Resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus [policy/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetstatus-v1beta1-policy">PodDisruptionBudgetStatus [policy/v1beta1]</a></LI>
+  <LI><a href="#servicestatus-v1-core">ServiceStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human readable message indicating details about the transition. This may be an empty string.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason contains a programmatic identifier indicating the reason for the condition&#39;s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type of condition in CamelCase or in foo.example.com/CamelCase.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="configmapenvsource-v1-core">ConfigMapEnvSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapEnvSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ConfigMapEnvSource selects a ConfigMap to populate the environment variables with.
+
+The contents of the target ConfigMap&#39;s Data field will represent the key-value pairs as environment variables.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#envfromsource-v1-core">EnvFromSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="configmapkeyselector-v1-core">ConfigMapKeySelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapKeySelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Selects a key from a ConfigMap.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key to select.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or its key must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="configmapnodeconfigsource-v1-core">ConfigMapNodeConfigSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapNodeConfigSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ConfigMapNodeConfigSource contains the information to reference a ConfigMap as a config source for the Node. This API is deprecated since 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeconfigsource-v1-core">NodeConfigSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>kubeletConfigKey</CODE><BR /><I>string</I></TD><TD>KubeletConfigKey declares which key of the referenced ConfigMap corresponds to the KubeletConfiguration structure This field is required in all cases.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the metadata.name of the referenced ConfigMap. This field is required in all cases.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the metadata.namespace of the referenced ConfigMap. This field is required in all cases.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>ResourceVersion is the metadata.ResourceVersion of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID is the metadata.UID of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="configmapprojection-v1-core">ConfigMapProjection v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapProjection</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Adapts a ConfigMap into a projected volume.
+
+The contents of the target ConfigMap&#39;s Data field will be presented in a projected 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. Note that this is identical to a configmap volume source without the default mode.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>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 unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or its keys must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="configmapvolumesource-v1-core">ConfigMapVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Adapts a ConfigMap into a volume.
+
+The contents of the target ConfigMap&#39;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.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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.</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>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 unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or its keys must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerimage-v1-core">ContainerImage v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerImage</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Describe a container image</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>names</CODE><BR /><I>string array</I></TD><TD>Names by which this image is known. e.g. [&#34;k8s.gcr.io/hyperkube:v1.0.7&#34;, &#34;dockerhub.io/google_containers/hyperkube:v1.0.7&#34;]</TD></TR>
+<TR><TD><CODE>sizeBytes</CODE><BR /><I>integer</I></TD><TD>The size of the image in bytes.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerport-v1-core">ContainerPort v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerPort represents a network port in a single container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerPort</CODE><BR /><I>integer</I></TD><TD>Number of port to expose on the pod&#39;s IP address. This must be a valid port number, 0 &lt; x &lt; 65536.</TD></TR>
+<TR><TD><CODE>hostIP</CODE><BR /><I>string</I></TD><TD>What host IP to bind the external port to.</TD></TR>
+<TR><TD><CODE>hostPort</CODE><BR /><I>integer</I></TD><TD>Number of port to expose on the host. If specified, this must be a valid port number, 0 &lt; x &lt; 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>Protocol for port. Must be UDP, TCP, or SCTP. Defaults to &#34;TCP&#34;.  Possible enum values:  - `&#34;SCTP&#34;` is the SCTP protocol.  - `&#34;TCP&#34;` is the TCP protocol.  - `&#34;UDP&#34;` is the UDP protocol.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerresourcemetricsource-v2-autoscaling">ContainerResourceMetricSource v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ContainerResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.  Only one &#34;target&#34; type should be set.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricsource-v2beta2-autoscaling">v2beta2</a>
+<a href="#containerresourcemetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerresourcemetricstatus-v2-autoscaling">ContainerResourceMetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ContainerResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#containerresourcemetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>Container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerstate-v1-core">ContainerState v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerState</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>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.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerstatus-v1-core">ContainerStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>running</CODE><BR /><I><a href="#containerstaterunning-v1-core">ContainerStateRunning</a></I></TD><TD>Details about a running container</TD></TR>
+<TR><TD><CODE>terminated</CODE><BR /><I><a href="#containerstateterminated-v1-core">ContainerStateTerminated</a></I></TD><TD>Details about a terminated container</TD></TR>
+<TR><TD><CODE>waiting</CODE><BR /><I><a href="#containerstatewaiting-v1-core">ContainerStateWaiting</a></I></TD><TD>Details about a waiting container</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerstaterunning-v1-core">ContainerStateRunning v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateRunning</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerStateRunning is a running state of a container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>startedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which the container was last (re-)started</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerstateterminated-v1-core">ContainerStateTerminated v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateTerminated</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerStateTerminated is a terminated state of a container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>Container&#39;s ID in the format &#39;docker://&lt;container_id&gt;&#39;</TD></TR>
+<TR><TD><CODE>exitCode</CODE><BR /><I>integer</I></TD><TD>Exit status from the last termination of the container</TD></TR>
+<TR><TD><CODE>finishedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which the container last terminated</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message regarding the last termination of the container</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason from the last termination of the container</TD></TR>
+<TR><TD><CODE>signal</CODE><BR /><I>integer</I></TD><TD>Signal from the last termination of the container</TD></TR>
+<TR><TD><CODE>startedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which previous execution of the container started</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerstatewaiting-v1-core">ContainerStateWaiting v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateWaiting</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerStateWaiting is a waiting state of a container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message regarding why the container is not yet running.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason the container is not yet running.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference v1 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CrossVersionObjectReference contains enough information to let you identify the referred resource.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#crossversionobjectreference-v2-autoscaling">v2</a>
+<a href="#crossversionobjectreference-v2beta2-autoscaling">v2beta2</a>
+<a href="#crossversionobjectreference-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcecolumndefinition-v1-apiextensions-k8s-io">CustomResourceColumnDefinition v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceColumnDefinition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceColumnDefinition specifies a column for server side printing.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD>description is a human readable description of this column.</TD></TR>
+<TR><TD><CODE>format</CODE><BR /><I>string</I></TD><TD>format is an optional OpenAPI type definition for this column. The &#39;name&#39; format is applied to the primary identifier column to assist in clients identifying column is the resource name. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.</TD></TR>
+<TR><TD><CODE>jsonPath</CODE><BR /><I>string</I></TD><TD>jsonPath is a simple JSON path (i.e. with array notation) which is evaluated against each custom resource to produce the value for this column.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is a human readable name for the column.</TD></TR>
+<TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>priority is an integer defining the relative importance of this column compared to others. Lower numbers are considered higher priority. Columns that may be omitted in limited space scenarios should be given a priority greater than 0.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is an OpenAPI type definition for this column. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourceconversion-v1-apiextensions-k8s-io">CustomResourceConversion v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceConversion</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceConversion describes how to convert different versions of a CR.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>strategy</CODE><BR /><I>string</I></TD><TD>strategy specifies how custom resources are converted between versions. Allowed values are: - `None`: The converter only change the apiVersion and would not touch any other field in the custom resource. - `Webhook`: API Server will call to an external webhook to do the conversion. Additional information   is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhook to be set.</TD></TR>
+<TR><TD><CODE>webhook</CODE><BR /><I><a href="#webhookconversion-v1-apiextensions-k8s-io">WebhookConversion</a></I></TD><TD>webhook describes how to call the conversion webhook. Required when `strategy` is set to `Webhook`.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcedefinitioncondition-v1-apiextensions-k8s-io">CustomResourceDefinitionCondition v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceDefinitionCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceDefinitionCondition contains details for the current condition of this pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is a unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status is the status of the condition. Can be True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of the condition. Types include Established, NamesAccepted and Terminating.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcedefinitionnames-v1-apiextensions-k8s-io">CustomResourceDefinitionNames v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceDefinitionNames</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceDefinitionNames indicates the names to serve this CustomResourceDefinition</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</a></LI>
+  <LI><a href="#customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>categories</CODE><BR /><I>string array</I></TD><TD>categories is a list of grouped resources this custom resource belongs to (e.g. &#39;all&#39;). This is published in API discovery documents, and used by clients to support invocations like `kubectl get all`.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the serialized kind of the resource. It is normally CamelCase and singular. Custom resource instances will use this value as the `kind` attribute in API calls.</TD></TR>
+<TR><TD><CODE>listKind</CODE><BR /><I>string</I></TD><TD>listKind is the serialized kind of the list for this resource. Defaults to &#34;`kind`List&#34;.</TD></TR>
+<TR><TD><CODE>plural</CODE><BR /><I>string</I></TD><TD>plural is the plural name of the resource to serve. The custom resources are served under `/apis/&lt;group&gt;/&lt;version&gt;/.../&lt;plural&gt;`. Must match the name of the CustomResourceDefinition (in the form `&lt;names.plural&gt;.&lt;group&gt;`). Must be all lowercase.</TD></TR>
+<TR><TD><CODE>shortNames</CODE><BR /><I>string array</I></TD><TD>shortNames are short names for the resource, exposed in API discovery documents, and used by clients to support invocations like `kubectl get &lt;shortname&gt;`. It must be all lowercase.</TD></TR>
+<TR><TD><CODE>singular</CODE><BR /><I>string</I></TD><TD>singular is the singular name of the resource. It must be all lowercase. Defaults to lowercased `kind`.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceDefinitionVersion</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceDefinitionVersion describes a version for CRD.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>additionalPrinterColumns</CODE><BR /><I><a href="#customresourcecolumndefinition-v1-apiextensions-k8s-io">CustomResourceColumnDefinition</a> array</I></TD><TD>additionalPrinterColumns specifies additional columns returned in Table output. See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for details. If no columns are specified, a single column displaying the age of the custom resource is used.</TD></TR>
+<TR><TD><CODE>deprecated</CODE><BR /><I>boolean</I></TD><TD>deprecated indicates this version of the custom resource API is deprecated. When set to true, API requests to this version receive a warning header in the server response. Defaults to false.</TD></TR>
+<TR><TD><CODE>deprecationWarning</CODE><BR /><I>string</I></TD><TD>deprecationWarning overrides the default warning returned to API clients. May only be set when `deprecated` is true. The default warning indicates this version is deprecated and recommends use of the newest served version of equal or greater stability, if one exists.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the version name, e.g. “v1”, “v2beta1”, etc. The custom resources are served under this version at `/apis/&lt;group&gt;/&lt;version&gt;/...` if `served` is true.</TD></TR>
+<TR><TD><CODE>schema</CODE><BR /><I><a href="#customresourcevalidation-v1-apiextensions-k8s-io">CustomResourceValidation</a></I></TD><TD>schema describes the schema used for validation, pruning, and defaulting of this version of the custom resource.</TD></TR>
+<TR><TD><CODE>served</CODE><BR /><I>boolean</I></TD><TD>served is a flag enabling/disabling this version from being served via REST APIs</TD></TR>
+<TR><TD><CODE>storage</CODE><BR /><I>boolean</I></TD><TD>storage indicates this version should be used when persisting custom resources to storage. There must be exactly one version with storage=true.</TD></TR>
+<TR><TD><CODE>subresources</CODE><BR /><I><a href="#customresourcesubresources-v1-apiextensions-k8s-io">CustomResourceSubresources</a></I></TD><TD>subresources specify what subresources this version of the defined custom resource have.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcesubresourcescale-v1-apiextensions-k8s-io">CustomResourceSubresourceScale v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceSubresourceScale</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceSubresourceScale defines how to serve the scale subresource for CustomResources.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcesubresources-v1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>labelSelectorPath</CODE><BR /><I>string</I></TD><TD>labelSelectorPath defines the JSON path inside of a custom resource that corresponds to Scale `status.selector`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status` or `.spec`. Must be set to work with HorizontalPodAutoscaler. The field pointed by this JSON path must be a string field (not a complex selector struct) which contains a serialized label selector in string form. More info: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions#scale-subresource If there is no value under the given path in the custom resource, the `status.selector` value in the `/scale` subresource will default to the empty string.</TD></TR>
+<TR><TD><CODE>specReplicasPath</CODE><BR /><I>string</I></TD><TD>specReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `spec.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.spec`. If there is no value under the given path in the custom resource, the `/scale` subresource will return an error on GET.</TD></TR>
+<TR><TD><CODE>statusReplicasPath</CODE><BR /><I>string</I></TD><TD>statusReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `status.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status`. If there is no value under the given path in the custom resource, the `status.replicas` value in the `/scale` subresource will default to 0.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcesubresourcestatus-v1-apiextensions-k8s-io">CustomResourceSubresourceStatus v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceSubresourceStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the `.status` JSON path inside of a CustomResource. When set, * exposes a /status subresource for the custom resource * PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcesubresources-v1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="customresourcesubresources-v1-apiextensions-k8s-io">CustomResourceSubresources v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceSubresources</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceSubresources defines the status and scale subresources for CustomResources.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>scale</CODE><BR /><I><a href="#customresourcesubresourcescale-v1-apiextensions-k8s-io">CustomResourceSubresourceScale</a></I></TD><TD>scale indicates the custom resource should serve a `/scale` subresource that returns an `autoscaling/v1` Scale object.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#customresourcesubresourcestatus-v1-apiextensions-k8s-io">CustomResourceSubresourceStatus</a></I></TD><TD>status indicates the custom resource should serve a `/status` subresource. When enabled: 1. requests to the custom resource primary endpoint ignore changes to the `status` stanza of the object. 2. requests to the custom resource `/status` subresource ignore changes to anything other than the `status` stanza of the object.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="customresourcevalidation-v1-apiextensions-k8s-io">CustomResourceValidation v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CustomResourceValidation</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>CustomResourceValidation is a list of validation methods for CustomResources.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>openAPIV3Schema</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD>openAPIV3Schema is the OpenAPI v3 schema to use for validation and pruning.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="daemonendpoint-v1-core">DaemonEndpoint v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonEndpoint</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DaemonEndpoint contains information about a single Daemon endpoint.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodedaemonendpoints-v1-core">NodeDaemonEndpoints [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>Port</CODE><BR /><I>integer</I></TD><TD>Port number of the given endpoint.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="daemonsetcondition-v1-apps">DaemonSetCondition v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSetCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DaemonSetCondition describes the state of a DaemonSet at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonsetstatus-v1-apps">DaemonSetStatus [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of DaemonSet condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSetUpdateStrategy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedaemonset-v1-apps">RollingUpdateDaemonSet</a></I></TD><TD>Rolling update config params. Present only if type = &#34;RollingUpdate&#34;.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of daemon set update. Can be &#34;RollingUpdate&#34; or &#34;OnDelete&#34;. Default is RollingUpdate.  Possible enum values:  - `&#34;OnDelete&#34;` Replace the old daemons only when it&#39;s killed  - `&#34;RollingUpdate&#34;` Replace the old daemons by new ones using rolling update i.e replace them on each node one after the other.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="deleteoptions-v1-meta">DeleteOptions v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DeleteOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DeleteOptions may be provided when deleting an API object.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#eviction-v1-policy">Eviction [policy/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>dryRun</CODE><BR /><I>string array</I></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE><BR /><I>boolean</I></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the &#34;orphan&#34; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>preconditions</CODE><BR /><I><a href="#preconditions-v1-meta">Preconditions</a></I></TD><TD>Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE><BR /><I>string</I></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="deploymentcondition-v1-apps">DeploymentCondition v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DeploymentCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DeploymentCondition describes the state of a deployment at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deploymentstatus-v1-apps">DeploymentStatus [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time this condition was updated.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="downwardapiprojection-v1-core">DownwardAPIProjection v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIProjection</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile</a> array</I></TD><TD>Items is a list of DownwardAPIVolume file</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="downwardapivolumefile-v1-core">DownwardAPIVolumeFile v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIVolumeFile</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DownwardAPIVolumeFile represents information to create the file containing the pod field</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#downwardapiprojection-v1-core">DownwardAPIProjection [core/v1]</a></LI>
+  <LI><a href="#downwardapivolumesource-v1-core">DownwardAPIVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fieldRef</CODE><BR /><I><a href="#objectfieldselector-v1-core">ObjectFieldSelector</a></I></TD><TD>Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.</TD></TR>
+<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Required: Path is  the relative path name of the file to be created. Must not be absolute or contain the &#39;..&#39; path. Must be utf-8 encoded. The first item of the relative path must not start with &#39;..&#39;</TD></TR>
+<TR><TD><CODE>resourceFieldRef</CODE><BR /><I><a href="#resourcefieldselector-v1-core">ResourceFieldSelector</a></I></TD><TD>Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="downwardapivolumesource-v1-core">DownwardAPIVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>DownwardAPIVolumeSource represents a volume containing downward API info. Downward API volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on created files by default. Must be a Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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.</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile</a> array</I></TD><TD>Items is a list of downward API volume file</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="emptydirvolumesource-v1-core">EmptyDirVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EmptyDirVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>medium</CODE><BR /><I>string</I></TD><TD>What type of storage medium should back this directory. The default is &#34;&#34; which means to use the node&#39;s default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir</TD></TR>
+<TR><TD><CODE>sizeLimit</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpoint-v1-discovery-k8s-io">Endpoint v1 discovery.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Endpoint</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Endpoint represents a single logical &#34;backend&#34; implementing a service.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpoint-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addresses</CODE><BR /><I>string array</I></TD><TD>addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#endpointconditions-v1-discovery-k8s-io">EndpointConditions</a></I></TD><TD>conditions contains information about the current status of the endpoint.</TD></TR>
+<TR><TD><CODE>deprecatedTopology</CODE><BR /><I>object</I></TD><TD>deprecatedTopology contains topology information part of the v1beta1 API. This field is deprecated, and will be removed when the v1beta1 API is removed (no sooner than kubernetes v1.24).  While this field can hold values, it is not writable through the v1 API, and any attempts to write to it will be silently ignored. Topology information can be found in the zone and nodeName fields instead.</TD></TR>
+<TR><TD><CODE>hints</CODE><BR /><I><a href="#endpointhints-v1-discovery-k8s-io">EndpointHints</a></I></TD><TD>hints contains information associated with how an endpoint should be consumed.</TD></TR>
+<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.</TD></TR>
+<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>nodeName represents the name of the Node hosting this endpoint. This can be used to determine endpoints local to a Node. This field can be enabled with the EndpointSliceNodeName feature gate.</TD></TR>
+<TR><TD><CODE>targetRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>targetRef is a reference to a Kubernetes object that represents this endpoint.</TD></TR>
+<TR><TD><CODE>zone</CODE><BR /><I>string</I></TD><TD>zone is the name of the Zone this endpoint exists in.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpointaddress-v1-core">EndpointAddress v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointAddress</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EndpointAddress is a tuple that describes single IP address.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointsubset-v1-core">EndpointSubset [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>The Hostname of this endpoint</TD></TR>
+<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.</TD></TR>
+<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>Optional: Node hosting this endpoint. This can be used to determine endpoints local to a node.</TD></TR>
+<TR><TD><CODE>targetRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>Reference to object providing the endpoint.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpointconditions-v1-discovery-k8s-io">EndpointConditions v1 discovery.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointConditions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EndpointConditions represents the current condition of an endpoint.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointconditions-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be &#34;true&#34; for terminating endpoints.</TD></TR>
+<TR><TD><CODE>serving</CODE><BR /><I>boolean</I></TD><TD>serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.</TD></TR>
+<TR><TD><CODE>terminating</CODE><BR /><I>boolean</I></TD><TD>terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpointhints-v1-discovery-k8s-io">EndpointHints v1 discovery.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointHints</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EndpointHints provides hints describing how an endpoint should be consumed.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointhints-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>forZones</CODE><BR /><I><a href="#forzone-v1-discovery-k8s-io">ForZone</a> array</I></TD><TD>forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpointport-v1-core">EndpointPort v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EndpointPort is a tuple that describes a single port.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointport-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointsubset-v1-core">EndpointSubset [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port.  This must match the &#39;name&#39; field in the corresponding ServicePort. Must be a DNS_LABEL. Optional only if one port is defined.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port number of the endpoint.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.  Possible enum values:  - `&#34;SCTP&#34;` is the SCTP protocol.  - `&#34;TCP&#34;` is the TCP protocol.  - `&#34;UDP&#34;` is the UDP protocol.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="endpointsubset-v1-core">EndpointSubset v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointSubset</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:
+  {
+    Addresses: [{&#34;ip&#34;: &#34;10.10.1.1&#34;}, {&#34;ip&#34;: &#34;10.10.2.2&#34;}],
+    Ports:     [{&#34;name&#34;: &#34;a&#34;, &#34;port&#34;: 8675}, {&#34;name&#34;: &#34;b&#34;, &#34;port&#34;: 309}]
+  }
+The resulting set of endpoints can be viewed as:
+    a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],
+    b: [ 10.10.1.1:309, 10.10.2.2:309 ]</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpoints-v1-core">Endpoints [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addresses</CODE><BR /><I><a href="#endpointaddress-v1-core">EndpointAddress</a> array</I></TD><TD>IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.</TD></TR>
+<TR><TD><CODE>notReadyAddresses</CODE><BR /><I><a href="#endpointaddress-v1-core">EndpointAddress</a> array</I></TD><TD>IP addresses which offer the related ports but are not currently marked as ready because they have not yet finished starting, have recently failed a readiness check, or have recently failed a liveness check.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#endpointport-v1-core">EndpointPort</a> array</I></TD><TD>Port numbers available on the related IP addresses.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="envfromsource-v1-core">EnvFromSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvFromSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EnvFromSource represents the source of a set of ConfigMaps</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>configMapRef</CODE><BR /><I><a href="#configmapenvsource-v1-core">ConfigMapEnvSource</a></I></TD><TD>The ConfigMap to select from</TD></TR>
+<TR><TD><CODE>prefix</CODE><BR /><I>string</I></TD><TD>An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretenvsource-v1-core">SecretEnvSource</a></I></TD><TD>The Secret to select from</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="envvar-v1-core">EnvVar v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvVar</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EnvVar represents an environment variable present in a Container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the environment variable. Must be a C_IDENTIFIER.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Variable references $(VAR_NAME) are expanded using the previously defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to &#34;&#34;.</TD></TR>
+<TR><TD><CODE>valueFrom</CODE><BR /><I><a href="#envvarsource-v1-core">EnvVarSource</a></I></TD><TD>Source for the environment variable&#39;s value. Cannot be used if value is not empty.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="envvarsource-v1-core">EnvVarSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvVarSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EnvVarSource represents a source for the value of an EnvVar.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#envvar-v1-core">EnvVar [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>configMapKeyRef</CODE><BR /><I><a href="#configmapkeyselector-v1-core">ConfigMapKeySelector</a></I></TD><TD>Selects a key of a ConfigMap.</TD></TR>
+<TR><TD><CODE>fieldRef</CODE><BR /><I><a href="#objectfieldselector-v1-core">ObjectFieldSelector</a></I></TD><TD>Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels[&#39;&lt;KEY&gt;&#39;]`, `metadata.annotations[&#39;&lt;KEY&gt;&#39;]`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.</TD></TR>
+<TR><TD><CODE>resourceFieldRef</CODE><BR /><I><a href="#resourcefieldselector-v1-core">ResourceFieldSelector</a></I></TD><TD>Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.</TD></TR>
+<TR><TD><CODE>secretKeyRef</CODE><BR /><I><a href="#secretkeyselector-v1-core">SecretKeySelector</a></I></TD><TD>Selects a key of a secret in the pod&#39;s namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ephemeralcontainer-v1-core">EphemeralContainer v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EphemeralContainer</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>An EphemeralContainer is a temporary container that you may add to an existing Pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a Pod is removed or restarted. The kubelet may evict a Pod if an ephemeral container causes the Pod to exceed its resource allocation.
+
+To add an ephemeral container, use the ephemeralcontainers subresource of an existing Pod. Ephemeral containers may not be removed or restarted.
+
+This is a beta feature available on clusters that haven&#39;t disabled the EphemeralContainers feature gate.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>args</CODE><BR /><I>string array</I></TD><TD>Arguments to the entrypoint. The docker image&#39;s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
+<TR><TD><CODE>command</CODE><BR /><I>string array</I></TD><TD>Entrypoint array. Not executed within a shell. The docker image&#39;s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
+<TR><TD><CODE>env</CODE><BR /><I><a href="#envvar-v1-core">EnvVar</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of environment variables to set in the container. Cannot be updated.</TD></TR>
+<TR><TD><CODE>envFrom</CODE><BR /><I><a href="#envfromsource-v1-core">EnvFromSource</a> array</I></TD><TD>List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images</TD></TR>
+<TR><TD><CODE>imagePullPolicy</CODE><BR /><I>string</I></TD><TD>Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images  Possible enum values:  - `&#34;Always&#34;` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `&#34;IfNotPresent&#34;` means that kubelet pulls if the image isn&#39;t present on disk. Container will fail if the image isn&#39;t present and the pull fails.  - `&#34;Never&#34;` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn&#39;t present</TD></TR>
+<TR><TD><CODE>lifecycle</CODE><BR /><I><a href="#lifecycle-v1-core">Lifecycle</a></I></TD><TD>Lifecycle is not allowed for ephemeral containers.</TD></TR>
+<TR><TD><CODE>livenessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the ephemeral container specified as a DNS_LABEL. This name must be unique among all containers, init containers and ephemeral containers.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#containerport-v1-core">ContainerPort</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>containerPort</I></TD><TD>Ports are not allowed for ephemeral containers.</TD></TR>
+<TR><TD><CODE>readinessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources are not allowed for ephemeral containers. Ephemeral containers use spare resources already allocated to the pod.</TD></TR>
+<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#securitycontext-v1-core">SecurityContext</a></I></TD><TD>Optional: SecurityContext defines the security options the ephemeral container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext.</TD></TR>
+<TR><TD><CODE>startupProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</TD></TR>
+<TR><TD><CODE>stdin</CODE><BR /><I>boolean</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>stdinOnce</CODE><BR /><I>boolean</I></TD><TD>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</TD></TR>
+<TR><TD><CODE>targetContainerName</CODE><BR /><I>string</I></TD><TD>If set, the name of the container from PodSpec that this ephemeral container targets. The ephemeral container will be run in the namespaces (IPC, PID, etc) of this container. If not set then the ephemeral container uses the namespaces configured in the Pod spec.  The container runtime must implement support for this feature. If the runtime does not support namespace targeting then the result of setting this field is undefined.</TD></TR>
+<TR><TD><CODE>terminationMessagePath</CODE><BR /><I>string</I></TD><TD>Optional: Path at which the file to which the container&#39;s termination message will be written is mounted into the container&#39;s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.</TD></TR>
+<TR><TD><CODE>terminationMessagePolicy</CODE><BR /><I>string</I></TD><TD>Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.  Possible enum values:  - `&#34;FallbackToLogsOnError&#34;` will read the most recent contents of the container logs for the container status message when the container exits with an error and the terminationMessagePath has no contents.  - `&#34;File&#34;` is the default behavior and will set the container status message to the contents of the container&#39;s terminationMessagePath when the container exits.</TD></TR>
+<TR><TD><CODE>tty</CODE><BR /><I>boolean</I></TD><TD>Whether this container should allocate a TTY for itself, also requires &#39;stdin&#39; to be true. Default is false.</TD></TR>
+<TR><TD><CODE>volumeDevices</CODE><BR /><I><a href="#volumedevice-v1-core">VolumeDevice</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>devicePath</I></TD><TD>volumeDevices is the list of block devices to be used by the container.</TD></TR>
+<TR><TD><CODE>volumeMounts</CODE><BR /><I><a href="#volumemount-v1-core">VolumeMount</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>mountPath</I></TD><TD>Pod volumes to mount into the container&#39;s filesystem. Subpath mounts are not allowed for ephemeral containers. Cannot be updated.</TD></TR>
+<TR><TD><CODE>workingDir</CODE><BR /><I>string</I></TD><TD>Container&#39;s working directory. If not specified, the container runtime&#39;s default will be used, which might be configured in the container image. Cannot be updated.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ephemeralvolumesource-v1-core">EphemeralVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EphemeralVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents an ephemeral volume that is handled by a normal storage driver.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>volumeClaimTemplate</CODE><BR /><I><a href="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate</a></I></TD><TD>Will be used to create a stand-alone PVC to provision the volume. The pod in which this EphemeralVolumeSource is embedded will be the owner of the PVC, i.e. the PVC will be deleted together with the pod.  The name of the PVC will be `&lt;pod name&gt;-&lt;volume name&gt;` where `&lt;volume name&gt;` is the name from the `PodSpec.Volumes` array entry. Pod validation will reject the pod if the concatenated name is not valid for a PVC (for example, too long).  An existing PVC with that name that is not owned by the pod will *not* be used for the pod to avoid using an unrelated volume by mistake. Starting the pod is then blocked until the unrelated PVC is removed. If such a pre-created PVC is meant to be used by the pod, the PVC has to updated with an owner reference to the pod once the pod exists. Normally this should not be necessary, but it may be useful when manually reconstructing a broken cluster.  This field is read-only and no changes will be made by Kubernetes to the PVC after it has been created.  Required, must not be nil.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="eventseries-v1-events-k8s-io">EventSeries v1 events.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EventSeries</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time. How often to update the EventSeries is up to the event reporters. The default event reporter in &#34;k8s.io/client-go/tools/events/event_broadcaster.go&#34; shows how this struct is updated on heartbeats and can guide customized reporter implementations.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#eventseries-v1beta1-events-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>count is the number of occurrences in this series up to the last heartbeat time.</TD></TR>
+<TR><TD><CODE>lastObservedTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>lastObservedTime is the time when last Event from the series was seen before last heartbeat.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="eventsource-v1-core">EventSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EventSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>EventSource contains information for an event.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>component</CODE><BR /><I>string</I></TD><TD>Component from which the event is generated.</TD></TR>
+<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Node name on which the event is generated.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="eviction-v1-policy">Eviction v1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Eviction</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod.  A request to cause such an eviction is created by POSTing to .../pods/&lt;pod name&gt;/evictions.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>deleteOptions</CODE><BR /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD>DeleteOptions may be provided</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>ObjectMeta describes the pod that is being evicted.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="execaction-v1-core">ExecAction v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ExecAction</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ExecAction describes a &#34;run in container&#34; action.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#lifecyclehandler-v1-core">LifecycleHandler [core/v1]</a></LI>
+  <LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>command</CODE><BR /><I>string array</I></TD><TD>Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="externaldocumentation-v1-apiextensions-k8s-io">ExternalDocumentation v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ExternalDocumentation</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ExternalDocumentation allows referencing an external resource for extended documentation.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>url</CODE><BR /><I>string</I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="externalmetricsource-v2-autoscaling">ExternalMetricSource v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ExternalMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricsource-v2beta2-autoscaling">v2beta2</a>
+<a href="#externalmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="externalmetricstatus-v2-autoscaling">ExternalMetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ExternalMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#externalmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="fcvolumesource-v1-core">FCVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FCVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>Optional: FC target lun number</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>targetWWNs</CODE><BR /><I>string array</I></TD><TD>Optional: FC target worldwide names (WWNs)</TD></TR>
+<TR><TD><CODE>wwids</CODE><BR /><I>string array</I></TD><TD>Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FSGroupStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FSGroupStrategyOptions defines the strategy type and options used to create the strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of fs groups.  If you would like to force a single fs group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what FSGroup is used in the SecurityContext.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="fieldsv1-v1-meta">FieldsV1 v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FieldsV1</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.
+
+Each key is either a &#39;.&#39; representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: &#39;f:&lt;name&gt;&#39;, where &lt;name&gt; is the name of a field in a struct, or key in a map &#39;v:&lt;value&gt;&#39;, where &lt;value&gt; is the exact json formatted value of a list item &#39;i:&lt;index&gt;&#39;, where &lt;index&gt; is position of a item in a list &#39;k:&lt;keys&gt;&#39;, where &lt;keys&gt; is a map of  a list item&#39;s key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.
+
+The exact format is defined in sigs.k8s.io/structured-merge-diff</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#managedfieldsentry-v1-meta">ManagedFieldsEntry [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlexPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FlexPersistentVolumeSource represents a generic persistent volume resource that is provisioned/attached using an exec based plugin.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume.</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default filesystem depends on FlexVolume script.</TD></TR>
+<TR><TD><CODE>options</CODE><BR /><I>object</I></TD><TD>Optional: Extra command options if any.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flexvolumesource-v1-core">FlexVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlexVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume.</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default filesystem depends on FlexVolume script.</TD></TR>
+<TR><TD><CODE>options</CODE><BR /><I>object</I></TD><TD>Optional: Extra command options if any.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flockervolumesource-v1-core">FlockerVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlockerVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>datasetName</CODE><BR /><I>string</I></TD><TD>Name of the dataset stored as metadata -&gt; name on the dataset for Flocker should be considered as deprecated</TD></TR>
+<TR><TD><CODE>datasetUUID</CODE><BR /><I>string</I></TD><TD>UUID of the dataset. This is unique identifier of a Flocker dataset</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>FlowDistinguisherMethod</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FlowDistinguisherMethod specifies the method of a flow distinguisher.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of flow distinguisher method The supported types are &#34;ByUser&#34; and &#34;ByNamespace&#34;. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>FlowSchema</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a &#34;flow distinguisher&#34;.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemalist-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#flowschemaspec-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#flowschemastatus-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaStatus</a></I></TD><TD>`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaCondition v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>FlowSchemaCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>FlowSchemaCondition describes conditions for a FlowSchema.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemastatus-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaStatus [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>`lastTransitionTime` is the last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>`message` is a human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>`status` is the status of the condition. Can be True, False, Unknown. Required.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="forzone-v1-discovery-k8s-io">ForZone v1 discovery.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ForZone</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ForZone provides information about which zones should consume this endpoint.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#forzone-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointhints-v1-discovery-k8s-io">EndpointHints [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name represents the name of the zone.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GCEPersistentDiskVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Persistent Disk resource in Google Compute Engine.
+
+A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>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 &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+<TR><TD><CODE>pdName</CODE><BR /><I>string</I></TD><TD>Unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="grpcaction-v1-core">GRPCAction v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GRPCAction</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P></P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>Port number of the gRPC service. Number must be in the range 1 to 65535.</TD></TR>
+<TR><TD><CODE>service</CODE><BR /><I>string</I></TD><TD>Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md).  If this is not specified, the default behavior is defined by gRPC.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="gitrepovolumesource-v1-core">GitRepoVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GitRepoVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling.
+
+DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod&#39;s container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>directory</CODE><BR /><I>string</I></TD><TD>Target directory name. Must not contain or start with &#39;..&#39;.  If &#39;.&#39; is supplied, the volume directory will be the git repository.  Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.</TD></TR>
+<TR><TD><CODE>repository</CODE><BR /><I>string</I></TD><TD>Repository URL</TD></TR>
+<TR><TD><CODE>revision</CODE><BR /><I>string</I></TD><TD>Commit hash for the specified revision.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="glusterfspersistentvolumesource-v1-core">GlusterfsPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GlusterfsPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>endpoints</CODE><BR /><I>string</I></TD><TD>EndpointsName is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+<TR><TD><CODE>endpointsNamespace</CODE><BR /><I>string</I></TD><TD>EndpointsNamespace is the namespace that contains Glusterfs endpoint. If this field is empty, the EndpointNamespace defaults to the same namespace as the bound PVC. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="glusterfsvolumesource-v1-core">GlusterfsVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GlusterfsVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>endpoints</CODE><BR /><I>string</I></TD><TD>EndpointsName is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="groupsubject-v1beta2-flowcontrol-apiserver-k8s-io">GroupSubject v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>GroupSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>GroupSubject holds detailed information for group-kind subject.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#groupsubject-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the user group that matches, or &#34;*&#34; to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="groupversionfordiscovery-v1-meta">GroupVersionForDiscovery v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GroupVersionForDiscovery</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>GroupVersion contains the &#34;group/version&#34; and &#34;version&#34; string of a version. It is made a struct to keep extensibility.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apigroup-v1-meta">APIGroup [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>groupVersion</CODE><BR /><I>string</I></TD><TD>groupVersion specifies the API group and version in the form &#34;group/version&#34;</TD></TR>
+<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>version specifies the version in the form of &#34;version&#34;. This is to save the clients the trouble of splitting the GroupVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="hpascalingpolicy-v2-autoscaling">HPAScalingPolicy v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>HPAScalingPolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HPAScalingPolicy is a single policy which must hold true for a specified past interval.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#hpascalingpolicy-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>periodSeconds</CODE><BR /><I>integer</I></TD><TD>PeriodSeconds specifies the window of time for which the policy should hold true. PeriodSeconds must be greater than zero and less than or equal to 1800 (30 min).</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is used to specify the scaling policy.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>Value contains the amount of change which is permitted by the policy. It must be greater than zero</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="hpascalingrules-v2-autoscaling">HPAScalingRules v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>HPAScalingRules</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HPAScalingRules configures the scaling behavior for one direction. These Rules are applied after calculating DesiredReplicas from metrics for the HPA. They can limit the scaling velocity by specifying scaling policies. They can prevent flapping by specifying the stabilization window, so that the number of replicas is not set instantly, instead, the safest value from the stabilization window is chosen.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#hpascalingrules-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerbehavior-v2-autoscaling">HorizontalPodAutoscalerBehavior [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policies</CODE><BR /><I><a href="#hpascalingpolicy-v2-autoscaling">HPAScalingPolicy</a> array</I></TD><TD>policies is a list of potential scaling polices which can be used during scaling. At least one policy must be specified, otherwise the HPAScalingRules will be discarded as invalid</TD></TR>
+<TR><TD><CODE>selectPolicy</CODE><BR /><I>string</I></TD><TD>selectPolicy is used to specify which policy should be used. If not set, the default value Max is used.</TD></TR>
+<TR><TD><CODE>stabilizationWindowSeconds</CODE><BR /><I>integer</I></TD><TD>StabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="httpgetaction-v1-core">HTTPGetAction v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPGetAction</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HTTPGetAction describes an action based on HTTP Get requests.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#lifecyclehandler-v1-core">LifecycleHandler [core/v1]</a></LI>
+  <LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.</TD></TR>
+<TR><TD><CODE>httpHeaders</CODE><BR /><I><a href="#httpheader-v1-core">HTTPHeader</a> array</I></TD><TD>Custom headers to set in the request. HTTP allows repeated headers.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path to access on the HTTP server.</TD></TR>
+<TR><TD><CODE>port</CODE></TD><TD>Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.</TD></TR>
+<TR><TD><CODE>scheme</CODE><BR /><I>string</I></TD><TD>Scheme to use for connecting to the host. Defaults to HTTP.  Possible enum values:  - `&#34;HTTP&#34;` means that the scheme used will be http://  - `&#34;HTTPS&#34;` means that the scheme used will be https://</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="httpheader-v1-core">HTTPHeader v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPHeader</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HTTPHeader describes a custom header to be used in HTTP probes</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#httpgetaction-v1-core">HTTPGetAction [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The header field name</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>The header field value</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="httpingresspath-v1-networking-k8s-io">HTTPIngressPath v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPIngressPath</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#httpingressrulevalue-v1-networking-k8s-io">HTTPIngressRuleValue [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>backend</CODE><BR /><I><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend</a></I></TD><TD>Backend defines the referenced service endpoint to which the traffic will be forwarded to.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional &#34;path&#34; part of a URL as defined by RFC 3986. Paths must begin with a &#39;/&#39; and must be present when using PathType with value &#34;Exact&#34; or &#34;Prefix&#34;.</TD></TR>
+<TR><TD><CODE>pathType</CODE><BR /><I>string</I></TD><TD>PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by &#39;/&#39;. Matching is   done on a path element by element basis. A path element refers is the   list of labels in the path split by the &#39;/&#39; separator. A request is a   match for path p if every p is an element-wise prefix of p of the   request path. Note that if the last element of the path is a substring   of the last element in request path, it is not a match (e.g. /foo/bar   matches /foo/bar/baz, but does not match /foo/barbaz). * ImplementationSpecific: Interpretation of the Path matching is up to   the IngressClass. Implementations can treat this as a separate PathType   or treat it identically to Prefix or Exact path types. Implementations are required to support all path types.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="httpingressrulevalue-v1-networking-k8s-io">HTTPIngressRuleValue v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPIngressRuleValue</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://&lt;host&gt;/&lt;path&gt;?&lt;searchpart&gt; -&gt; backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last &#39;/&#39; and before the first &#39;?&#39; or &#39;#&#39;.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressrule-v1-networking-k8s-io">IngressRule [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>paths</CODE><BR /><I><a href="#httpingresspath-v1-networking-k8s-io">HTTPIngressPath</a> array</I></TD><TD>A collection of paths that map requests to backends.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscaler-v1-autoscaling">v1</a>
+<a href="#horizontalpodautoscaler-v2beta2-autoscaling">v2beta2</a>
+<a href="#horizontalpodautoscaler-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerlist-v2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>status is the current information about the autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="horizontalpodautoscalerbehavior-v2-autoscaling">HorizontalPodAutoscalerBehavior v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>HorizontalPodAutoscalerBehavior</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HorizontalPodAutoscalerBehavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscalerbehavior-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>scaleDown</CODE><BR /><I><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleDown is scaling policy for scaling Down. If not set, the default value is to allow to scale down to minReplicas pods, with a 300 second stabilization window (i.e., the highest recommendation for the last 300sec is used).</TD></TR>
+<TR><TD><CODE>scaleUp</CODE><BR /><I><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleUp is scaling policy for scaling Up. If not set, the default value is the higher of:   * increase no more than 4 pods per 60 seconds   * double the number of pods per 60 seconds No stabilization is used.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="horizontalpodautoscalercondition-v2-autoscaling">HorizontalPodAutoscalerCondition v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>HorizontalPodAutoscalerCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscalercondition-v2beta2-autoscaling">v2beta2</a>
+<a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the last time the condition transitioned from one status to another</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human-readable explanation containing details about the transition</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is the reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status is the status of the condition (True, False, Unknown)</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type describes the current condition</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="hostalias-v1-core">HostAlias v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HostAlias</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod&#39;s hosts file.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hostnames</CODE><BR /><I>string array</I></TD><TD>Hostnames for the above IP address.</TD></TR>
+<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>IP address of the host file entry.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="hostpathvolumesource-v1-core">HostPathVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HostPathVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type for HostPath Volume Defaults to &#34;&#34; More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="hostportrange-v1beta1-policy">HostPortRange v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>HostPortRange</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>HostPortRange defines a range of host ports that will be enabled by a policy for pods to use.  It requires both the start and end to be defined.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
+<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="idrange-v1beta1-policy">IDRange v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IDRange</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IDRange provides a min/max of an allowed range of IDs.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions [policy/v1beta1]</a></LI>
+  <LI><a href="#runasgroupstrategyoptions-v1beta1-policy">RunAsGroupStrategyOptions [policy/v1beta1]</a></LI>
+  <LI><a href="#runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions [policy/v1beta1]</a></LI>
+  <LI><a href="#supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
+<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ipblock-v1-networking-k8s-io">IPBlock v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IPBlock</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IPBlock describes a particular CIDR (Ex. &#34;192.168.1.1/24&#34;,&#34;2001:db9::/64&#34;) that is allowed to the pods matched by a NetworkPolicySpec&#39;s podSelector. The except entry describes CIDRs that should not be included within this rule.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>cidr</CODE><BR /><I>string</I></TD><TD>CIDR is a string representing the IP Block Valid examples are &#34;192.168.1.1/24&#34; or &#34;2001:db9::/64&#34;</TD></TR>
+<TR><TD><CODE>except</CODE><BR /><I>string array</I></TD><TD>Except is a slice of CIDRs that should not be included within an IP Block Valid examples are &#34;192.168.1.1/24&#34; or &#34;2001:db9::/64&#34; Except values will be rejected if they are outside the CIDR range</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ISCSIPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ISCSIPersistentVolumeSource represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>chapAuthDiscovery</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Discovery CHAP authentication</TD></TR>
+<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Session CHAP authentication</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi</TD></TR>
+<TR><TD><CODE>initiatorName</CODE><BR /><I>string</I></TD><TD>Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface &lt;target portal&gt;:&lt;volume name&gt; will be created for the connection.</TD></TR>
+<TR><TD><CODE>iqn</CODE><BR /><I>string</I></TD><TD>Target iSCSI Qualified Name.</TD></TR>
+<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iSCSI Interface Name that uses an iSCSI transport. Defaults to &#39;default&#39; (tcp).</TD></TR>
+<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>iSCSI Target Lun number.</TD></TR>
+<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>iSCSI Target Portal List. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>CHAP Secret for iSCSI target and initiator authentication</TD></TR>
+<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="iscsivolumesource-v1-core">ISCSIVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ISCSIVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>chapAuthDiscovery</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Discovery CHAP authentication</TD></TR>
+<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Session CHAP authentication</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi</TD></TR>
+<TR><TD><CODE>initiatorName</CODE><BR /><I>string</I></TD><TD>Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface &lt;target portal&gt;:&lt;volume name&gt; will be created for the connection.</TD></TR>
+<TR><TD><CODE>iqn</CODE><BR /><I>string</I></TD><TD>Target iSCSI Qualified Name.</TD></TR>
+<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iSCSI Interface Name that uses an iSCSI transport. Defaults to &#39;default&#39; (tcp).</TD></TR>
+<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>iSCSI Target Lun number.</TD></TR>
+<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>CHAP Secret for iSCSI target and initiator authentication</TD></TR>
+<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressbackend-v1-networking-k8s-io">IngressBackend v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressBackend</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressBackend describes all endpoints for a given service and port.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#httpingresspath-v1-networking-k8s-io">HTTPIngressPath [networking/v1]</a></LI>
+  <LI><a href="#ingressspec-v1-networking-k8s-io">IngressSpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#typedlocalobjectreference-v1-core">TypedLocalObjectReference</a></I></TD><TD>Resource is an ObjectRef to another Kubernetes resource in the namespace of the Ingress object. If resource is specified, a service.Name and service.Port must not be specified. This is a mutually exclusive setting with &#34;Service&#34;.</TD></TR>
+<TR><TD><CODE>service</CODE><BR /><I><a href="#ingressservicebackend-v1-networking-k8s-io">IngressServiceBackend</a></I></TD><TD>Service references a Service as a Backend. This is a mutually exclusive setting with &#34;Resource&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressclassparametersreference-v1-networking-k8s-io">IngressClassParametersReference v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressClassParametersReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressclassspec-v1-networking-k8s-io">IngressClassSpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the resource being referenced. This field is required when scope is set to &#34;Namespace&#34; and must be unset when scope is set to &#34;Cluster&#34;.</TD></TR>
+<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>Scope represents if this refers to a cluster or namespace scoped resource. This may be set to &#34;Cluster&#34; (default) or &#34;Namespace&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressrule-v1-networking-k8s-io">IngressRule v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressspec-v1-networking-k8s-io">IngressSpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the &#34;host&#34; part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to    the IP in the Spec of the parent Ingress. 2. The `:` delimiter is not respected because ports are not allowed. 	  Currently the port of an Ingress is implicitly :80 for http and 	  :443 for https. Both these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.  Host can be &#34;precise&#34; which is a domain name without the terminating dot of a network host (e.g. &#34;foo.bar.com&#34;) or &#34;wildcard&#34;, which is a domain name prefixed with a single wildcard label (e.g. &#34;*.foo.com&#34;). The wildcard character &#39;\*&#39; must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == &#34;*&#34;). Requests will be matched against the Host field in the following way: 1. If Host is precise, the request matches this rule if the http host header is equal to Host. 2. If Host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule.</TD></TR>
+<TR><TD><CODE>http</CODE><BR /><I><a href="#httpingressrulevalue-v1-networking-k8s-io">HTTPIngressRuleValue</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressservicebackend-v1-networking-k8s-io">IngressServiceBackend v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressServiceBackend</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressServiceBackend references a Kubernetes Service as a Backend.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the referenced service. The service must exist in the same namespace as the Ingress object.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I><a href="#servicebackendport-v1-networking-k8s-io">ServiceBackendPort</a></I></TD><TD>Port of the referenced service. A port name or port number is required for a IngressServiceBackend.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingresstls-v1-networking-k8s-io">IngressTLS v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IngressTLS</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressTLS describes the transport layer security associated with an Ingress.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressspec-v1-networking-k8s-io">IngressSpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hosts</CODE><BR /><I>string array</I></TD><TD>Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.</TD></TR>
+<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>SecretName is the name of the secret used to terminate TLS traffic on port 443. Field is left optional to allow TLS routing based on SNI hostname alone. If the SNI host in a listener conflicts with the &#34;Host&#34; header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="json-v1-apiextensions-k8s-io">JSON v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JSON</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JSON represents any valid JSON value. These types are supported: bool, int64, float64, string, []interface{}, map[string]interface{} and nil.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JSONSchemaProps</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/).</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourcevalidation-v1-apiextensions-k8s-io">CustomResourceValidation [apiextensions/v1]</a></LI>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>$ref</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>$schema</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>additionalItems</CODE><BR /><I><a href="#jsonschemapropsorbool-v1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>additionalProperties</CODE><BR /><I><a href="#jsonschemapropsorbool-v1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>allOf</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
+<TR><TD><CODE>anyOf</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
+<TR><TD><CODE>default</CODE><BR /><I><a href="#json-v1-apiextensions-k8s-io">JSON</a></I></TD><TD>default is a default value for undefined object fields. Defaulting is a beta feature under the CustomResourceDefaulting feature gate. Defaulting requires spec.preserveUnknownFields to be false.</TD></TR>
+<TR><TD><CODE>definitions</CODE><BR /><I>object</I></TD><TD></TD></TR>
+<TR><TD><CODE>dependencies</CODE><BR /><I>object</I></TD><TD></TD></TR>
+<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>enum</CODE><BR /><I><a href="#json-v1-apiextensions-k8s-io">JSON</a> array</I></TD><TD></TD></TR>
+<TR><TD><CODE>example</CODE><BR /><I><a href="#json-v1-apiextensions-k8s-io">JSON</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>exclusiveMaximum</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
+<TR><TD><CODE>exclusiveMinimum</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
+<TR><TD><CODE>externalDocs</CODE><BR /><I><a href="#externaldocumentation-v1-apiextensions-k8s-io">ExternalDocumentation</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>format</CODE><BR /><I>string</I></TD><TD>format is an OpenAPI v3 format string. Unknown formats are ignored. The following formats are validated:  - bsonobjectid: a bson object ID, i.e. a 24 characters hex string - uri: an URI as parsed by Golang net/url.ParseRequestURI - email: an email address as parsed by Golang net/mail.ParseAddress - hostname: a valid representation for an Internet host name, as defined by RFC 1034, section 3.1 [RFC1034]. - ipv4: an IPv4 IP as parsed by Golang net.ParseIP - ipv6: an IPv6 IP as parsed by Golang net.ParseIP - cidr: a CIDR as parsed by Golang net.ParseCIDR - mac: a MAC address as parsed by Golang net.ParseMAC - uuid: an UUID that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid3: an UUID3 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?3[0-9a-f]{3}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid4: an UUID4 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?4[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - uuid5: an UUID5 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?5[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - isbn: an ISBN10 or ISBN13 number string like &#34;0321751043&#34; or &#34;978-0321751041&#34; - isbn10: an ISBN10 number string like &#34;0321751043&#34; - isbn13: an ISBN13 number string like &#34;978-0321751041&#34; - creditcard: a credit card number defined by the regex ^(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14}|6(?:011|5[0-9][0-9])[0-9]{12}|3[47][0-9]{13}|3(?:0[0-5]|[68][0-9])[0-9]{11}|(?:2131|1800|35\d{3})\d{11})$ with any non digit characters mixed in - ssn: a U.S. social security number following the regex ^\d{3}[- ]?\d{2}[- ]?\d{4}$ - hexcolor: an hexadecimal color code like &#34;#FFFFFF: following the regex ^#?([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$ - rgbcolor: an RGB color code like rgb like &#34;rgb(255,255,2559&#34; - byte: base64 encoded binary data - password: any kind of string - date: a date string like &#34;2006-01-02&#34; as defined by full-date in RFC3339 - duration: a duration string like &#34;22 ns&#34; as parsed by Golang time.ParseDuration or compatible with Scala duration format - datetime: a date time string like &#34;2014-12-15T19:30:20.000Z&#34; as defined by date-time in RFC3339.</TD></TR>
+<TR><TD><CODE>id</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#jsonschemapropsorarray-v1-apiextensions-k8s-io">JSONSchemaPropsOrArray</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>maxItems</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>maxLength</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>maxProperties</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>maximum</CODE><BR /><I>number</I></TD><TD></TD></TR>
+<TR><TD><CODE>minItems</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>minLength</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>minProperties</CODE><BR /><I>integer</I></TD><TD></TD></TR>
+<TR><TD><CODE>minimum</CODE><BR /><I>number</I></TD><TD></TD></TR>
+<TR><TD><CODE>multipleOf</CODE><BR /><I>number</I></TD><TD></TD></TR>
+<TR><TD><CODE>not</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>nullable</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
+<TR><TD><CODE>oneOf</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
+<TR><TD><CODE>pattern</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>patternProperties</CODE><BR /><I>object</I></TD><TD></TD></TR>
+<TR><TD><CODE>properties</CODE><BR /><I>object</I></TD><TD></TD></TR>
+<TR><TD><CODE>required</CODE><BR /><I>string array</I></TD><TD></TD></TR>
+<TR><TD><CODE>title</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>uniqueItems</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
+<TR><TD><CODE>x-kubernetes-embedded-resource</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-embedded-resource defines that the value is an embedded Kubernetes runtime.Object, with TypeMeta and ObjectMeta. The type must be object. It is allowed to further restrict the embedded object. kind, apiVersion and metadata are validated automatically. x-kubernetes-preserve-unknown-fields is allowed to be true, but does not have to be if the object is fully specified (up to kind, apiVersion, metadata).</TD></TR>
+<TR><TD><CODE>x-kubernetes-int-or-string</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-int-or-string specifies that this value is either an integer or a string. If this is true, an empty type is allowed and type as child of anyOf is permitted if following one of the following patterns:  1) anyOf:    - type: integer    - type: string 2) allOf:    - anyOf:      - type: integer      - type: string    - ... zero or more</TD></TR>
+<TR><TD><CODE>x-kubernetes-list-map-keys</CODE><BR /><I>string array</I></TD><TD>x-kubernetes-list-map-keys annotates an array with the x-kubernetes-list-type `map` by specifying the keys used as the index of the map.  This tag MUST only be used on lists that have the &#34;x-kubernetes-list-type&#34; extension set to &#34;map&#34;. Also, the values specified for this attribute must be a scalar typed field of the child structure (no nesting is supported).  The properties specified must either be required or have a default value, to ensure those properties are present for all list items.</TD></TR>
+<TR><TD><CODE>x-kubernetes-list-type</CODE><BR /><I>string</I></TD><TD>x-kubernetes-list-type annotates an array to further describe its topology. This extension must only be used on lists and may have 3 possible values:  1) `atomic`: the list is treated as a single entity, like a scalar.      Atomic lists will be entirely replaced when updated. This extension      may be used on any type of list (struct, scalar, ...). 2) `set`:      Sets are lists that must not have multiple items with the same value. Each      value must be a scalar, an object with x-kubernetes-map-type `atomic` or an      array with x-kubernetes-list-type `atomic`. 3) `map`:      These lists are like maps in that their elements have a non-index key      used to identify them. Order is preserved upon merge. The map tag      must only be used on a list with elements of type object. Defaults to atomic for arrays.</TD></TR>
+<TR><TD><CODE>x-kubernetes-map-type</CODE><BR /><I>string</I></TD><TD>x-kubernetes-map-type annotates an object to further describe its topology. This extension must only be used when type is object and may have 2 possible values:  1) `granular`:      These maps are actual maps (key-value pairs) and each fields are independent      from each other (they can each be manipulated by separate actors). This is      the default behaviour for all maps. 2) `atomic`: the list is treated as a single entity, like a scalar.      Atomic maps will be entirely replaced when updated.</TD></TR>
+<TR><TD><CODE>x-kubernetes-preserve-unknown-fields</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-preserve-unknown-fields stops the API server decoding step from pruning fields which are not specified in the validation schema. This affects fields recursively, but switches back to normal pruning behaviour if nested properties or additionalProperties are specified in the schema. This can either be true or undefined. False is forbidden.</TD></TR>
+<TR><TD><CODE>x-kubernetes-validations</CODE><BR /><I><a href="#validationrule-v1-apiextensions-k8s-io">ValidationRule</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>rule</I></TD><TD>x-kubernetes-validations describes a list of validation rules written in the CEL expression language. This field is an alpha-level. Using this field requires the feature gate `CustomResourceValidationExpressions` to be enabled.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="jsonschemapropsorarray-v1-apiextensions-k8s-io">JSONSchemaPropsOrArray v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JSONSchemaPropsOrArray</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JSONSchemaPropsOrArray represents a value that can either be a JSONSchemaProps or an array of JSONSchemaProps. Mainly here for serialization purposes.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="jsonschemapropsorbool-v1-apiextensions-k8s-io">JSONSchemaPropsOrBool v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JSONSchemaPropsOrBool</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JSONSchemaPropsOrBool represents JSONSchemaProps or a boolean value. Defaults to true for the boolean property.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="jobcondition-v1-batch">JobCondition v1 batch</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JobCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JobCondition describes current state of a job.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jobstatus-v1-batch">JobStatus [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition was checked.</TD></TR>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transit from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of job condition, Complete or Failed.  Possible enum values:  - `&#34;Complete&#34;` means the job has completed its execution.  - `&#34;Failed&#34;` means the job has failed its execution.  - `&#34;Suspended&#34;` means the job has been suspended.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="jobtemplatespec-v1-batch">JobTemplateSpec v1 batch</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JobTemplateSpec</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>JobTemplateSpec describes the data a Job should have when created from a template</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#jobtemplatespec-v1beta1-batch">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjobspec-v1-batch">CronJobSpec [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="keytopath-v1-core">KeyToPath v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>KeyToPath</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Maps a string key to a path within a volume.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#configmapprojection-v1-core">ConfigMapProjection [core/v1]</a></LI>
+  <LI><a href="#configmapvolumesource-v1-core">ConfigMapVolumeSource [core/v1]</a></LI>
+  <LI><a href="#secretprojection-v1-core">SecretProjection [core/v1]</a></LI>
+  <LI><a href="#secretvolumesource-v1-core">SecretVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key to project.</TD></TR>
+<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="labelselector-v1-meta">LabelSelector v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LabelSelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule [rbac/v1]</a></LI>
+  <LI><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity [storage/v1beta1]</a></LI>
+  <LI><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity [storage/v1alpha1]</a></LI>
+  <LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
+  <LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
+  <LI><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
+  <LI><a href="#metricidentifier-v2-autoscaling">MetricIdentifier [autoscaling/v2]</a></LI>
+  <LI><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
+  <LI><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer [networking/v1]</a></LI>
+  <LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec [core/v1]</a></LI>
+  <LI><a href="#podaffinityterm-v1-core">PodAffinityTerm [core/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetspec-v1-policy">PodDisruptionBudgetSpec [policy/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec [policy/v1beta1]</a></LI>
+  <LI><a href="#podsmetricsource-v2beta1-autoscaling">PodsMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#replicasetspec-v1-apps">ReplicaSetSpec [apps/v1]</a></LI>
+  <LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
+  <LI><a href="#topologyspreadconstraint-v1-core">TopologySpreadConstraint [core/v1]</a></LI>
+  <LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#labelselectorrequirement-v1-meta">LabelSelectorRequirement</a> array</I></TD><TD>matchExpressions is a list of label selector requirements. The requirements are ANDed.</TD></TR>
+<TR><TD><CODE>matchLabels</CODE><BR /><I>object</I></TD><TD>matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="labelselectorrequirement-v1-meta">LabelSelectorRequirement v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LabelSelectorRequirement</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#labelselector-v1-meta">LabelSelector [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>key</I></TD><TD>key is the label key that the selector applies to.</TD></TR>
+<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.</TD></TR>
+<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="lifecycle-v1-core">Lifecycle v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Lifecycle</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Lifecycle describes actions that the management system should take in response to container lifecycle events. For the PostStart and PreStop lifecycle handlers, management of the container blocks until the action is complete, unless the container process fails, in which case the handler is aborted.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>postStart</CODE><BR /><I><a href="#lifecyclehandler-v1-core">LifecycleHandler</a></I></TD><TD>PostStart is called immediately after a container is created. If the handler fails, the container is terminated and restarted according to its restart policy. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks</TD></TR>
+<TR><TD><CODE>preStop</CODE><BR /><I><a href="#lifecyclehandler-v1-core">LifecycleHandler</a></I></TD><TD>PreStop is called immediately before a container is terminated due to an API request or management event such as liveness/startup probe failure, preemption, resource contention, etc. The handler is not called if the container crashes or exits. The Pod&#39;s termination grace period countdown begins before the PreStop hook is executed. Regardless of the outcome of the handler, the container will eventually terminate within the Pod&#39;s termination grace period (unless delayed by finalizers). Other management of the container blocks until the hook completes or until the termination grace period is reached. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="lifecyclehandler-v1-core">LifecycleHandler v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LifecycleHandler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LifecycleHandler defines a specific action that should be taken in a lifecycle hook. One and only one of the fields, except TCPSocket must be specified.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#lifecycle-v1-core">Lifecycle [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>exec</CODE><BR /><I><a href="#execaction-v1-core">ExecAction</a></I></TD><TD>Exec specifies the action to take.</TD></TR>
+<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies the http request to perform.</TD></TR>
+<TR><TD><CODE>tcpSocket</CODE><BR /><I><a href="#tcpsocketaction-v1-core">TCPSocketAction</a></I></TD><TD>Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept for the backward compatibility. There are no validation of this field and lifecycle hooks will fail in runtime when tcp handler is specified.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="limitrangeitem-v1-core">LimitRangeItem v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitRangeItem</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LimitRangeItem defines a min/max usage limit for any resource that matches on kind.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitrangespec-v1-core">LimitRangeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>default</CODE><BR /><I>object</I></TD><TD>Default resource requirement limit value by resource name if resource limit is omitted.</TD></TR>
+<TR><TD><CODE>defaultRequest</CODE><BR /><I>object</I></TD><TD>DefaultRequest is the default resource requirement request value by resource name if resource request is omitted.</TD></TR>
+<TR><TD><CODE>max</CODE><BR /><I>object</I></TD><TD>Max usage constraints on this kind by resource name.</TD></TR>
+<TR><TD><CODE>maxLimitRequestRatio</CODE><BR /><I>object</I></TD><TD>MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.</TD></TR>
+<TR><TD><CODE>min</CODE><BR /><I>object</I></TD><TD>Min usage constraints on this kind by resource name.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of resource that this limit applies to.  Possible enum values:  - `&#34;Container&#34;` Limit that applies to all containers in a namespace  - `&#34;PersistentVolumeClaim&#34;` Limit that applies to all persistent volume claims in a namespace  - `&#34;Pod&#34;` Limit that applies to all pods in a namespace</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="limitresponse-v1beta2-flowcontrol-apiserver-k8s-io">LimitResponse v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>LimitResponse</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LimitResponse defines how to handle requests that can not be executed right now.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#limitresponse-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>queuing</CODE><BR /><I><a href="#queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">QueuingConfiguration</a></I></TD><TD>`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `&#34;Queue&#34;`.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is &#34;Queue&#34; or &#34;Reject&#34;. &#34;Queue&#34; means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. &#34;Reject&#34; means that requests that can not be executed upon arrival are rejected. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>LimitedPriorityLevelConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:
+ * How are requests for this priority level limited?
+ * What should be done with requests that exceed the limit?</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationspec-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>assuredConcurrencyShares</CODE><BR /><I>integer</I></TD><TD>`assuredConcurrencyShares` (ACS) configures the execution limit, which is a limit on the number of requests of this priority level that may be exeucting at a given time.  ACS must be a positive number. The server&#39;s concurrency limit (SCL) is divided among the concurrency-controlled priority levels in proportion to their assured concurrency shares. This produces the assured concurrency value (ACV) --- the number of requests that may be executing at a time --- for each such priority level:              ACV(l) = ceil( SCL * ACS(l) / ( sum[priority levels k] ACS(k) ) )  bigger numbers of ACS mean more reserved concurrent requests (at the expense of every other PL). This field has a default value of 30.</TD></TR>
+<TR><TD><CODE>limitResponse</CODE><BR /><I><a href="#limitresponse-v1beta2-flowcontrol-apiserver-k8s-io">LimitResponse</a></I></TD><TD>`limitResponse` indicates what to do with requests that can not be executed right now</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="listmeta-v1-meta">ListMeta v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ListMeta</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList [apiregistration/v1]</a></LI>
+  <LI><a href="#csidriverlist-v1-storage-k8s-io">CSIDriverList [storage/v1]</a></LI>
+  <LI><a href="#csinodelist-v1-storage-k8s-io">CSINodeList [storage/v1]</a></LI>
+  <LI><a href="#csistoragecapacitylist-v1beta1-storage-k8s-io">CSIStorageCapacityList [storage/v1beta1]</a></LI>
+  <LI><a href="#csistoragecapacitylist-v1alpha1-storage-k8s-io">CSIStorageCapacityList [storage/v1alpha1]</a></LI>
+  <LI><a href="#certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1]</a></LI>
+  <LI><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1]</a></LI>
+  <LI><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1]</a></LI>
+  <LI><a href="#componentstatuslist-v1-core">ComponentStatusList [core/v1]</a></LI>
+  <LI><a href="#configmaplist-v1-core">ConfigMapList [core/v1]</a></LI>
+  <LI><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList [apps/v1]</a></LI>
+  <LI><a href="#cronjoblist-v1-batch">CronJobList [batch/v1]</a></LI>
+  <LI><a href="#cronjoblist-v1beta1-batch">CronJobList [batch/v1beta1]</a></LI>
+  <LI><a href="#customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/v1]</a></LI>
+  <LI><a href="#daemonsetlist-v1-apps">DaemonSetList [apps/v1]</a></LI>
+  <LI><a href="#deploymentlist-v1-apps">DeploymentList [apps/v1]</a></LI>
+  <LI><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList [discovery/v1]</a></LI>
+  <LI><a href="#endpointslicelist-v1beta1-discovery-k8s-io">EndpointSliceList [discovery/v1beta1]</a></LI>
+  <LI><a href="#endpointslist-v1-core">EndpointsList [core/v1]</a></LI>
+  <LI><a href="#eventlist-v1-core">EventList [core/v1]</a></LI>
+  <LI><a href="#eventlist-v1-events-k8s-io">EventList [events/v1]</a></LI>
+  <LI><a href="#eventlist-v1beta1-events-k8s-io">EventList [events/v1beta1]</a></LI>
+  <LI><a href="#flowschemalist-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#horizontalpodautoscalerlist-v2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
+  <LI><a href="#horizontalpodautoscalerlist-v2beta2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#ingressclasslist-v1-networking-k8s-io">IngressClassList [networking/v1]</a></LI>
+  <LI><a href="#ingresslist-v1-networking-k8s-io">IngressList [networking/v1]</a></LI>
+  <LI><a href="#joblist-v1-batch">JobList [batch/v1]</a></LI>
+  <LI><a href="#leaselist-v1-coordination-k8s-io">LeaseList [coordination/v1]</a></LI>
+  <LI><a href="#limitrangelist-v1-core">LimitRangeList [core/v1]</a></LI>
+  <LI><a href="#mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/v1]</a></LI>
+  <LI><a href="#namespacelist-v1-core">NamespaceList [core/v1]</a></LI>
+  <LI><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList [networking/v1]</a></LI>
+  <LI><a href="#nodelist-v1-core">NodeList [core/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList [core/v1]</a></LI>
+  <LI><a href="#persistentvolumelist-v1-core">PersistentVolumeList [core/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList [policy/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList [policy/v1beta1]</a></LI>
+  <LI><a href="#podlist-v1-core">PodList [core/v1]</a></LI>
+  <LI><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList [policy/v1beta1]</a></LI>
+  <LI><a href="#podtemplatelist-v1-core">PodTemplateList [core/v1]</a></LI>
+  <LI><a href="#priorityclasslist-v1-scheduling-k8s-io">PriorityClassList [scheduling/v1]</a></LI>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#replicasetlist-v1-apps">ReplicaSetList [apps/v1]</a></LI>
+  <LI><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList [core/v1]</a></LI>
+  <LI><a href="#resourcequotalist-v1-core">ResourceQuotaList [core/v1]</a></LI>
+  <LI><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1]</a></LI>
+  <LI><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList [rbac/v1]</a></LI>
+  <LI><a href="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList [node/v1]</a></LI>
+  <LI><a href="#runtimeclasslist-v1beta1-node-k8s-io">RuntimeClassList [node/v1beta1]</a></LI>
+  <LI><a href="#runtimeclasslist-v1alpha1-node-k8s-io">RuntimeClassList [node/v1alpha1]</a></LI>
+  <LI><a href="#secretlist-v1-core">SecretList [core/v1]</a></LI>
+  <LI><a href="#serviceaccountlist-v1-core">ServiceAccountList [core/v1]</a></LI>
+  <LI><a href="#servicelist-v1-core">ServiceList [core/v1]</a></LI>
+  <LI><a href="#statefulsetlist-v1-apps">StatefulSetList [apps/v1]</a></LI>
+  <LI><a href="#status-v1-meta">Status [meta/v1]</a></LI>
+  <LI><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList [storage/v1]</a></LI>
+  <LI><a href="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList [apiserverinternal/v1alpha1]</a></LI>
+  <LI><a href="#validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/v1]</a></LI>
+  <LI><a href="#volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>continue</CODE><BR /><I>string</I></TD><TD>continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a consistent list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response, unless you have received this token from an error message.</TD></TR>
+<TR><TD><CODE>remainingItemCount</CODE><BR /><I>integer</I></TD><TD>remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>String that identifies the server&#39;s internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency</TD></TR>
+<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>selfLink is a URL representing this object. Populated by the system. Read-only.  DEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="loadbalanceringress-v1-core">LoadBalancerIngress v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LoadBalancerIngress</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LoadBalancerIngress represents the status of a load-balancer ingress point: traffic intended for the service should be sent to an ingress point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers)</TD></TR>
+<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#portstatus-v1-core">PortStatus</a> array</I></TD><TD>Ports is a list of records of service ports If used, every port defined in the service should have an entry in it</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="loadbalancerstatus-v1-core">LoadBalancerStatus v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LoadBalancerStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LoadBalancerStatus represents the status of a load-balancer.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressstatus-v1-networking-k8s-io">IngressStatus [networking/v1]</a></LI>
+  <LI><a href="#servicestatus-v1-core">ServiceStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ingress</CODE><BR /><I><a href="#loadbalanceringress-v1-core">LoadBalancerIngress</a> array</I></TD><TD>Ingress is a list containing ingress points for the load-balancer. Traffic intended for the service should be sent to these ingress points.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="localobjectreference-v1-core">LocalObjectReference v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csivolumesource-v1-core">CSIVolumeSource [core/v1]</a></LI>
+  <LI><a href="#cephfsvolumesource-v1-core">CephFSVolumeSource [core/v1]</a></LI>
+  <LI><a href="#cindervolumesource-v1-core">CinderVolumeSource [core/v1]</a></LI>
+  <LI><a href="#flexvolumesource-v1-core">FlexVolumeSource [core/v1]</a></LI>
+  <LI><a href="#iscsivolumesource-v1-core">ISCSIVolumeSource [core/v1]</a></LI>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+  <LI><a href="#rbdvolumesource-v1-core">RBDVolumeSource [core/v1]</a></LI>
+  <LI><a href="#scaleiovolumesource-v1-core">ScaleIOVolumeSource [core/v1]</a></LI>
+  <LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
+  <LI><a href="#storageosvolumesource-v1-core">StorageOSVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="localvolumesource-v1-core">LocalVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Local represents directly-attached storage with node affinity (Beta feature)</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. It applies only when the Path is a block device. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default value is to auto-select a filesystem if unspecified.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>The full path to the volume on the node. It can be either a directory or block device (disk, partition, ...).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="managedfieldsentry-v1-meta">ManagedFieldsEntry v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ManagedFieldsEntry</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>APIVersion defines the version of this resource that this field set applies to. The format is &#34;group/version&#34; just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.</TD></TR>
+<TR><TD><CODE>fieldsType</CODE><BR /><I>string</I></TD><TD>FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: &#34;FieldsV1&#34;</TD></TR>
+<TR><TD><CODE>fieldsV1</CODE><BR /><I><a href="#fieldsv1-v1-meta">FieldsV1</a></I></TD><TD>FieldsV1 holds the first JSON version format as described in the &#34;FieldsV1&#34; type.</TD></TR>
+<TR><TD><CODE>manager</CODE><BR /><I>string</I></TD><TD>Manager is an identifier of the workflow managing these fields.</TD></TR>
+<TR><TD><CODE>operation</CODE><BR /><I>string</I></TD><TD>Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are &#39;Apply&#39; and &#39;Update&#39;.</TD></TR>
+<TR><TD><CODE>subresource</CODE><BR /><I>string</I></TD><TD>Subresource is the name of the subresource used to update that object, or empty string if the object was updated through the main resource. The value of this field is used to distinguish between managers, even if they share the same name. For example, a status update will be distinct from a regular update using the same manager name. Note that the APIVersion field is not related to the Subresource field and it always corresponds to the version of the main resource.</TD></TR>
+<TR><TD><CODE>time</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time is timestamp of when these fields were set. It should always be empty if Operation is &#39;Apply&#39;</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="metricidentifier-v2-autoscaling">MetricIdentifier v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>MetricIdentifier</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MetricIdentifier defines the name and optionally selector for a metric</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricidentifier-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#externalmetricsource-v2-autoscaling">ExternalMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#externalmetricstatus-v2-autoscaling">ExternalMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#podsmetricsource-v2-autoscaling">PodsMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#podsmetricstatus-v2-autoscaling">PodsMetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the given metric</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="metricspec-v2-autoscaling">MetricSpec v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>MetricSpec</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricspec-v2beta2-autoscaling">v2beta2</a>
+<a href="#metricspec-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricsource-v2-autoscaling">ContainerResourceMetricSource</a></I></TD><TD>containerResource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricsource-v2-autoscaling">ExternalMetricSource</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricsource-v2-autoscaling">PodsMetricSource</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricsource-v2-autoscaling">ResourceMetricSource</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It should be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each mapping to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="metricstatus-v2-autoscaling">MetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>MetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MetricStatus describes the last-read state of a single metric.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#metricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricstatus-v2-autoscaling">ContainerResourceMetricStatus</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricstatus-v2-autoscaling">ExternalMetricStatus</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricstatus-v2-autoscaling">PodsMetricStatus</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricstatus-v2-autoscaling">ResourceMetricStatus</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It will be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each corresponds to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="metrictarget-v2-autoscaling">MetricTarget v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>MetricTarget</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MetricTarget defines the target value, average value, or average utilization of a specific metric</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metrictarget-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerresourcemetricsource-v2-autoscaling">ContainerResourceMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#externalmetricsource-v2-autoscaling">ExternalMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#podsmetricsource-v2-autoscaling">PodsMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#resourcemetricsource-v2-autoscaling">ResourceMetricSource [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageUtilization</CODE><BR /><I>integer</I></TD><TD>averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. Currently only valid for Resource metric source type</TD></TR>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type represents whether the metric type is Utilization, Value, or AverageValue</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the target value of the metric (as a quantity).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="metricvaluestatus-v2-autoscaling">MetricValueStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>MetricValueStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MetricValueStatus holds the current value for a metric</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricvaluestatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerresourcemetricstatus-v2-autoscaling">ContainerResourceMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#externalmetricstatus-v2-autoscaling">ExternalMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#podsmetricstatus-v2-autoscaling">PodsMetricStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#resourcemetricstatus-v2-autoscaling">ResourceMetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageUtilization</CODE><BR /><I>integer</I></TD><TD>currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.</TD></TR>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the current value of the metric (as a quantity).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="microtime-v1-meta">MicroTime v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>MicroTime</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MicroTime is version of Time with microsecond level precision.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+  <LI><a href="#eventseries-v1-core">EventSeries [core/v1]</a></LI>
+  <LI><a href="#eventseries-v1-events-k8s-io">EventSeries [events/v1]</a></LI>
+  <LI><a href="#eventseries-v1beta1-events-k8s-io">EventSeries [events/v1beta1]</a></LI>
+  <LI><a href="#leasespec-v1-coordination-k8s-io">LeaseSpec [coordination/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook v1 admissionregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>MutatingWebhook</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MutatingWebhook describes an admission webhook and the resources and operations it applies to.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionReviewVersions</CODE><BR /><I>string array</I></TD><TD>AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.</TD></TR>
+<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1-admissionregistration-k8s-io">WebhookClientConfig</a></I></TD><TD>ClientConfig defines how to communicate with the hook. Required</TD></TR>
+<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
+<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;rules&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;.  - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.  - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.  Defaults to &#34;Equivalent&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where &#34;imagepolicy&#34; is the name of the webhook, and kubernetes.io is the name of the organization. Required.</TD></TR>
+<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.  For example, to run the webhook on any objects whose namespace is not associated with &#34;runlevel&#34; of &#34;0&#34; or &#34;1&#34;;  you will set the selector as follows: &#34;namespaceSelector&#34;: {   &#34;matchExpressions&#34;: [     {       &#34;key&#34;: &#34;runlevel&#34;,       &#34;operator&#34;: &#34;NotIn&#34;,       &#34;values&#34;: [         &#34;0&#34;,         &#34;1&#34;       ]     }   ] }  If instead you want to only run the webhook on any objects whose namespace is associated with the &#34;environment&#34; of &#34;prod&#34; or &#34;staging&#34;; you will set the selector as follows: &#34;namespaceSelector&#34;: {   &#34;matchExpressions&#34;: [     {       &#34;key&#34;: &#34;environment&#34;,       &#34;operator&#34;: &#34;In&#34;,       &#34;values&#34;: [         &#34;prod&#34;,         &#34;staging&#34;       ]     }   ] }  See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors.  Default to the empty LabelSelector, which matches everything.</TD></TR>
+<TR><TD><CODE>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
+<TR><TD><CODE>reinvocationPolicy</CODE><BR /><I>string</I></TD><TD>reinvocationPolicy indicates whether this webhook should be called multiple times as part of a single admission evaluation. Allowed values are &#34;Never&#34; and &#34;IfNeeded&#34;.  Never: the webhook will not be called more than once in a single admission evaluation.  IfNeeded: the webhook will be called at least one additional time as part of the admission evaluation if the object being admitted is modified by other admission plugins after the initial webhook call. Webhooks that specify this option *must* be idempotent, able to process objects they previously admitted. Note: * the number of additional invocations is not guaranteed to be exactly one. * if additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again. * webhooks that use this option may be reordered to minimize the number of additional invocations. * to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead.  Defaults to &#34;Never&#34;.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#rulewithoperations-v1-admissionregistration-k8s-io">RuleWithOperations</a> array</I></TD><TD>Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.</TD></TR>
+<TR><TD><CODE>sideEffects</CODE><BR /><I>string</I></TD><TD>SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nfsvolumesource-v1-core">NFSVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NFSVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
+<TR><TD><CODE>server</CODE><BR /><I>string</I></TD><TD>Server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="namespacecondition-v1-core">NamespaceCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NamespaceCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NamespaceCondition contains details about state of namespace.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#namespacestatus-v1-core">NamespaceStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of namespace controller condition.  Possible enum values:  - `&#34;NamespaceContentRemaining&#34;` contains information about resources remaining in a namespace.  - `&#34;NamespaceDeletionContentFailure&#34;` contains information about namespace deleter errors during deletion of resources.  - `&#34;NamespaceDeletionDiscoveryFailure&#34;` contains information about namespace deleter errors during resource discovery.  - `&#34;NamespaceDeletionGroupVersionParsingFailure&#34;` contains information about namespace deleter errors parsing GV for legacy types.  - `&#34;NamespaceFinalizersRemaining&#34;` contains information about which finalizers are on resources remaining in a namespace.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyEgressRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec&#39;s podSelector. The traffic must match both ports and to. This type is beta-level in 1.8</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort</a> array</I></TD><TD>List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
+<TR><TD><CODE>to</CODE><BR /><I><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer</a> array</I></TD><TD>List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyIngressRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec&#39;s podSelector. The traffic must match both ports and from.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>from</CODE><BR /><I><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer</a> array</I></TD><TD>List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the from list.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort</a> array</I></TD><TD>List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyPeer</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule [networking/v1]</a></LI>
+  <LI><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ipBlock</CODE><BR /><I><a href="#ipblock-v1-networking-k8s-io">IPBlock</a></I></TD><TD>IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.</TD></TR>
+<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.  If PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.</TD></TR>
+<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.  If NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy&#39;s own Namespace.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NetworkPolicyPort describes a port to allow traffic on</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule [networking/v1]</a></LI>
+  <LI><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>endPort</CODE><BR /><I>integer</I></TD><TD>If set, indicates that the range of ports from port to endPort, inclusive, should be allowed by the policy. This field cannot be defined if the port field is not defined or if the port field is defined as a named (string) port. The endPort must be equal or greater than port. This feature is in Beta state and is enabled by default. It can be disabled using the Feature Gate &#34;NetworkPolicyEndPort&#34;.</TD></TR>
+<TR><TD><CODE>port</CODE></TD><TD>The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeaddress-v1-core">NodeAddress v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeAddress</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeAddress contains information for the node&#39;s address.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>address</CODE><BR /><I>string</I></TD><TD>The node address.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Node address type, one of Hostname, ExternalIP or InternalIP.  Possible enum values:  - `&#34;ExternalDNS&#34;` identifies a DNS name which resolves to an IP address which has the characteristics of a NodeExternalIP. The IP it resolves to may or may not be a listed NodeExternalIP address.  - `&#34;ExternalIP&#34;` identifies an IP address which is, in some way, intended to be more usable from outside the cluster then an internal IP, though no specific semantics are defined. It may be a globally routable IP, though it is not required to be. External IPs may be assigned directly to an interface on the node, like a NodeInternalIP, or alternatively, packets sent to the external IP may be NAT&#39;ed to an internal node IP rather than being delivered directly (making the IP less efficient for node-to-node traffic than a NodeInternalIP).  - `&#34;Hostname&#34;` identifies a name of the node. Although every node can be assumed to have a NodeAddress of this type, its exact syntax and semantics are not defined, and are not consistent between different clusters.  - `&#34;InternalDNS&#34;` identifies a DNS name which resolves to an IP address which has the characteristics of a NodeInternalIP. The IP it resolves to may or may not be a listed NodeInternalIP address.  - `&#34;InternalIP&#34;` identifies an IP address which is assigned to one of the node&#39;s network interfaces. Every node should have at least one address of this type. An internal IP is normally expected to be reachable from every other node, but may not be visible to hosts outside the cluster. By default it is assumed that kube-apiserver can reach node internal IPs, though it is possible to configure clusters where this is not the case. NodeInternalIP is the default type of node IP, and does not necessarily imply that the IP is ONLY reachable internally. If a node has multiple internal IPs, no specific semantics are assigned to the additional IPs.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeaffinity-v1-core">NodeAffinity v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeAffinity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Node affinity is a group of node affinity scheduling rules.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#preferredschedulingterm-v1-core">PreferredSchedulingTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.</TD></TR>
+<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodecondition-v1-core">NodeCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeCondition contains condition information for a node.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastHeartbeatTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we got an update on a given condition.</TD></TR>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transit from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of node condition.  Possible enum values:  - `&#34;DiskPressure&#34;` means the kubelet is under pressure due to insufficient available disk.  - `&#34;MemoryPressure&#34;` means the kubelet is under pressure due to insufficient available memory.  - `&#34;NetworkUnavailable&#34;` means that network for the node is not correctly configured.  - `&#34;PIDPressure&#34;` means the kubelet is under pressure due to insufficient available PID.  - `&#34;Ready&#34;` means kubelet is healthy and ready to accept pods.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeconfigsource-v1-core">NodeConfigSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeConfigSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil. This API is deprecated since 1.22</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeconfigstatus-v1-core">NodeConfigStatus [core/v1]</a></LI>
+  <LI><a href="#nodespec-v1-core">NodeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapnodeconfigsource-v1-core">ConfigMapNodeConfigSource</a></I></TD><TD>ConfigMap is a reference to a Node&#39;s ConfigMap</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeconfigstatus-v1-core">NodeConfigStatus v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeConfigStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>active</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>Active reports the checkpointed config the node is actively using. Active will represent either the current version of the Assigned config, or the current LastKnownGood config, depending on whether attempting to use the Assigned config results in an error.</TD></TR>
+<TR><TD><CODE>assigned</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>Assigned reports the checkpointed config the node will try to use. When Node.Spec.ConfigSource is updated, the node checkpoints the associated config payload to local disk, along with a record indicating intended config. The node refers to this record to choose its config checkpoint, and reports this record in Assigned. Assigned only updates in the status after the record has been checkpointed to disk. When the Kubelet is restarted, it tries to make the Assigned config the Active config by loading and validating the checkpointed payload identified by Assigned.</TD></TR>
+<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error describes any problems reconciling the Spec.ConfigSource to the Active config. Errors may occur, for example, attempting to checkpoint Spec.ConfigSource to the local Assigned record, attempting to checkpoint the payload associated with Spec.ConfigSource, attempting to load or validate the Assigned config, etc. Errors may occur at different points while syncing config. Earlier errors (e.g. download or checkpointing errors) will not result in a rollback to LastKnownGood, and may resolve across Kubelet retries. Later errors (e.g. loading or validating a checkpointed config) will result in a rollback to LastKnownGood. In the latter case, it is usually possible to resolve the error by fixing the config assigned in Spec.ConfigSource. You can find additional information for debugging by searching the error message in the Kubelet log. Error is a human-readable description of the error state; machines can check whether or not Error is empty, but should not rely on the stability of the Error text across Kubelet versions.</TD></TR>
+<TR><TD><CODE>lastKnownGood</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>LastKnownGood reports the checkpointed config the node will fall back to when it encounters an error attempting to use the Assigned config. The Assigned config becomes the LastKnownGood config when the node determines that the Assigned config is stable and correct. This is currently implemented as a 10-minute soak period starting when the local record of Assigned config is updated. If the Assigned config is Active at the end of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil, because the local default config is always assumed good. You should not make assumptions about the node&#39;s method of determining config stability and correctness, as this may change or become configurable in the future.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodedaemonendpoints-v1-core">NodeDaemonEndpoints v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeDaemonEndpoints</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeDaemonEndpoints lists ports opened by daemons running on the Node.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>kubeletEndpoint</CODE><BR /><I><a href="#daemonendpoint-v1-core">DaemonEndpoint</a></I></TD><TD>Endpoint on which Kubelet is listening.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeselector-v1-core">NodeSelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
+  <LI><a href="#volumenodeaffinity-v1-core">VolumeNodeAffinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nodeSelectorTerms</CODE><BR /><I><a href="#nodeselectorterm-v1-core">NodeSelectorTerm</a> array</I></TD><TD>Required. A list of node selector terms. The terms are ORed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeselectorrequirement-v1-core">NodeSelectorRequirement v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelectorRequirement</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeselectorterm-v1-core">NodeSelectorTerm [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The label key that the selector applies to.</TD></TR>
+<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.  Possible enum values:  - `&#34;DoesNotExist&#34;`  - `&#34;Exists&#34;`  - `&#34;Gt&#34;`  - `&#34;In&#34;`  - `&#34;Lt&#34;`  - `&#34;NotIn&#34;`</TD></TR>
+<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodeselectorterm-v1-core">NodeSelectorTerm v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelectorTerm</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeselector-v1-core">NodeSelector [core/v1]</a></LI>
+  <LI><a href="#preferredschedulingterm-v1-core">PreferredSchedulingTerm [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#nodeselectorrequirement-v1-core">NodeSelectorRequirement</a> array</I></TD><TD>A list of node selector requirements by node&#39;s labels.</TD></TR>
+<TR><TD><CODE>matchFields</CODE><BR /><I><a href="#nodeselectorrequirement-v1-core">NodeSelectorRequirement</a> array</I></TD><TD>A list of node selector requirements by node&#39;s fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nodesysteminfo-v1-core">NodeSystemInfo v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSystemInfo</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NodeSystemInfo is a set of ids/uuids to uniquely identify the node.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>architecture</CODE><BR /><I>string</I></TD><TD>The Architecture reported by the node</TD></TR>
+<TR><TD><CODE>bootID</CODE><BR /><I>string</I></TD><TD>Boot ID reported by the node.</TD></TR>
+<TR><TD><CODE>containerRuntimeVersion</CODE><BR /><I>string</I></TD><TD>ContainerRuntime Version reported by the node through runtime remote API (e.g. docker://1.5.0).</TD></TR>
+<TR><TD><CODE>kernelVersion</CODE><BR /><I>string</I></TD><TD>Kernel Version reported by the node from &#39;uname -r&#39; (e.g. 3.16.0-0.bpo.4-amd64).</TD></TR>
+<TR><TD><CODE>kubeProxyVersion</CODE><BR /><I>string</I></TD><TD>KubeProxy Version reported by the node.</TD></TR>
+<TR><TD><CODE>kubeletVersion</CODE><BR /><I>string</I></TD><TD>Kubelet Version reported by the node.</TD></TR>
+<TR><TD><CODE>machineID</CODE><BR /><I>string</I></TD><TD>MachineID reported by the node. For unique machine identification in the cluster this field is preferred. Learn more from man(5) machine-id: http://man7.org/linux/man-pages/man5/machine-id.5.html</TD></TR>
+<TR><TD><CODE>operatingSystem</CODE><BR /><I>string</I></TD><TD>The Operating System reported by the node</TD></TR>
+<TR><TD><CODE>osImage</CODE><BR /><I>string</I></TD><TD>OS Image reported by the node from /etc/os-release (e.g. Debian GNU/Linux 7 (wheezy)).</TD></TR>
+<TR><TD><CODE>systemUUID</CODE><BR /><I>string</I></TD><TD>SystemUUID reported by the node. For unique machine identification MachineID is preferred. This field is specific to Red Hat hosts https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/rhsm/uuid</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes v1 authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NonResourceAttributes</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1]</a></LI>
+  <LI><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the URL path of the request</TD></TR>
+<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is the standard HTTP verb</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>NonResourcePolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NonResourcePolicyRule is a predicate that matches non-resource requests according to their verb and the target non-resource URL. A NonResourcePolicyRule matches a request if and only if both (a) at least one member of verbs matches the request and (b) at least one member of nonResourceURLs matches the request.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>`nonResourceURLs` is a set of url prefixes that a user should have access to and may not be empty. For example:   - &#34;/healthz&#34; is legal   - &#34;/hea*&#34; is illegal   - &#34;/hea&#34; is legal but matches nothing   - &#34;/hea/*&#34; also matches nothing   - &#34;/healthz/*&#34; matches all per-component health checks. &#34;*&#34; matches all non-resource urls. if it is present, it must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs. If it is present, it must be the only entry. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="nonresourcerule-v1-authorization-k8s-io">NonResourceRule v1 authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NonResourceRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NonResourceRule holds information that describes a rule for the non-resource</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options.  &#34;*&#34; means all.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="objectfieldselector-v1-core">ObjectFieldSelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectFieldSelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ObjectFieldSelector selects an APIVersioned field of an object.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile [core/v1]</a></LI>
+  <LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.</TD></TR>
+<TR><TD><CODE>fieldPath</CODE><BR /><I>string</I></TD><TD>Path of the field to select in the specified API version.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="objectmeta-v1-meta">ObjectMeta v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectMeta</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
+  <LI><a href="#binding-v1-core">Binding [core/v1]</a></LI>
+  <LI><a href="#csidriver-v1-storage-k8s-io">CSIDriver [storage/v1]</a></LI>
+  <LI><a href="#csinode-v1-storage-k8s-io">CSINode [storage/v1]</a></LI>
+  <LI><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity [storage/v1beta1]</a></LI>
+  <LI><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity [storage/v1alpha1]</a></LI>
+  <LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
+  <LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
+  <LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
+  <LI><a href="#componentstatus-v1-core">ComponentStatus [core/v1]</a></LI>
+  <LI><a href="#configmap-v1-core">ConfigMap [core/v1]</a></LI>
+  <LI><a href="#controllerrevision-v1-apps">ControllerRevision [apps/v1]</a></LI>
+  <LI><a href="#cronjob-v1-batch">CronJob [batch/v1]</a></LI>
+  <LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
+  <LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</a></LI>
+  <LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
+  <LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
+  <LI><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</a></LI>
+  <LI><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice [discovery/v1beta1]</a></LI>
+  <LI><a href="#endpoints-v1-core">Endpoints [core/v1]</a></LI>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+  <LI><a href="#eviction-v1-policy">Eviction [policy/v1]</a></LI>
+  <LI><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
+  <LI><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/v1]</a></LI>
+  <LI><a href="#ingressclass-v1-networking-k8s-io">IngressClass [networking/v1]</a></LI>
+  <LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
+  <LI><a href="#jobtemplatespec-v1-batch">JobTemplateSpec [batch/v1]</a></LI>
+  <LI><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec [batch/v1beta1]</a></LI>
+  <LI><a href="#lease-v1-coordination-k8s-io">Lease [coordination/v1]</a></LI>
+  <LI><a href="#limitrange-v1-core">LimitRange [core/v1]</a></LI>
+  <LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1]</a></LI>
+  <LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
+  <LI><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy [networking/v1]</a></LI>
+  <LI><a href="#node-v1-core">Node [core/v1]</a></LI>
+  <LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate [core/v1]</a></LI>
+  <LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
+  <LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/v1]</a></LI>
+  <LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
+  <LI><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy [policy/v1beta1]</a></LI>
+  <LI><a href="#podtemplate-v1-core">PodTemplate [core/v1]</a></LI>
+  <LI><a href="#podtemplatespec-v1-core">PodTemplateSpec [core/v1]</a></LI>
+  <LI><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass [scheduling/v1]</a></LI>
+  <LI><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
+  <LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
+  <LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
+  <LI><a href="#role-v1-rbac-authorization-k8s-io">Role [rbac/v1]</a></LI>
+  <LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
+  <LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
+  <LI><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass [node/v1beta1]</a></LI>
+  <LI><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass [node/v1alpha1]</a></LI>
+  <LI><a href="#scale-v1-autoscaling">Scale [autoscaling/v1]</a></LI>
+  <LI><a href="#secret-v1-core">Secret [core/v1]</a></LI>
+  <LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
+  <LI><a href="#service-v1-core">Service [core/v1]</a></LI>
+  <LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
+  <LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
+  <LI><a href="#storageclass-v1-storage-k8s-io">StorageClass [storage/v1]</a></LI>
+  <LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
+  <LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
+  <LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
+  <LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
+  <LI><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1]</a></LI>
+  <LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>annotations</CODE><BR /><I>object</I></TD><TD>Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations</TD></TR>
+<TR><TD><CODE>clusterName</CODE><BR /><I>string</I></TD><TD>The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.</TD></TR>
+<TR><TD><CODE>creationTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.  Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>deletionGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.</TD></TR>
+<TR><TD><CODE>deletionTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.  Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>finalizers</CODE><BR /><I>string array</I><BR /><B>patch strategy</B>: <I>merge</I></TD><TD>Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order.  Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.</TD></TR>
+<TR><TD><CODE>generateName</CODE><BR /><I>string</I></TD><TD>GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.  If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).  Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency</TD></TR>
+<TR><TD><CODE>generation</CODE><BR /><I>integer</I></TD><TD>A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.</TD></TR>
+<TR><TD><CODE>labels</CODE><BR /><I>object</I></TD><TD>Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels</TD></TR>
+<TR><TD><CODE>managedFields</CODE><BR /><I><a href="#managedfieldsentry-v1-meta">ManagedFieldsEntry</a> array</I></TD><TD>ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn&#39;t need to set or understand this field. A workflow can be the user&#39;s name, a controller&#39;s name, or the name of a specific apply path like &#34;ci-cd&#34;. The set of fields is always in the version that the workflow used when modifying the object.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the &#34;default&#34; namespace, but &#34;default&#34; is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.  Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces</TD></TR>
+<TR><TD><CODE>ownerReferences</CODE><BR /><I><a href="#ownerreference-v1-meta">OwnerReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>uid</I></TD><TD>List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.  Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency</TD></TR>
+<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>SelfLink is a URL representing this object. Populated by the system. Read-only.  DEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.  Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="objectmetricsource-v2-autoscaling">ObjectMetricSource v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ObjectMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricsource-v2beta2-autoscaling">v2beta2</a>
+<a href="#objectmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2-autoscaling">CrossVersionObjectReference</a></I></TD><TD>describedObject specifies the descriptions of a object,such as kind,name apiVersion</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="objectmetricstatus-v2-autoscaling">ObjectMetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ObjectMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#objectmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2-autoscaling">CrossVersionObjectReference</a></I></TD><TD>DescribedObject specifies the descriptions of a object,such as kind,name apiVersion</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="objectreference-v1-core">ObjectReference v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ObjectReference contains enough information to let you inspect or modify the referred object.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#binding-v1-core">Binding [core/v1]</a></LI>
+  <LI><a href="#cronjobstatus-v1-batch">CronJobStatus [batch/v1]</a></LI>
+  <LI><a href="#cronjobstatus-v1beta1-batch">CronJobStatus [batch/v1beta1]</a></LI>
+  <LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</a></LI>
+  <LI><a href="#endpoint-v1beta1-discovery-k8s-io">Endpoint [discovery/v1beta1]</a></LI>
+  <LI><a href="#endpointaddress-v1-core">EndpointAddress [core/v1]</a></LI>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
+  <LI><a href="#storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent.</TD></TR>
+<TR><TD><CODE>fieldPath</CODE><BR /><I>string</I></TD><TD>If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: &#34;spec.containers{name}&#34; (where &#34;name&#34; refers to the name of the container that triggered the event) or if no container name is specified &#34;spec.containers[2]&#34; (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="overhead-v1-node-k8s-io">Overhead v1 node.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Overhead</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Overhead structure represents the resource overhead associated with running a pod.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#overhead-v1beta1-node-k8s-io">v1beta1</a>
+<a href="#overhead-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>podFixed</CODE><BR /><I>object</I></TD><TD>PodFixed represents the fixed resource overhead associated with running a pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ownerreference-v1-meta">OwnerReference v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>OwnerReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent.</TD></TR>
+<TR><TD><CODE>blockOwnerDeletion</CODE><BR /><I>boolean</I></TD><TD>If true, AND if the owner has the &#34;foregroundDeletion&#34; finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs &#34;delete&#34; permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.</TD></TR>
+<TR><TD><CODE>controller</CODE><BR /><I>boolean</I></TD><TD>If true, this reference points to the managing controller.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-v1-meta">Patch v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Patch</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaimCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PersistentVolumeClaimCondition contails details about state of pvc</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we probed the condition.</TD></TR>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, this should be a short, machine understandable string that gives the reason for condition&#39;s last transition. If it reports &#34;ResizeStarted&#34; that means the underlying persistent volume is being resized.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD></TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>   Possible enum values:  - `&#34;FileSystemResizePending&#34;` - controller resize is finished and a file system resize is pending on node  - `&#34;Resizing&#34;` - a user trigger resize of pvc has been started</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaimTemplate</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PersistentVolumeClaimTemplate is used to produce PersistentVolumeClaim objects as part of an EphemeralVolumeSource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ephemeralvolumesource-v1-core">EphemeralVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>May contain labels and annotations that will be copied into the PVC when creating it. No other fields are allowed and will be rejected during validation.</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec</a></I></TD><TD>The specification for the PersistentVolumeClaim. The entire content is copied unchanged into the PVC that gets created from this template. The same fields as in a PersistentVolumeClaim are also valid here.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="persistentvolumeclaimvolumesource-v1-core">PersistentVolumeClaimVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaimVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PersistentVolumeClaimVolumeSource references the user&#39;s PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>claimName</CODE><BR /><I>string</I></TD><TD>ClaimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Will force the ReadOnly setting in VolumeMounts. Default false.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PhotonPersistentDiskVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Photon Controller persistent disk resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>pdID</CODE><BR /><I>string</I></TD><TD>ID that identifies Photon Controller persistent disk</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podaffinity-v1-core">PodAffinity v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAffinity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Pod affinity is a group of inter pod affinity scheduling rules.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.</TD></TR>
+<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a> array</I></TD><TD>If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podaffinityterm-v1-core">PodAffinityTerm v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAffinityTerm</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key &lt;topologyKey&gt; matches that of any node on which a pod of the set of pods is running</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podaffinity-v1-core">PodAffinity [core/v1]</a></LI>
+  <LI><a href="#podantiaffinity-v1-core">PodAntiAffinity [core/v1]</a></LI>
+  <LI><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>labelSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over a set of resources, in this case pods.</TD></TR>
+<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means &#34;this pod&#39;s namespace&#34;. An empty selector ({}) matches all namespaces. This field is beta-level and is only honored when PodAffinityNamespaceSelector feature is enabled.</TD></TR>
+<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means &#34;this pod&#39;s namespace&#34;</TD></TR>
+<TR><TD><CODE>topologyKey</CODE><BR /><I>string</I></TD><TD>This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podantiaffinity-v1-core">PodAntiAffinity v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAntiAffinity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Pod anti affinity is a group of inter pod anti affinity scheduling rules.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.</TD></TR>
+<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a> array</I></TD><TD>If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podcondition-v1-core">PodCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodCondition contains details for the current condition of this pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we probed the condition.</TD></TR>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions  Possible enum values:  - `&#34;ContainersReady&#34;` indicates whether all containers in the pod are ready.  - `&#34;Initialized&#34;` means that all init containers in the pod have started successfully.  - `&#34;PodScheduled&#34;` represents status of the scheduling process for this pod.  - `&#34;Ready&#34;` means the pod is able to service requests and should be added to the load balancing pools of all matching services.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="poddnsconfig-v1-core">PodDNSConfig v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodDNSConfig</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodDNSConfig defines the DNS parameters of a pod in addition to those generated from DNSPolicy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nameservers</CODE><BR /><I>string array</I></TD><TD>A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.</TD></TR>
+<TR><TD><CODE>options</CODE><BR /><I><a href="#poddnsconfigoption-v1-core">PodDNSConfigOption</a> array</I></TD><TD>A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.</TD></TR>
+<TR><TD><CODE>searches</CODE><BR /><I>string array</I></TD><TD>A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="poddnsconfigoption-v1-core">PodDNSConfigOption v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodDNSConfigOption</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodDNSConfigOption defines DNS resolver options of a pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddnsconfig-v1-core">PodDNSConfig [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Required.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podip-v1-core">PodIP v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodIP</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IP address information for entries in the (plural) PodIPs field. Each entry includes:
+   IP: An IP address allocated to the pod. Routable at least within the cluster.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>ip is an IP address (IPv4 or IPv6) assigned to the pod</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podos-v1-core">PodOS v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodOS</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodOS defines the OS parameters of a pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the operating system. The currently supported values are linux and windows. Additional value may be defined in future and can be one of: https://github.com/opencontainers/runtime-spec/blob/master/config.md#platform-specific-configuration Clients should expect to handle additional values and treat unrecognized values in this field as os: null</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podreadinessgate-v1-core">PodReadinessGate v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodReadinessGate</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodReadinessGate contains the reference to a pod condition</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditionType</CODE><BR /><I>string</I></TD><TD>ConditionType refers to a condition in the pod&#39;s condition list with matching type.  Possible enum values:  - `&#34;ContainersReady&#34;` indicates whether all containers in the pod are ready.  - `&#34;Initialized&#34;` means that all init containers in the pod have started successfully.  - `&#34;PodScheduled&#34;` represents status of the scheduling process for this pod.  - `&#34;Ready&#34;` means the pod is able to service requests and should be added to the load balancing pools of all matching services.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podsecuritycontext-v1-core">PodSecurityContext v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodSecurityContext</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext.  Field values of container.securityContext take precedence over field values of PodSecurityContext.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsGroup</CODE><BR /><I>integer</I></TD><TD>A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod:  1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR&#39;d with rw-rw----  If unset, the Kubelet will not modify the ownership and permissions of any volume. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>fsGroupChangePolicy</CODE><BR /><I>string</I></TD><TD>fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are &#34;OnRootMismatch&#34; and &#34;Always&#34;. If not specified, &#34;Always&#34; is used. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>runAsGroup</CODE><BR /><I>integer</I></TD><TD>The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>runAsNonRoot</CODE><BR /><I>boolean</I></TD><TD>Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
+<TR><TD><CODE>runAsUser</CODE><BR /><I>integer</I></TD><TD>The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>seccompProfile</CODE><BR /><I><a href="#seccompprofile-v1-core">SeccompProfile</a></I></TD><TD>The seccomp options to use by the containers in this pod. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>supplementalGroups</CODE><BR /><I>integer array</I></TD><TD>A list of groups applied to the first process run in each container, in addition to the container&#39;s primary GID.  If unspecified, no groups will be added to any container. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>sysctls</CODE><BR /><I><a href="#sysctl-v1-core">Sysctl</a> array</I></TD><TD>Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>windowsOptions</CODE><BR /><I><a href="#windowssecuritycontextoptions-v1-core">WindowsSecurityContextOptions</a></I></TD><TD>The Windows specific settings applied to all containers. If unspecified, the options within a container&#39;s SecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podsmetricsource-v2-autoscaling">PodsMetricSource v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>PodsMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricsource-v2beta2-autoscaling">v2beta2</a>
+<a href="#podsmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podsmetricstatus-v2-autoscaling">PodsMetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>PodsMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#podsmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="policyrule-v1-rbac-authorization-k8s-io">PolicyRule v1 rbac.authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
+  <LI><a href="#role-v1-rbac-authorization-k8s-io">Role [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.</TD></TR>
+<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as &#34;pods&#34; or &#34;secrets&#34;) or non-resource URL paths (such as &#34;/api&#34;),  but not both.</TD></TR>
+<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. &#39;\*&#39; represents all resources.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verbs is a list of Verbs that apply to ALL the ResourceKinds contained in this rule. &#39;\*&#39; represents all verbs.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>PolicyRulesWithSubjects</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PolicyRulesWithSubjects prescribes a test that applies to a request to an apiserver. The test considers the subject making the request, the verb being requested, and the resource to be acted upon. This PolicyRulesWithSubjects matches a request if and only if both (a) at least one member of subjects matches the request and (b) at least one member of resourceRules or nonResourceRules matches the request.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule</a> array</I></TD><TD>`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.</TD></TR>
+<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">ResourcePolicyRule</a> array</I></TD><TD>`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.</TD></TR>
+<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">Subject</a> array</I></TD><TD>subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="portstatus-v1-core">PortStatus v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PortStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P></P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#loadbalanceringress-v1-core">LoadBalancerIngress [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error is to record the problem with the service port The format of the error shall comply with the following rules: - built-in error values shall be specified in this file and those shall use   CamelCase names - cloud provider specific error values must have names that comply with the   format foo.example.com/CamelCase.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>Port is the port number of the service port of which status is recorded here</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>Protocol is the protocol of the service port of which status is recorded here The supported values are: &#34;TCP&#34;, &#34;UDP&#34;, &#34;SCTP&#34;  Possible enum values:  - `&#34;SCTP&#34;` is the SCTP protocol.  - `&#34;TCP&#34;` is the TCP protocol.  - `&#34;UDP&#34;` is the UDP protocol.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="portworxvolumesource-v1-core">PortworxVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PortworxVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PortworxVolumeSource represents a Portworx volume resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>FSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>VolumeID uniquely identifies a Portworx volume</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="preconditions-v1-meta">Preconditions v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Preconditions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#deleteoptions-v1-meta">DeleteOptions [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>Specifies the target ResourceVersion</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>Specifies the target UID.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="preferredschedulingterm-v1-core">PreferredSchedulingTerm v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PreferredSchedulingTerm</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it&#39;s a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>preference</CODE><BR /><I><a href="#nodeselectorterm-v1-core">NodeSelectorTerm</a></I></TD><TD>A node selector term, associated with the corresponding weight.</TD></TR>
+<TR><TD><CODE>weight</CODE><BR /><I>integer</I></TD><TD>Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>PriorityLevelConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PriorityLevelConfiguration represents the configuration of a priority level.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#prioritylevelconfigurationspec-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#prioritylevelconfigurationstatus-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus</a></I></TD><TD>`status` is the current status of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>PriorityLevelConfigurationCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PriorityLevelConfigurationCondition defines the condition of priority level.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationstatus-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>`lastTransitionTime` is the last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>`message` is a human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>`status` is the status of the condition. Can be True, False, Unknown. Required.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>PriorityLevelConfigurationReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PriorityLevelConfigurationReference contains information that points to the &#34;request-priority&#34; being used.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of the priority level configuration being referenced Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="probe-v1-core">Probe v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Probe</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>exec</CODE><BR /><I><a href="#execaction-v1-core">ExecAction</a></I></TD><TD>Exec specifies the action to take.</TD></TR>
+<TR><TD><CODE>failureThreshold</CODE><BR /><I>integer</I></TD><TD>Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.</TD></TR>
+<TR><TD><CODE>grpc</CODE><BR /><I><a href="#grpcaction-v1-core">GRPCAction</a></I></TD><TD>GRPC specifies an action involving a GRPC port. This is an alpha field and requires enabling GRPCContainerProbe feature gate.</TD></TR>
+<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies the http request to perform.</TD></TR>
+<TR><TD><CODE>initialDelaySeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
+<TR><TD><CODE>periodSeconds</CODE><BR /><I>integer</I></TD><TD>How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.</TD></TR>
+<TR><TD><CODE>successThreshold</CODE><BR /><I>integer</I></TD><TD>Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.</TD></TR>
+<TR><TD><CODE>tcpSocket</CODE><BR /><I><a href="#tcpsocketaction-v1-core">TCPSocketAction</a></I></TD><TD>TCPSocket specifies an action involving a TCP port.</TD></TR>
+<TR><TD><CODE>terminationGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod needs to terminate gracefully upon probe failure. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. If this value is nil, the pod&#39;s terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="projectedvolumesource-v1-core">ProjectedVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ProjectedVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a projected volume source</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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.</TD></TR>
+<TR><TD><CODE>sources</CODE><BR /><I><a href="#volumeprojection-v1-core">VolumeProjection</a> array</I></TD><TD>list of volume projections</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="quantity-resource-core">Quantity resource core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>resource</CODE></TD><TD><CODE>Quantity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.
+
+The serialization format is:
+
+&lt;quantity&gt;        ::= &lt;signedNumber&gt;&lt;suffix&gt;
+  (Note that &lt;suffix&gt; may be empty, from the &#34;&#34; case in &lt;decimalSI&gt;.)
+&lt;digit&gt;           ::= 0 | 1 | ... | 9 &lt;digits&gt;          ::= &lt;digit&gt; | &lt;digit&gt;&lt;digits&gt; &lt;number&gt;          ::= &lt;digits&gt; | &lt;digits&gt;.&lt;digits&gt; | &lt;digits&gt;. | .&lt;digits&gt; &lt;sign&gt;            ::= &#34;+&#34; | &#34;-&#34; &lt;signedNumber&gt;    ::= &lt;number&gt; | &lt;sign&gt;&lt;number&gt; &lt;suffix&gt;          ::= &lt;binarySI&gt; | &lt;decimalExponent&gt; | &lt;decimalSI&gt; &lt;binarySI&gt;        ::= Ki | Mi | Gi | Ti | Pi | Ei
+  (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
+&lt;decimalSI&gt;       ::= m | &#34;&#34; | k | M | G | T | P | E
+  (Note that 1024 = 1Ki but 1000 = 1k; I didn&#39;t choose the capitalization.)
+&lt;decimalExponent&gt; ::= &#34;e&#34; &lt;signedNumber&gt; | &#34;E&#34; &lt;signedNumber&gt;
+
+No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.
+
+When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.
+
+Before serializing, Quantity will be put in &#34;canonical form&#34;. This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:
+  a. No precision is lost
+  b. No fractional digits will be emitted
+  c. The exponent (or suffix) is as large as possible.
+The sign will be omitted unless the number is negative.
+
+Examples:
+  1.5 will be serialized as &#34;1500m&#34;
+  1.5Gi will be serialized as &#34;1536Mi&#34;
+
+Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.
+
+Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don&#39;t diff.)
+
+This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csistoragecapacity-v1beta1-storage-k8s-io">CSIStorageCapacity [storage/v1beta1]</a></LI>
+  <LI><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity [storage/v1alpha1]</a></LI>
+  <LI><a href="#containerresourcemetricsource-v2beta1-autoscaling">ContainerResourceMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#containerresourcemetricstatus-v2beta1-autoscaling">ContainerResourceMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource [core/v1]</a></LI>
+  <LI><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#metrictarget-v2-autoscaling">MetricTarget [autoscaling/v2]</a></LI>
+  <LI><a href="#metrictarget-v2beta2-autoscaling">MetricTarget [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#podsmetricsource-v2beta1-autoscaling">PodsMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#resourcefieldselector-v1-core">ResourceFieldSelector [core/v1]</a></LI>
+  <LI><a href="#resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">QueuingConfiguration v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>QueuingConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>QueuingConfiguration holds the configuration parameters for queuing</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitresponse-v1beta2-flowcontrol-apiserver-k8s-io">LimitResponse [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>handSize</CODE><BR /><I>integer</I></TD><TD>`handSize` is a small positive number that configures the shuffle sharding of requests into queues.  When enqueuing a request at this priority level the request&#39;s flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here.  The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues).  See the user-facing documentation for more extensive guidance on setting this field.  This field has a default value of 8.</TD></TR>
+<TR><TD><CODE>queueLengthLimit</CODE><BR /><I>integer</I></TD><TD>`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected.  This value must be positive.  If not specified, it will be defaulted to 50.</TD></TR>
+<TR><TD><CODE>queues</CODE><BR /><I>integer</I></TD><TD>`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive.  Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant.  This field has a default value of 64.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="quobytevolumesource-v1-core">QuobyteVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>QuobyteVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Quobyte mount that lasts the lifetime of a pod. Quobyte volumes do not support ownership management or SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group to map volume access to Default is no group</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.</TD></TR>
+<TR><TD><CODE>registry</CODE><BR /><I>string</I></TD><TD>Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes</TD></TR>
+<TR><TD><CODE>tenant</CODE><BR /><I>string</I></TD><TD>Tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User to map volume access to Defaults to serivceaccount user</TD></TR>
+<TR><TD><CODE>volume</CODE><BR /><I>string</I></TD><TD>Volume is a string that references an already created Quobyte volume by name.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RBDPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>keyring</CODE><BR /><I>string</I></TD><TD>Keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>A collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>The rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>SecretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>The rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="rbdvolumesource-v1-core">RBDVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RBDVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>keyring</CODE><BR /><I>string</I></TD><TD>Keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>A collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>The rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>The rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replicasetcondition-v1-apps">ReplicaSetCondition v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicaSetCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ReplicaSetCondition describes the state of a replica set at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicasetstatus-v1-apps">ReplicaSetStatus [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replica set condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replicationcontrollercondition-v1-core">ReplicationControllerCondition v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicationControllerCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ReplicationControllerCondition describes the state of a replication controller at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#replicationcontrollerstatus-v1-core">ReplicationControllerStatus [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replication controller condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourceattributes-v1-authorization-k8s-io">ResourceAttributes v1 authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceAttributes</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1]</a></LI>
+  <LI><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API Group of the Resource.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource being requested for a &#34;get&#34; or deleted for a &#34;delete&#34;. &#34;&#34; (empty) means all.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the action being requested.  Currently, there is no distinction between no namespace and all namespaces &#34;&#34; (empty) is defaulted for LocalSubjectAccessReviews &#34;&#34; (empty) is empty for cluster-scoped resources &#34;&#34; (empty) means &#34;all&#34; for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is one of the existing resource types.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>subresource</CODE><BR /><I>string</I></TD><TD>Subresource is one of the existing resource types.  &#34;&#34; means none.</TD></TR>
+<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API Version of the Resource.  &#34;*&#34; means all.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcefieldselector-v1-core">ResourceFieldSelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceFieldSelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceFieldSelector represents container resources (cpu, memory) and their output format</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile [core/v1]</a></LI>
+  <LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerName</CODE><BR /><I>string</I></TD><TD>Container name: required for volumes, optional for env vars</TD></TR>
+<TR><TD><CODE>divisor</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Specifies the output format of the exposed resources, defaults to &#34;1&#34;</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Required: resource to select</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcemetricsource-v2-autoscaling">ResourceMetricSource v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.  Only one &#34;target&#34; type should be set.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricsource-v2beta2-autoscaling">v2beta2</a>
+<a href="#resourcemetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcemetricstatus-v2-autoscaling">ResourceMetricStatus v2 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>ResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricstatus-v2beta2-autoscaling">v2beta2</a>
+<a href="#resourcemetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">ResourcePolicyRule v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>ResourcePolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourcePolicyRule is a predicate that matches some resource requests, testing the request&#39;s verb and the target resource. A ResourcePolicyRule matches a resource request if and only if: (a) at least one member of verbs matches the request, (b) at least one member of apiGroups matches the request, (c) at least one member of resources matches the request, and (d) either (d1) the request does not specify a namespace (i.e., `Namespace==&#34;&#34;`) and clusterScope is true or (d2) the request specifies a namespace and least one member of namespaces matches the request&#39;s namespace.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>`apiGroups` is a list of matching API groups and may not be empty. &#34;*&#34; matches all API groups and, if present, must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>clusterScope</CODE><BR /><I>boolean</I></TD><TD>`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.</TD></TR>
+<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>`namespaces` is a list of target namespaces that restricts matches.  A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains &#34;*&#34;.  Note that &#34;*&#34; matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource.  For example, [ &#34;services&#34;, &#34;nodes/status&#34; ].  This list may not be empty. &#34;*&#34; matches all resources and, if present, must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs and, if present, must be the only entry. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcerequirements-v1-core">ResourceRequirements v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceRequirements</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceRequirements describes the compute resource requirements.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>limits</CODE><BR /><I>object</I></TD><TD>Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
+<TR><TD><CODE>requests</CODE><BR /><I>object</I></TD><TD>Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourcerule-v1-authorization-k8s-io">ResourceRule v1 authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.  &#34;*&#34; means all.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to.  &#34;*&#34; means all in the specified apiGroups.  &#34;*/foo&#34; represents the subresource &#39;foo&#39; for all resources in the specified apiGroups.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy.  &#34;*&#34; means all.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="roleref-v1-rbac-authorization-k8s-io">RoleRef v1 rbac.authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RoleRef</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RoleRef contains information that points to the role being used</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
+  <LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="rollingupdatestatefulsetstrategy-v1-apps">RollingUpdateStatefulSetStrategy v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RollingUpdateStatefulSetStrategy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned. Default value is 0.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="rulewithoperations-v1-admissionregistration-k8s-io">RuleWithOperations v1 admissionregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RuleWithOperations</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
+  <LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the API groups the resources belong to. &#39;\*&#39; is all groups. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
+<TR><TD><CODE>apiVersions</CODE><BR /><I>string array</I></TD><TD>APIVersions is the API versions the resources belong to. &#39;\*&#39; is all versions. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
+<TR><TD><CODE>operations</CODE><BR /><I>string array</I></TD><TD>Operations is the operations the admission hook cares about - CREATE, UPDATE, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to.  For example: &#39;pods&#39; means pods. &#39;pods/log&#39; means the log subresource of pods. &#39;\*&#39; means all resources, but not subresources. &#39;pods/\*&#39; means all subresources of pods. &#39;\*/scale&#39; means all scale subresources. &#39;\*/\*&#39; means all resources and their subresources.  If wildcard is present, the validation rule will ensure resources do not overlap with each other.  Depending on the enclosing object, subresources might not be allowed. Required.</TD></TR>
+<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope specifies the scope of this rule. Valid values are &#34;Cluster&#34;, &#34;Namespaced&#34;, and &#34;*&#34; &#34;Cluster&#34; means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. &#34;Namespaced&#34; means that only namespaced resources will match this rule. &#34;*&#34; means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is &#34;*&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="runasgroupstrategyoptions-v1beta1-policy">RunAsGroupStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RunAsGroupStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RunAsGroupStrategyOptions defines the strategy type and any options used to create the strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of gids that may be used. If you would like to force a single gid then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable RunAsGroup values that may be set.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RunAsUserStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RunAsUserStrategyOptions defines the strategy type and any options used to create the strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of uids that may be used. If you would like to force a single uid then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="runtimeclassstrategyoptions-v1beta1-policy">RuntimeClassStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RuntimeClassStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>RuntimeClassStrategyOptions define the strategy that will dictate the allowable RuntimeClasses for a pod.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowedRuntimeClassNames</CODE><BR /><I>string array</I></TD><TD>allowedRuntimeClassNames is an allowlist of RuntimeClass names that may be specified on a pod. A value of &#34;*&#34; means that any RuntimeClass name is allowed, and must be the only item in the list. An empty list requires the RuntimeClassName field to be unset.</TD></TR>
+<TR><TD><CODE>defaultRuntimeClassName</CODE><BR /><I>string</I></TD><TD>defaultRuntimeClassName is the default RuntimeClassName to set on the pod. The default MUST be allowed by the allowedRuntimeClassNames list. A value of nil does not mutate the Pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="selinuxoptions-v1-core">SELinuxOptions v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SELinuxOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SELinuxOptions are the labels to be applied to the container</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
+  <LI><a href="#selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions [policy/v1beta1]</a></LI>
+  <LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>level</CODE><BR /><I>string</I></TD><TD>Level is SELinux level label that applies to the container.</TD></TR>
+<TR><TD><CODE>role</CODE><BR /><I>string</I></TD><TD>Role is a SELinux role label that applies to the container.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is a SELinux type label that applies to the container.</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User is a SELinux user label that applies to the container.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SELinuxStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SELinuxStrategyOptions defines the strategy type and any options used to create the strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable labels that may be set.</TD></TR>
+<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>seLinuxOptions required to run as; required for MustRunAs More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scale-v1-autoscaling">Scale v1 autoscaling</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Scale</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Scale represents a scaling request for a resource.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1-autoscaling">ScaleSpec</a></I></TD><TD>defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#scalestatus-v1-autoscaling">ScaleStatus</a></I></TD><TD>current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScaleIOPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ScaleIOPersistentVolumeSource represents a persistent ScaleIO volume</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Default is &#34;xfs&#34;</TD></TR>
+<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>The host address of the ScaleIO API Gateway.</TD></TR>
+<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>The name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>SecretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.</TD></TR>
+<TR><TD><CODE>sslEnabled</CODE><BR /><I>boolean</I></TD><TD>Flag to enable/disable SSL communication with Gateway, default false</TD></TR>
+<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>Indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.</TD></TR>
+<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>The ScaleIO Storage Pool associated with the protection domain.</TD></TR>
+<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>The name of the storage system as configured in ScaleIO.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>The name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scaleiovolumesource-v1-core">ScaleIOVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScaleIOVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ScaleIOVolumeSource represents a persistent ScaleIO volume</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Default is &#34;xfs&#34;.</TD></TR>
+<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>The host address of the ScaleIO API Gateway.</TD></TR>
+<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>The name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.</TD></TR>
+<TR><TD><CODE>sslEnabled</CODE><BR /><I>boolean</I></TD><TD>Flag to enable/disable SSL communication with Gateway, default false</TD></TR>
+<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>Indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.</TD></TR>
+<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>The ScaleIO Storage Pool associated with the protection domain.</TD></TR>
+<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>The name of the storage system as configured in ScaleIO.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>The name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scheduling-v1-node-k8s-io">Scheduling v1 node.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Scheduling</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#scheduling-v1beta1-node-k8s-io">v1beta1</a>
+<a href="#scheduling-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod&#39;s existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.</TD></TR>
+<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scopeselector-v1-core">ScopeSelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScopeSelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A scope selector represents the AND of the selectors represented by the scoped-resource selector requirements.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourcequotaspec-v1-core">ResourceQuotaSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#scopedresourceselectorrequirement-v1-core">ScopedResourceSelectorRequirement</a> array</I></TD><TD>A list of scope selector requirements by scope of the resources.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="scopedresourceselectorrequirement-v1-core">ScopedResourceSelectorRequirement v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScopedResourceSelectorRequirement</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#scopeselector-v1-core">ScopeSelector [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents a scope&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.  Possible enum values:  - `&#34;DoesNotExist&#34;`  - `&#34;Exists&#34;`  - `&#34;In&#34;`  - `&#34;NotIn&#34;`</TD></TR>
+<TR><TD><CODE>scopeName</CODE><BR /><I>string</I></TD><TD>The name of the scope that the selector applies to.  Possible enum values:  - `&#34;BestEffort&#34;` Match all pod objects that have best effort quality of service  - `&#34;CrossNamespacePodAffinity&#34;` Match all pod objects that have cross-namespace pod (anti)affinity mentioned. This is a beta feature enabled by the PodAffinityNamespaceSelector feature flag.  - `&#34;NotBestEffort&#34;` Match all pod objects that do not have best effort quality of service  - `&#34;NotTerminating&#34;` Match all pod objects where spec.activeDeadlineSeconds is nil  - `&#34;PriorityClass&#34;` Match all pod objects that have priority class mentioned  - `&#34;Terminating&#34;` Match all pod objects where spec.activeDeadlineSeconds &gt;=0</TD></TR>
+<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="seccompprofile-v1-core">SeccompProfile v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SeccompProfile</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SeccompProfile defines a pod/container&#39;s seccomp profile settings. Only one profile source may be set.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
+  <LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>localhostProfile</CODE><BR /><I>string</I></TD><TD>localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet&#39;s configured seccomp profile location. Must only be set if type is &#34;Localhost&#34;.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type indicates which kind of seccomp profile will be applied. Valid options are:  Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied.  Possible enum values:  - `&#34;Localhost&#34;` indicates a profile defined in a file on the node should be used. The file&#39;s location relative to &lt;kubelet-root-dir&gt;/seccomp.  - `&#34;RuntimeDefault&#34;` represents the default container runtime seccomp profile.  - `&#34;Unconfined&#34;` indicates no seccomp profile is applied (A.K.A. unconfined).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="secretenvsource-v1-core">SecretEnvSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretEnvSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SecretEnvSource selects a Secret to populate the environment variables with.
+
+The contents of the target Secret&#39;s Data field will represent the key-value pairs as environment variables.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#envfromsource-v1-core">EnvFromSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="secretkeyselector-v1-core">SecretKeySelector v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretKeySelector</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SecretKeySelector selects a key of a Secret.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key of the secret to select from.  Must be a valid secret key.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or its key must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="secretprojection-v1-core">SecretProjection v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretProjection</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Adapts a secret into a projected volume.
+
+The contents of the target Secret&#39;s Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced Secret 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 Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or its key must be defined</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="secretreference-v1-core">SecretReference v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csipersistentvolumesource-v1-core">CSIPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource [core/v1]</a></LI>
+  <LI><a href="#scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is unique within a namespace to reference a secret resource.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace defines the space within which the secret name must be unique.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="secretvolumesource-v1-core">SecretVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Adapts a Secret into a volume.
+
+The contents of the target Secret&#39;s Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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.</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced Secret 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 Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
+<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or its keys must be defined</TD></TR>
+<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>Name of the secret in the pod&#39;s namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="securitycontext-v1-core">SecurityContext v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecurityContext</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext.  When both are set, the values in SecurityContext take precedence.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>capabilities</CODE><BR /><I><a href="#capabilities-v1-core">Capabilities</a></I></TD><TD>The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>privileged</CODE><BR /><I>boolean</I></TD><TD>Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>procMount</CODE><BR /><I>string</I></TD><TD>procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>readOnlyRootFilesystem</CODE><BR /><I>boolean</I></TD><TD>Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>runAsGroup</CODE><BR /><I>integer</I></TD><TD>The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>runAsNonRoot</CODE><BR /><I>boolean</I></TD><TD>Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
+<TR><TD><CODE>runAsUser</CODE><BR /><I>integer</I></TD><TD>The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>seccompProfile</CODE><BR /><I><a href="#seccompprofile-v1-core">SeccompProfile</a></I></TD><TD>The seccomp options to use by this container. If seccomp options are provided at both the pod &amp; container level, the container options override the pod options. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
+<TR><TD><CODE>windowsOptions</CODE><BR /><I><a href="#windowssecuritycontextoptions-v1-core">WindowsSecurityContextOptions</a></I></TD><TD>The Windows specific settings applied to all containers. If unspecified, the options from the PodSecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServerAddressByClientCIDR</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apigroup-v1-meta">APIGroup [meta/v1]</a></LI>
+  <LI><a href="#apiversions-v1-meta">APIVersions [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>clientCIDR</CODE><BR /><I>string</I></TD><TD>The CIDR with which clients can match their IP to figure out the server address that they should use.</TD></TR>
+<TR><TD><CODE>serverAddress</CODE><BR /><I>string</I></TD><TD>Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="serverstorageversion-v1alpha1-internal-apiserver-k8s-io">ServerStorageVersion v1alpha1 internal.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>ServerStorageVersion</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>An API server instance reports the version it can decode and the version it encodes objects to when persisting objects in the backend.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus [apiserverinternal/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiServerID</CODE><BR /><I>string</I></TD><TD>The ID of the reporting API server.</TD></TR>
+<TR><TD><CODE>decodableVersions</CODE><BR /><I>string array</I></TD><TD>The API server can decode objects encoded in these versions. The encodingVersion must be included in the decodableVersions.</TD></TR>
+<TR><TD><CODE>encodingVersion</CODE><BR /><I>string</I></TD><TD>The API server encodes the object to this version when persisting it in the backend (e.g., etcd).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io">ServiceAccountSubject v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>ServiceAccountSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServiceAccountSubject holds detailed information for service-account-kind subject.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of matching ServiceAccount objects, or &#34;*&#34; to match regardless of name. Required.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>`namespace` is the namespace of matching ServiceAccount objects. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="serviceaccounttokenprojection-v1-core">ServiceAccountTokenProjection v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceAccountTokenProjection</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServiceAccountTokenProjection represents a projected service account token volume. This projection can be used to insert a service account token into the pods runtime filesystem for use against APIs (Kubernetes API Server or otherwise).</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>audience</CODE><BR /><I>string</I></TD><TD>Audience is the intended audience of the token. A recipient of a token must identify itself with an identifier specified in the audience of the token, and otherwise should reject the token. The audience defaults to the identifier of the apiserver.</TD></TR>
+<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>ExpirationSeconds is the requested duration of validity of the service account token. As the token approaches expiration, the kubelet volume plugin will proactively rotate the service account token. The kubelet will start trying to rotate the token if the token is older than 80 percent of its time to live or if the token is older than 24 hours.Defaults to 1 hour and must be at least 10 minutes.</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the path relative to the mount point of the file to project the token into.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="servicebackendport-v1-networking-k8s-io">ServiceBackendPort v1 networking.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceBackendPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServiceBackendPort is the service port being referenced.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressservicebackend-v1-networking-k8s-io">IngressServiceBackend [networking/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the port on the Service. This is a mutually exclusive setting with &#34;Number&#34;.</TD></TR>
+<TR><TD><CODE>number</CODE><BR /><I>integer</I></TD><TD>Number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with &#34;Name&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="serviceport-v1-core">ServicePort v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServicePort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServicePort contains information on service&#39;s port.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#servicespec-v1-core">ServiceSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port within the service. This must be a DNS_LABEL. All ports within a ServiceSpec must have unique names. When considering the endpoints for a Service, this must match the &#39;name&#39; field in the EndpointPort. Optional if only one ServicePort is defined on this service.</TD></TR>
+<TR><TD><CODE>nodePort</CODE><BR /><I>integer</I></TD><TD>The port on each node on which this service is exposed when type is NodePort or LoadBalancer.  Usually assigned by the system. If a value is specified, in-range, and not in use it will be used, otherwise the operation will fail.  If not specified, a port will be allocated if this Service requires one.  If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type from NodePort to ClusterIP). More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port that will be exposed by this service.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Supports &#34;TCP&#34;, &#34;UDP&#34;, and &#34;SCTP&#34;. Default is TCP.  Possible enum values:  - `&#34;SCTP&#34;` is the SCTP protocol.  - `&#34;TCP&#34;` is the TCP protocol.  - `&#34;UDP&#34;` is the UDP protocol.</TD></TR>
+<TR><TD><CODE>targetPort</CODE></TD><TD>Number or name of the port to access on the pods targeted by the service. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME. If this is a string, it will be looked up as a named port in the target Pod&#39;s container ports. If this is not specified, the value of the &#39;port&#39; field is used (an identity map). This field is ignored for services with clusterIP=None, and should be omitted or set equal to the &#39;port&#39; field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="servicereference-v1-admissionregistration-k8s-io">ServiceReference v1 admissionregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ServiceReference holds a reference to Service.legacy.k8s.io</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#webhookclientconfig-v1-admissionregistration-k8s-io">WebhookClientConfig [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of the service. Required</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>`namespace` is the namespace of the service. Required</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>`path` is an optional URL path which will be sent in any request to this service.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="sessionaffinityconfig-v1-core">SessionAffinityConfig v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SessionAffinityConfig</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SessionAffinityConfig represents the configurations of session affinity.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#servicespec-v1-core">ServiceSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>clientIP</CODE><BR /><I><a href="#clientipconfig-v1-core">ClientIPConfig</a></I></TD><TD>clientIP contains the configurations of Client IP based session affinity.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="statefulsetcondition-v1-apps">StatefulSetCondition v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSetCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatefulSetCondition describes the state of a statefulset at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulsetstatus-v1-apps">StatefulSetStatus [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of statefulset condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="statefulsetpersistentvolumeclaimretentionpolicy-v1-apps">StatefulSetPersistentVolumeClaimRetentionPolicy v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSetPersistentVolumeClaimRetentionPolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatefulSetPersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>whenDeleted</CODE><BR /><I>string</I></TD><TD>WhenDeleted specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is deleted. The default policy of `Retain` causes PVCs to not be affected by StatefulSet deletion. The `Delete` policy causes those PVCs to be deleted.</TD></TR>
+<TR><TD><CODE>whenScaled</CODE><BR /><I>string</I></TD><TD>WhenScaled specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is scaled down. The default policy of `Retain` causes PVCs to not be affected by a scaledown. The `Delete` policy causes the associated PVCs for any excess pods above the replica count to be deleted.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy v1 apps</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSetUpdateStrategy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatestatefulsetstrategy-v1-apps">RollingUpdateStatefulSetStrategy</a></I></TD><TD>RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.  Possible enum values:  - `&#34;OnDelete&#34;` triggers the legacy behavior. Version tracking and ordered rolling restarts are disabled. Pods are recreated from the StatefulSetSpec when they are manually deleted. When a scale operation is performed with this strategy,specification version indicated by the StatefulSet&#39;s currentRevision.  - `&#34;RollingUpdate&#34;` indicates that update will be applied to all Pods in the StatefulSet with respect to the StatefulSet ordering constraints. When a scale operation is performed with this strategy, new Pods will be created from the specification version indicated by the StatefulSet&#39;s updateRevision.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="status-v1-meta">Status v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Status</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Status is a return value for calls that don&#39;t return other objects.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>code</CODE><BR /><I>integer</I></TD><TD>Suggested HTTP return code for this status, 0 if not set.</TD></TR>
+<TR><TD><CODE>details</CODE><BR /><I><a href="#statusdetails-v1-meta">StatusDetails</a></I></TD><TD>Extended data associated with the reason.  Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the status of this operation.</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A machine-readable description of why this operation is in the &#34;Failure&#34; status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the operation. One of: &#34;Success&#34; or &#34;Failure&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="statuscause-v1-meta">StatusCause v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatusCause</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#statusdetails-v1-meta">StatusDetails [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>field</CODE><BR /><I>string</I></TD><TD>The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed.  Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.  Examples:   &#34;name&#34; - the field &#34;name&#34; on the current resource   &#34;items[0].name&#34; - the field &#34;name&#34; on the first array entry in &#34;items&#34;</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the cause of the error.  This field may be presented as-is to a reader.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A machine-readable description of the cause of the error. If this value is empty there is no information available.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="statusdetails-v1-meta">StatusDetails v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatusDetails</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#status-v1-meta">Status [meta/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>causes</CODE><BR /><I><a href="#statuscause-v1-meta">StatusCause</a> array</I></TD><TD>The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.</TD></TR>
+<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>The group attribute of the resource associated with the status StatusReason.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).</TD></TR>
+<TR><TD><CODE>retryAfterSeconds</CODE><BR /><I>integer</I></TD><TD>If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageOSPersistentVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a StorageOS persistent volume resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>SecretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.</TD></TR>
+<TR><TD><CODE>volumeNamespace</CODE><BR /><I>string</I></TD><TD>VolumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod&#39;s namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to &#34;default&#34; if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="storageosvolumesource-v1-core">StorageOSVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageOSVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a StorageOS persistent volume resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
+<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.</TD></TR>
+<TR><TD><CODE>volumeNamespace</CODE><BR /><I>string</I></TD><TD>VolumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod&#39;s namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to &#34;default&#34; if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="storageversioncondition-v1alpha1-internal-apiserver-k8s-io">StorageVersionCondition v1alpha1 internal.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersionCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Describes the state of the storageVersion at a certain point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus [apiserverinternal/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>If set, this represents the .metadata.generation that the condition was set based upon.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of the condition.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="subject-v1beta2-flowcontrol-apiserver-k8s-io">Subject v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Subject matches the originator of a request, as identified by the request authentication system. There are three ways of matching an originator; by user, group, or service account.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+<a href="#subject-v1-rbac-authorization-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>group</CODE><BR /><I><a href="#groupsubject-v1beta2-flowcontrol-apiserver-k8s-io">GroupSubject</a></I></TD><TD>`group` matches based on user group name.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>`kind` indicates which one of the other fields is non-empty. Required</TD></TR>
+<TR><TD><CODE>serviceAccount</CODE><BR /><I><a href="#serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io">ServiceAccountSubject</a></I></TD><TD>`serviceAccount` matches ServiceAccounts.</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I><a href="#usersubject-v1beta2-flowcontrol-apiserver-k8s-io">UserSubject</a></I></TD><TD>`user` matches based on username.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus v1 authorization.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SubjectRulesReviewStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it&#39;s safe to assume the subject has that permission, even if that list is incomplete.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn&#39;t support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.</TD></TR>
+<TR><TD><CODE>incomplete</CODE><BR /><I>boolean</I></TD><TD>Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn&#39;t support rules evaluation.</TD></TR>
+<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcerule-v1-authorization-k8s-io">NonResourceRule</a> array</I></TD><TD>NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
+<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcerule-v1-authorization-k8s-io">ResourceRule</a> array</I></TD><TD>ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions v1beta1 policy</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SupplementalGroupsStrategyOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of supplemental groups.  If you would like to force a single supplemental group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="sysctl-v1-core">Sysctl v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Sysctl</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Sysctl defines a kernel parameter to be set</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of a property to set</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Value of a property to set</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="tcpsocketaction-v1-core">TCPSocketAction v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TCPSocketAction</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>TCPSocketAction describes an action based on opening a socket</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#lifecyclehandler-v1-core">LifecycleHandler [core/v1]</a></LI>
+  <LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Optional: Host name to connect to, defaults to the pod IP.</TD></TR>
+<TR><TD><CODE>port</CODE></TD><TD>Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="taint-v1-core">Taint v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Taint</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>The node this Taint is attached to has the &#34;effect&#34; on any pod that does not tolerate the Taint.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#nodespec-v1-core">NodeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>effect</CODE><BR /><I>string</I></TD><TD>Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.  Possible enum values:  - `&#34;NoExecute&#34;` Evict any already-running pods that do not tolerate the taint. Currently enforced by NodeController.  - `&#34;NoSchedule&#34;` Do not allow new pods to schedule onto the node unless they tolerate the taint, but allow all pods submitted to Kubelet without going through the scheduler to start, and allow all already-running pods to continue running. Enforced by the scheduler.  - `&#34;PreferNoSchedule&#34;` Like TaintEffectNoSchedule, but the scheduler tries not to schedule new pods onto the node, rather than prohibiting new pods from scheduling onto the node entirely. Enforced by the scheduler.</TD></TR>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>Required. The taint key to be applied to a node.</TD></TR>
+<TR><TD><CODE>timeAdded</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>TimeAdded represents the time at which the taint was added. It is only written for NoExecute taints.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>The taint value corresponding to the taint key.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="time-v1-meta">Time v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Time</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON.  Wrappers are provided for many of the factory methods that the time package offers.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition [apiregistration/v1]</a></LI>
+  <LI><a href="#certificatesigningrequestcondition-v1-certificates-k8s-io">CertificateSigningRequestCondition [certificates/v1]</a></LI>
+  <LI><a href="#condition-v1-meta">Condition [meta/v1]</a></LI>
+  <LI><a href="#containerstaterunning-v1-core">ContainerStateRunning [core/v1]</a></LI>
+  <LI><a href="#containerstateterminated-v1-core">ContainerStateTerminated [core/v1]</a></LI>
+  <LI><a href="#cronjobstatus-v1-batch">CronJobStatus [batch/v1]</a></LI>
+  <LI><a href="#cronjobstatus-v1beta1-batch">CronJobStatus [batch/v1beta1]</a></LI>
+  <LI><a href="#customresourcedefinitioncondition-v1-apiextensions-k8s-io">CustomResourceDefinitionCondition [apiextensions/v1]</a></LI>
+  <LI><a href="#daemonsetcondition-v1-apps">DaemonSetCondition [apps/v1]</a></LI>
+  <LI><a href="#deploymentcondition-v1-apps">DeploymentCondition [apps/v1]</a></LI>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+  <LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+  <LI><a href="#flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaCondition [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#horizontalpodautoscalercondition-v2-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscalercondition-v2beta2-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v1]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#jobcondition-v1-batch">JobCondition [batch/v1]</a></LI>
+  <LI><a href="#jobstatus-v1-batch">JobStatus [batch/v1]</a></LI>
+  <LI><a href="#managedfieldsentry-v1-meta">ManagedFieldsEntry [meta/v1]</a></LI>
+  <LI><a href="#namespacecondition-v1-core">NamespaceCondition [core/v1]</a></LI>
+  <LI><a href="#nodecondition-v1-core">NodeCondition [core/v1]</a></LI>
+  <LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition [core/v1]</a></LI>
+  <LI><a href="#podcondition-v1-core">PodCondition [core/v1]</a></LI>
+  <LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
+  <LI><a href="#prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition [flowcontrol/v1beta1]</a></LI>
+  <LI><a href="#replicasetcondition-v1-apps">ReplicaSetCondition [apps/v1]</a></LI>
+  <LI><a href="#replicationcontrollercondition-v1-core">ReplicationControllerCondition [core/v1]</a></LI>
+  <LI><a href="#statefulsetcondition-v1-apps">StatefulSetCondition [apps/v1]</a></LI>
+  <LI><a href="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io">StorageVersionCondition [apiserverinternal/v1alpha1]</a></LI>
+  <LI><a href="#taint-v1-core">Taint [core/v1]</a></LI>
+  <LI><a href="#tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus [authentication/v1]</a></LI>
+  <LI><a href="#volumeerror-v1-storage-k8s-io">VolumeError [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="toleration-v1-core">Toleration v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Toleration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>The pod this Toleration is attached to tolerates any taint that matches the triple &lt;key,value,effect&gt; using the matching operator &lt;operator&gt;.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+  <LI><a href="#scheduling-v1-node-k8s-io">Scheduling [node/v1]</a></LI>
+  <LI><a href="#scheduling-v1beta1-node-k8s-io">Scheduling [node/v1beta1]</a></LI>
+  <LI><a href="#scheduling-v1alpha1-node-k8s-io">Scheduling [node/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>effect</CODE><BR /><I>string</I></TD><TD>Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.  Possible enum values:  - `&#34;NoExecute&#34;` Evict any already-running pods that do not tolerate the taint. Currently enforced by NodeController.  - `&#34;NoSchedule&#34;` Do not allow new pods to schedule onto the node unless they tolerate the taint, but allow all pods submitted to Kubelet without going through the scheduler to start, and allow all already-running pods to continue running. Enforced by the scheduler.  - `&#34;PreferNoSchedule&#34;` Like TaintEffectNoSchedule, but the scheduler tries not to schedule new pods onto the node, rather than prohibiting new pods from scheduling onto the node entirely. Enforced by the scheduler.</TD></TR>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.</TD></TR>
+<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Operator represents a key&#39;s relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.  Possible enum values:  - `&#34;Equal&#34;`  - `&#34;Exists&#34;`</TD></TR>
+<TR><TD><CODE>tolerationSeconds</CODE><BR /><I>integer</I></TD><TD>TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="topologyselectorlabelrequirement-v1-core">TopologySelectorLabelRequirement v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TopologySelectorLabelRequirement</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A topology selector requirement is a selector that matches given label. This is an alpha feature and may change in the future.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#topologyselectorterm-v1-core">TopologySelectorTerm [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The label key that the selector applies to.</TD></TR>
+<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. One value must match the label to be selected. Each entry in Values is ORed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="topologyselectorterm-v1-core">TopologySelectorTerm v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TopologySelectorTerm</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>A topology selector term represents the result of label queries. A null or empty topology selector term matches no objects. The requirements of them are ANDed. It provides a subset of functionality as NodeSelectorTerm. This is an alpha feature and may change in the future.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#storageclass-v1-storage-k8s-io">StorageClass [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>matchLabelExpressions</CODE><BR /><I><a href="#topologyselectorlabelrequirement-v1-core">TopologySelectorLabelRequirement</a> array</I></TD><TD>A list of topology selector requirements by labels.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="topologyspreadconstraint-v1-core">TopologySpreadConstraint v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TopologySpreadConstraint</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>TopologySpreadConstraint specifies how to spread matching pods among the given topology.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>labelSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>LabelSelector is used to find matching pods. Pods that match this label selector are counted to determine the number of pods in their corresponding topology domain.</TD></TR>
+<TR><TD><CODE>maxSkew</CODE><BR /><I>integer</I></TD><TD>MaxSkew describes the degree to which pods may be unevenly distributed. When `whenUnsatisfiable=DoNotSchedule`, it is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 1/1/0: | zone1 | zone2 | zone3 | |   P   |   P   |       | - if MaxSkew is 1, incoming pod can only be scheduled to zone3 to become 1/1/1; scheduling it onto zone1(zone2) would make the ActualSkew(2-0) on zone1(zone2) violate MaxSkew(1). - if MaxSkew is 2, incoming pod can be scheduled onto any zone. When `whenUnsatisfiable=ScheduleAnyway`, it is used to give higher precedence to topologies that satisfy it. It&#39;s a required field. Default value is 1 and 0 is not allowed.</TD></TR>
+<TR><TD><CODE>topologyKey</CODE><BR /><I>string</I></TD><TD>TopologyKey is the key of node labels. Nodes that have a label with this key and identical values are considered to be in the same topology. We consider each &lt;key, value&gt; as a &#34;bucket&#34;, and try to put balanced number of pods into each bucket. It&#39;s a required field.</TD></TR>
+<TR><TD><CODE>whenUnsatisfiable</CODE><BR /><I>string</I></TD><TD>WhenUnsatisfiable indicates how to deal with a pod if it doesn&#39;t satisfy the spread constraint. - DoNotSchedule (default) tells the scheduler not to schedule it. - ScheduleAnyway tells the scheduler to schedule the pod in any location,   but giving higher precedence to topologies that would help reduce the   skew. A constraint is considered &#34;Unsatisfiable&#34; for an incoming pod if and only if every possible node assignment for that pod would violate &#34;MaxSkew&#34; on some topology. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 3/1/1: | zone1 | zone2 | zone3 | | P P P |   P   |   P   | If WhenUnsatisfiable is set to DoNotSchedule, incoming pod can only be scheduled to zone2(zone3) to become 3/2/1(3/1/2) as ActualSkew(2-1) on zone2(zone3) satisfies MaxSkew(1). In other words, the cluster can still be imbalanced, but scheduler won&#39;t make it *more* imbalanced. It&#39;s a required field.  Possible enum values:  - `&#34;DoNotSchedule&#34;` instructs the scheduler not to schedule the pod when constraints are not satisfied.  - `&#34;ScheduleAnyway&#34;` instructs the scheduler to schedule the pod even if constraints are not satisfied.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="typedlocalobjectreference-v1-core">TypedLocalObjectReference v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TypedLocalObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>TypedLocalObjectReference contains enough information to let you locate the typed referenced object inside the same namespace.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend [networking/v1]</a></LI>
+  <LI><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="uncountedterminatedpods-v1-batch">UncountedTerminatedPods v1 batch</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>UncountedTerminatedPods</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>UncountedTerminatedPods holds UIDs of Pods that have terminated but haven&#39;t been accounted in Job status counters.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jobstatus-v1-batch">JobStatus [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>failed</CODE><BR /><I>string array</I></TD><TD>Failed holds UIDs of failed Pods.</TD></TR>
+<TR><TD><CODE>succeeded</CODE><BR /><I>string array</I></TD><TD>Succeeded holds UIDs of succeeded Pods.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="userinfo-v1-authentication-k8s-io">UserInfo v1 authentication.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>UserInfo</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>UserInfo holds the information about the user needed to implement the user.Info interface.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus [authentication/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Any additional information provided by the authenticator.</TD></TR>
+<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>The names of groups this user is a part of.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.</TD></TR>
+<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>The name that uniquely identifies this user among all active users.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="usersubject-v1beta2-flowcontrol-apiserver-k8s-io">UserSubject v1beta2 flowcontrol.apiserver.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>UserSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>UserSubject holds detailed information for user-kind subject.</P>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#usersubject-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the username that matches, or &#34;*&#34; to match all usernames. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook v1 admissionregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ValidatingWebhook</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ValidatingWebhook describes an admission webhook and the resources and operations it applies to.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionReviewVersions</CODE><BR /><I>string array</I></TD><TD>AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.</TD></TR>
+<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1-admissionregistration-k8s-io">WebhookClientConfig</a></I></TD><TD>ClientConfig defines how to communicate with the hook. Required</TD></TR>
+<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
+<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;rules&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;.  - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.  - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.  Defaults to &#34;Equivalent&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where &#34;imagepolicy&#34; is the name of the webhook, and kubernetes.io is the name of the organization. Required.</TD></TR>
+<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.  For example, to run the webhook on any objects whose namespace is not associated with &#34;runlevel&#34; of &#34;0&#34; or &#34;1&#34;;  you will set the selector as follows: &#34;namespaceSelector&#34;: {   &#34;matchExpressions&#34;: [     {       &#34;key&#34;: &#34;runlevel&#34;,       &#34;operator&#34;: &#34;NotIn&#34;,       &#34;values&#34;: [         &#34;0&#34;,         &#34;1&#34;       ]     }   ] }  If instead you want to only run the webhook on any objects whose namespace is associated with the &#34;environment&#34; of &#34;prod&#34; or &#34;staging&#34;; you will set the selector as follows: &#34;namespaceSelector&#34;: {   &#34;matchExpressions&#34;: [     {       &#34;key&#34;: &#34;environment&#34;,       &#34;operator&#34;: &#34;In&#34;,       &#34;values&#34;: [         &#34;prod&#34;,         &#34;staging&#34;       ]     }   ] }  See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels for more examples of label selectors.  Default to the empty LabelSelector, which matches everything.</TD></TR>
+<TR><TD><CODE>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#rulewithoperations-v1-admissionregistration-k8s-io">RuleWithOperations</a> array</I></TD><TD>Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.</TD></TR>
+<TR><TD><CODE>sideEffects</CODE><BR /><I>string</I></TD><TD>SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="validationrule-v1-apiextensions-k8s-io">ValidationRule v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ValidationRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ValidationRule describes a validation rule written in the CEL expression language.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message represents the message displayed when validation fails. The message is required if the Rule contains line breaks. The message must not contain line breaks. If unset, the message is &#34;failed rule: {Rule}&#34;. e.g. &#34;must be a URL with the host matching spec.host&#34;</TD></TR>
+<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>Rule represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec The Rule is scoped to the location of the x-kubernetes-validations extension in the schema. The `self` variable in the CEL expression is bound to the scoped value. Example: - Rule scoped to the root of a resource with a status subresource: {&#34;rule&#34;: &#34;self.status.actual &lt;= self.spec.maxDesired&#34;}  If the Rule is scoped to an object with properties, the accessible properties of the object are field selectable via `self.field` and field presence can be checked via `has(self.field)`. Null valued fields are treated as absent fields in CEL expressions. If the Rule is scoped to an object with additionalProperties (i.e. a map) the value of the map are accessible via `self[mapKey]`, map containment can be checked via `mapKey in self` and all entries of the map are accessible via CEL macros and functions such as `self.all(...)`. If the Rule is scoped to an array, the elements of the array are accessible via `self[i]` and also by macros and functions. If the Rule is scoped to a scalar, `self` is bound to the scalar value. Examples: - Rule scoped to a map of objects: {&#34;rule&#34;: &#34;self.components[&#39;Widget&#39;].priority &lt; 10&#34;} - Rule scoped to a list of integers: {&#34;rule&#34;: &#34;self.values.all(value, value &gt;= 0 &amp;&amp; value &lt; 100)&#34;} - Rule scoped to a string value: {&#34;rule&#34;: &#34;self.startsWith(&#39;kube&#39;)&#34;}  The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object and from any x-kubernetes-embedded-resource annotated objects. No other metadata properties are accessible.  Unknown data preserved in custom resources via x-kubernetes-preserve-unknown-fields is not accessible in CEL expressions. This includes: - Unknown field values that are preserved by object schemas with x-kubernetes-preserve-unknown-fields. - Object properties where the property schema is of an &#34;unknown type&#34;. An &#34;unknown type&#34; is recursively defined as:   - A schema with no type and x-kubernetes-preserve-unknown-fields set to true   - An array where the items schema is of an &#34;unknown type&#34;   - An object where the additionalProperties schema is of an &#34;unknown type&#34;  Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - &#39;__&#39; escapes to &#39;__underscores__&#39; - &#39;.&#39; escapes to &#39;__dot__&#39; - &#39;-&#39; escapes to &#39;__dash__&#39; - &#39;/&#39; escapes to &#39;__slash__&#39; - Property names that exactly match a CEL RESERVED keyword escape to &#39;__{keyword}__&#39;. The keywords are: 	  &#34;true&#34;, &#34;false&#34;, &#34;null&#34;, &#34;in&#34;, &#34;as&#34;, &#34;break&#34;, &#34;const&#34;, &#34;continue&#34;, &#34;else&#34;, &#34;for&#34;, &#34;function&#34;, &#34;if&#34;, 	  &#34;import&#34;, &#34;let&#34;, &#34;loop&#34;, &#34;package&#34;, &#34;namespace&#34;, &#34;return&#34;. Examples:   - Rule accessing a property named &#34;namespace&#34;: {&#34;rule&#34;: &#34;self.__namespace__ &gt; 0&#34;}   - Rule accessing a property named &#34;x-prop&#34;: {&#34;rule&#34;: &#34;self.x__dash__prop &gt; 0&#34;}   - Rule accessing a property named &#34;redact__d&#34;: {&#34;rule&#34;: &#34;self.redact__underscores__d &gt; 0&#34;}  Equality on arrays with x-kubernetes-list-type of &#39;set&#39; or &#39;map&#39; ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type:   - &#39;set&#39;: `X + Y` performs a union where the array positions of all elements in `X` are preserved and     non-intersecting elements in `Y` are appended, retaining their partial order.   - &#39;map&#39;: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values     are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with     non-intersecting keys are appended, retaining their partial order.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumeattachmentsource-v1-storage-k8s-io">VolumeAttachmentSource v1 storage.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeAttachmentSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>inlineVolumeSpec</CODE><BR /><I><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec</a></I></TD><TD>inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod&#39;s inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod&#39;s inline VolumeSource to a PersistentVolumeSpec. This field is beta-level and is only honored by servers that enabled the CSIMigration feature.</TD></TR>
+<TR><TD><CODE>persistentVolumeName</CODE><BR /><I>string</I></TD><TD>Name of the persistent volume to attach.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumedevice-v1-core">VolumeDevice v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeDevice</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>volumeDevice describes a mapping of a raw block device within a container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>devicePath</CODE><BR /><I>string</I></TD><TD>devicePath is the path inside of the container that the device will be mapped to.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name must match the name of a persistentVolumeClaim in the pod</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumeerror-v1-storage-k8s-io">VolumeError v1 storage.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeError</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>VolumeError captures an error encountered during a volume operation.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#volumeattachmentstatus-v1-storage-k8s-io">VolumeAttachmentStatus [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.</TD></TR>
+<TR><TD><CODE>time</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time the error was encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumemount-v1-core">VolumeMount v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeMount</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>VolumeMount describes a mounting of a Volume within a container.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#container-v1-core">Container [core/v1]</a></LI>
+  <LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>mountPath</CODE><BR /><I>string</I></TD><TD>Path within the container at which the volume should be mounted.  Must not contain &#39;:&#39;.</TD></TR>
+<TR><TD><CODE>mountPropagation</CODE><BR /><I>string</I></TD><TD>mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationNone is used. This field is beta in 1.10.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>This must match the Name of a Volume.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.</TD></TR>
+<TR><TD><CODE>subPath</CODE><BR /><I>string</I></TD><TD>Path within the volume from which the container&#39;s volume should be mounted. Defaults to &#34;&#34; (volume&#39;s root).</TD></TR>
+<TR><TD><CODE>subPathExpr</CODE><BR /><I>string</I></TD><TD>Expanded path within the volume from which the container&#39;s volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container&#39;s environment. Defaults to &#34;&#34; (volume&#39;s root). SubPathExpr and SubPath are mutually exclusive.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumenodeaffinity-v1-core">VolumeNodeAffinity v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeNodeAffinity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>VolumeNodeAffinity defines constraints that limit what nodes this volume can be accessed from.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>required</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>Required specifies hard node constraints that must be met.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumenoderesources-v1-storage-k8s-io">VolumeNodeResources v1 storage.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeNodeResources</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>VolumeNodeResources is a set of resource limits for scheduling of volumes.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csinodedriver-v1-storage-k8s-io">CSINodeDriver [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Maximum number of unique volumes managed by the CSI driver that can be used on a node. A volume that is both attached and mounted on a node is considered to be used once, not twice. The same rule applies for a unique volume that is shared among multiple pods on the same node. If this field is not specified, then the supported number of volumes on this node is unbounded.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="volumeprojection-v1-core">VolumeProjection v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeProjection</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Projection that may be projected along with other supported volume types</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#projectedvolumesource-v1-core">ProjectedVolumeSource [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapprojection-v1-core">ConfigMapProjection</a></I></TD><TD>information about the configMap data to project</TD></TR>
+<TR><TD><CODE>downwardAPI</CODE><BR /><I><a href="#downwardapiprojection-v1-core">DownwardAPIProjection</a></I></TD><TD>information about the downwardAPI data to project</TD></TR>
+<TR><TD><CODE>secret</CODE><BR /><I><a href="#secretprojection-v1-core">SecretProjection</a></I></TD><TD>information about the secret data to project</TD></TR>
+<TR><TD><CODE>serviceAccountToken</CODE><BR /><I><a href="#serviceaccounttokenprojection-v1-core">ServiceAccountTokenProjection</a></I></TD><TD>information about the serviceAccountToken data to project</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VsphereVirtualDiskVolumeSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Represents a vSphere volume resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
+  <LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
+<TR><TD><CODE>storagePolicyID</CODE><BR /><I>string</I></TD><TD>Storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.</TD></TR>
+<TR><TD><CODE>storagePolicyName</CODE><BR /><I>string</I></TD><TD>Storage Policy Based Management (SPBM) profile name.</TD></TR>
+<TR><TD><CODE>volumePath</CODE><BR /><I>string</I></TD><TD>Path that identifies vSphere volume vmdk</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watchevent-v1-meta">WatchEvent v1 meta</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WatchEvent</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Event represents a single event to a watched resource.</P>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>object</CODE></TD><TD>Object is:  * If Type is Added or Modified: the new state of the object.  * If Type is Deleted: the state of the object immediately before deletion.  * If Type is Error: *Status is recommended; other types may make sense    depending on context.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="webhookclientconfig-v1-admissionregistration-k8s-io">WebhookClientConfig v1 admissionregistration.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WebhookClientConfig</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>WebhookClientConfig contains the information to make a TLS connection with the webhook</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
+  <LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook&#39;s server certificate. If unspecified, system trust roots on the apiserver are used.</TD></TR>
+<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-admissionregistration-k8s-io">ServiceReference</a></I></TD><TD>`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.  If the webhook is running within the cluster, then you should use `service`.</TD></TR>
+<TR><TD><CODE>url</CODE><BR /><I>string</I></TD><TD>`url` gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.  The `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.  Please note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.  The scheme must be &#34;https&#34;; the URL must begin with &#34;https://&#34;.  A path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.  Attempting to use a user or basic auth e.g. &#34;user:password@&#34; is not allowed. Fragments (&#34;#...&#34;) and query parameters (&#34;?...&#34;) are not allowed, either.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="webhookconversion-v1-apiextensions-k8s-io">WebhookConversion v1 apiextensions.k8s.io</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WebhookConversion</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>WebhookConversion describes how to call a conversion webhook</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#customresourceconversion-v1-apiextensions-k8s-io">CustomResourceConversion [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1-apiextensions-k8s-io">WebhookClientConfig</a></I></TD><TD>clientConfig is the instructions for how to call the webhook if strategy is `Webhook`.</TD></TR>
+<TR><TD><CODE>conversionReviewVersions</CODE><BR /><I>string array</I></TD><TD>conversionReviewVersions is an ordered list of preferred `ConversionReview` versions the Webhook expects. The API server will use the first version in the list which it supports. If none of the versions specified in this list are supported by API server, conversion will fail for the custom resource. If a persisted Webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WeightedPodAffinityTerm</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>The weights of all of the matched WeightedPodAffinityTerm fields are added per-node to find the most preferred node(s)</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podaffinity-v1-core">PodAffinity [core/v1]</a></LI>
+  <LI><a href="#podantiaffinity-v1-core">PodAntiAffinity [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>podAffinityTerm</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a></I></TD><TD>Required. A pod affinity term, associated with the corresponding weight.</TD></TR>
+<TR><TD><CODE>weight</CODE><BR /><I>integer</I></TD><TD>weight associated with matching the corresponding podAffinityTerm, in the range 1-100.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="windowssecuritycontextoptions-v1-core">WindowsSecurityContextOptions v1 core</H2>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WindowsSecurityContextOptions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>WindowsSecurityContextOptions contain Windows-specific options and credentials.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
+  <LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>gmsaCredentialSpec</CODE><BR /><I>string</I></TD><TD>GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.</TD></TR>
+<TR><TD><CODE>gmsaCredentialSpecName</CODE><BR /><I>string</I></TD><TD>GMSACredentialSpecName is the name of the GMSA credential spec to use.</TD></TR>
+<TR><TD><CODE>hostProcess</CODE><BR /><I>boolean</I></TD><TD>HostProcess determines if a container should be run as a &#39;Host Process&#39; container. This field is alpha-level and will only be honored by components that enable the WindowsHostProcessContainers feature flag. Setting this field without the feature flag will result in errors when validating the Pod. All of a Pod&#39;s containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers).  In addition, if HostProcess is true then HostNetwork must also be set to true.</TD></TR>
+<TR><TD><CODE>runAsUserName</CODE><BR /><I>string</I></TD><TD>The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="-strong-old-api-versions-strong-"><STRONG>OLD API VERSIONS</STRONG></H1>
+
+<P>This section contains older versions of resources shown above.</P>
+<H1 id="csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity v1alpha1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>CSIStorageCapacity</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#csistoragecapacity-v1beta1-storage-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csistoragecapacitylist-v1alpha1-storage-k8s-io">CSIStorageCapacityList [storage/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>capacity</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.  The semantic is currently (CSI spec 1.2) defined as: The available capacity, in bytes, of the storage that can be used to provision volumes. If not set, that information is currently unavailable and treated like zero capacity.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>maximumVolumeSize</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.  This is defined since CSI spec 1.4.0 as the largest size that may be used in a CreateVolumeRequest.capacity_range.required_bytes field to create a volume with the same parameters as those in GetCapacityRequest. The corresponding value in the Kubernetes API is ResourceRequirements.Requests in a volume claim.</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. The name has no particular meaning. It must be be a DNS subdomain (dots allowed, 253 characters). To ensure that there are no conflicts with other CSI drivers on the cluster, the recommendation is to use csisc-&lt;uuid&gt;, a generated name, or a reverse-domain name which ends with the unique CSI driver name.  Objects are namespaced.  More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>nodeTopology</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>NodeTopology defines which nodes have access to the storage for which capacity was reported. If not set, the storage is not accessible from any node in the cluster. If empty, the storage is accessible from all nodes. This field is immutable.</TD></TR>
+<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>The name of the StorageClass that the reported capacity applies to. It must meet the same requirements as the name of a StorageClass object (non-empty, DNS subdomain). If that object no longer exists, the CSIStorageCapacity object is obsolete and should be removed by its creator. This field is immutable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="csistoragecapacitylist-v1alpha1-storage-k8s-io">CSIStorageCapacityList v1alpha1 storage</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a> array</I></TD><TD>Items is the list of CSIStorageCapacity objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-csistoragecapacity-v1alpha1-storage-k8s-io">Create</H2>
+<P>create a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-csistoragecapacity-v1alpha1-storage-k8s-io">Patch</H2>
+<P>partially update the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-csistoragecapacity-v1alpha1-storage-k8s-io">Replace</H2>
+<P>replace the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-csistoragecapacity-v1alpha1-storage-k8s-io">Delete</H2>
+<P>delete a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-csistoragecapacity-v1alpha1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-csistoragecapacity-v1alpha1-storage-k8s-io">Read</H2>
+<P>read the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacity-v1alpha1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-csistoragecapacity-v1alpha1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1alpha1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/csistoragecapacities</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1alpha1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-csistoragecapacity-v1alpha1-storage-k8s-io">Watch</H2>
+<P>watch changes to an object of kind CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/watch/namespaces/{namespace}/csistoragecapacities/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-csistoragecapacity-v1alpha1-storage-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/watch/namespaces/{namespace}/csistoragecapacities</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1alpha1/watch/csistoragecapacities</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="containerresourcemetricsource-v2beta2-autoscaling">ContainerResourceMetricSource v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ContainerResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricsource-v2-autoscaling">v2</a>
+<a href="#containerresourcemetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta2-autoscaling">MetricSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2beta2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="containerresourcemetricsource-v2beta1-autoscaling">ContainerResourceMetricSource v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ContainerResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricsource-v2-autoscaling">v2</a>
+<a href="#containerresourcemetricsource-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>targetAverageUtilization</CODE><BR /><I>integer</I></TD><TD>targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.</TD></TR>
+<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="containerresourcemetricstatus-v2beta2-autoscaling">ContainerResourceMetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ContainerResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricstatus-v2-autoscaling">v2</a>
+<a href="#containerresourcemetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta2-autoscaling">MetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>Container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="containerresourcemetricstatus-v2beta1-autoscaling">ContainerResourceMetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ContainerResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#containerresourcemetricstatus-v2-autoscaling">v2</a>
+<a href="#containerresourcemetricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
+<TR><TD><CODE>currentAverageUtilization</CODE><BR /><I>integer</I></TD><TD>currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.</TD></TR>
+<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type. It will always be set, regardless of the corresponding metric specification.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="cronjob-v1beta1-batch">CronJob v1beta1 batch</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CronJob</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#cronjob-v1-batch">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjoblist-v1beta1-batch">CronJobList [batch/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#cronjobspec-v1beta1-batch">CronJobSpec</a></I></TD><TD>Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#cronjobstatus-v1beta1-batch">CronJobStatus</a></I></TD><TD>Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjobspec-v1beta1-batch">CronJobSpec v1beta1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>concurrencyPolicy</CODE><BR /><I>string</I></TD><TD>Specifies how to treat concurrent executions of a Job. Valid values are: - &#34;Allow&#34; (default): allows CronJobs to run concurrently; - &#34;Forbid&#34;: forbids concurrent runs, skipping next run if previous run hasn&#39;t finished yet; - &#34;Replace&#34;: cancels currently running job and replaces it with a new one</TD></TR>
+<TR><TD><CODE>failedJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of failed finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
+<TR><TD><CODE>jobTemplate</CODE><BR /><I><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec</a></I></TD><TD>Specifies the job that will be created when executing a CronJob.</TD></TR>
+<TR><TD><CODE>schedule</CODE><BR /><I>string</I></TD><TD>The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.</TD></TR>
+<TR><TD><CODE>startingDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>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.</TD></TR>
+<TR><TD><CODE>successfulJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of successful finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 3.</TD></TR>
+<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>This flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjobstatus-v1beta1-batch">CronJobStatus v1beta1 batch</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>active</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I></TD><TD>A list of pointers to currently running jobs.</TD></TR>
+<TR><TD><CODE>lastScheduleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job was successfully scheduled.</TD></TR>
+<TR><TD><CODE>lastSuccessfulTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job successfully completed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="cronjoblist-v1beta1-batch">CronJobList v1beta1 batch</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#cronjob-v1beta1-batch">CronJob</a> array</I></TD><TD>items is the list of CronJobs.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-cronjob-v1beta1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-cronjob-v1beta1-batch">Create</H2>
+<P>create a CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-cronjob-v1beta1-batch">Patch</H2>
+<P>partially update the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-cronjob-v1beta1-batch">Replace</H2>
+<P>replace the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-cronjob-v1beta1-batch">Delete</H2>
+<P>delete a CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-cronjob-v1beta1-batch">Delete Collection</H2>
+<P>delete collection of CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-cronjob-v1beta1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-cronjob-v1beta1-batch">Read</H2>
+<P>read the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-cronjob-v1beta1-batch">List</H2>
+<P>list or watch objects of kind CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjoblist-v1beta1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-cronjob-v1beta1-batch">List All Namespaces</H2>
+<P>list or watch objects of kind CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/cronjobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjoblist-v1beta1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-cronjob-v1beta1-batch">Watch</H2>
+<P>watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/watch/namespaces/{namespace}/cronjobs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-cronjob-v1beta1-batch">Watch List</H2>
+<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/watch/namespaces/{namespace}/cronjobs</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-cronjob-v1beta1-batch">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/watch/cronjobs</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-cronjob-v1beta1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-cronjob-v1beta1-batch">Patch Status</H2>
+<P>partially update status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-cronjob-v1beta1-batch">Read Status</H2>
+<P>read status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-cronjob-v1beta1-batch">Replace Status</H2>
+<P>replace status of the specified CronJob</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="crossversionobjectreference-v2-autoscaling">CrossVersionObjectReference v2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#crossversionobjectreference-v1-autoscaling">v1</a>
+<a href="#crossversionobjectreference-v2beta2-autoscaling">v2beta2</a>
+<a href="#crossversionobjectreference-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="crossversionobjectreference-v2beta2-autoscaling">CrossVersionObjectReference v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#crossversionobjectreference-v1-autoscaling">v1</a>
+<a href="#crossversionobjectreference-v2-autoscaling">v2</a>
+<a href="#crossversionobjectreference-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2beta2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta2-autoscaling">ObjectMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta2-autoscaling">ObjectMetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#crossversionobjectreference-v1-autoscaling">v1</a>
+<a href="#crossversionobjectreference-v2-autoscaling">v2</a>
+<a href="#crossversionobjectreference-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource [autoscaling/v2beta1]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds&#34;</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpoint-v1beta1-discovery-k8s-io">Endpoint v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Endpoint</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpoint-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addresses</CODE><BR /><I>string array</I></TD><TD>addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100.</TD></TR>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#endpointconditions-v1beta1-discovery-k8s-io">EndpointConditions</a></I></TD><TD>conditions contains information about the current status of the endpoint.</TD></TR>
+<TR><TD><CODE>hints</CODE><BR /><I><a href="#endpointhints-v1beta1-discovery-k8s-io">EndpointHints</a></I></TD><TD>hints contains information associated with how an endpoint should be consumed.</TD></TR>
+<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.</TD></TR>
+<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>nodeName represents the name of the Node hosting this endpoint. This can be used to determine endpoints local to a Node. This field can be enabled with the EndpointSliceNodeName feature gate.</TD></TR>
+<TR><TD><CODE>targetRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>targetRef is a reference to a Kubernetes object that represents this endpoint.</TD></TR>
+<TR><TD><CODE>topology</CODE><BR /><I>object</I></TD><TD>topology contains arbitrary topology information associated with the endpoint. These key/value pairs must conform with the label format. https://kubernetes.io/docs/concepts/overview/working-with-objects/labels Topology may include a maximum of 16 key/value pairs. This includes, but is not limited to the following well known keys: * kubernetes.io/hostname: the value indicates the hostname of the node   where the endpoint is located. This should match the corresponding   node label. * topology.kubernetes.io/zone: the value indicates the zone where the   endpoint is located. This should match the corresponding node label. * topology.kubernetes.io/region: the value indicates the region where the   endpoint is located. This should match the corresponding node label. This field is deprecated and will be removed in future api versions.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointconditions-v1beta1-discovery-k8s-io">EndpointConditions v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EndpointConditions</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointconditions-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpoint-v1beta1-discovery-k8s-io">Endpoint [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be &#34;true&#34; for terminating endpoints.</TD></TR>
+<TR><TD><CODE>serving</CODE><BR /><I>boolean</I></TD><TD>serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.</TD></TR>
+<TR><TD><CODE>terminating</CODE><BR /><I>boolean</I></TD><TD>terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointhints-v1beta1-discovery-k8s-io">EndpointHints v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EndpointHints</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointhints-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpoint-v1beta1-discovery-k8s-io">Endpoint [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>forZones</CODE><BR /><I><a href="#forzone-v1beta1-discovery-k8s-io">ForZone</a> array</I></TD><TD>forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing. May contain a maximum of 8 entries.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointport-v1-discovery-k8s-io">EndpointPort v1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointport-v1beta1-discovery-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or &#39;-&#39;. * must start and end with an alphanumeric character. Default is empty string.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointport-v1beta1-discovery-k8s-io">EndpointPort v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EndpointPort</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointport-v1-core">v1</a>
+<a href="#endpointport-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or &#39;-&#39;. * must start and end with an alphanumeric character. Default is empty string.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="endpointslice-v1beta1-discovery-k8s-io">EndpointSlice v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EndpointSlice</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#endpointslice-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointslicelist-v1beta1-discovery-k8s-io">EndpointSliceList [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>addressType</CODE><BR /><I>string</I></TD><TD>addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>endpoints</CODE><BR /><I><a href="#endpoint-v1beta1-discovery-k8s-io">Endpoint</a> array</I></TD><TD>endpoints is a list of unique endpoints in this slice. Each slice may include a maximum of 1000 endpoints.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#endpointport-v1beta1-discovery-k8s-io">EndpointPort</a> array</I></TD><TD>ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates &#34;all ports&#34;. Each slice may include a maximum of 100 ports.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="endpointslicelist-v1beta1-discovery-k8s-io">EndpointSliceList v1beta1 discovery</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a> array</I></TD><TD>List of endpoint slices</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-endpointslice-v1beta1-discovery-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-endpointslice-v1beta1-discovery-k8s-io">Create</H2>
+<P>create an EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-endpointslice-v1beta1-discovery-k8s-io">Patch</H2>
+<P>partially update the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-endpointslice-v1beta1-discovery-k8s-io">Replace</H2>
+<P>replace the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-endpointslice-v1beta1-discovery-k8s-io">Delete</H2>
+<P>delete an EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-endpointslice-v1beta1-discovery-k8s-io">Delete Collection</H2>
+<P>delete collection of EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-endpointslice-v1beta1-discovery-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-endpointslice-v1beta1-discovery-k8s-io">Read</H2>
+<P>read the specified EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslice-v1beta1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-endpointslice-v1beta1-discovery-k8s-io">List</H2>
+<P>list or watch objects of kind EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslicelist-v1beta1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind EndpointSlice</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/endpointslices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#endpointslicelist-v1beta1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-endpointslice-v1beta1-discovery-k8s-io">Watch</H2>
+<P>watch changes to an object of kind EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/watch/namespaces/{namespace}/endpointslices/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-endpointslice-v1beta1-discovery-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/watch/namespaces/{namespace}/endpointslices</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/discovery.k8s.io/v1beta1/watch/endpointslices</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="event-v1-core">Event v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Event</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#event-v1beta1-events-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#eventlist-v1-core">EventList [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>action</CODE><BR /><I>string</I></TD><TD>What action was taken/failed regarding to the Regarding object.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>The number of times this event has occurred.</TD></TR>
+<TR><TD><CODE>eventTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Time when this Event was first observed.</TD></TR>
+<TR><TD><CODE>firstTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The time at which the event was first recorded. (Time of server receipt is in TypeMeta.)</TD></TR>
+<TR><TD><CODE>involvedObject</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>The object that this event is about.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>lastTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The time at which the most recent occurrence of this event was recorded.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the status of this operation.</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>This should be a short, machine understandable string that gives the reason for the transition into the object&#39;s current status.</TD></TR>
+<TR><TD><CODE>related</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>Optional secondary object for more complex actions.</TD></TR>
+<TR><TD><CODE>reportingComponent</CODE><BR /><I>string</I></TD><TD>Name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`.</TD></TR>
+<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>ID of the controller instance, e.g. `kubelet-xyzf`.</TD></TR>
+<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1-core">EventSeries</a></I></TD><TD>Data about the Event series this event represents or nil if it&#39;s a singleton Event.</TD></TR>
+<TR><TD><CODE>source</CODE><BR /><I><a href="#eventsource-v1-core">EventSource</a></I></TD><TD>The component reporting this event. Should be a short machine understandable string.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of this event (Normal, Warning), new types could be added in the future</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="eventlist-v1-core">EventList v1 core</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1-core">Event</a> array</I></TD><TD>List of events</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-event-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-event-v1-core">Create</H2>
+<P>create an Event</P>
+<H3>HTTP Request</H3>
+<CODE>POST /api/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-core">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-event-v1-core">Patch</H2>
+<P>partially update the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /api/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-event-v1-core">Replace</H2>
+<P>replace the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /api/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-core">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-event-v1-core">Delete</H2>
+<P>delete an Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-event-v1-core">Delete Collection</H2>
+<P>delete collection of Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /api/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-event-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-event-v1-core">Read</H2>
+<P>read the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-event-v1-core">List</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1-core">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-event-v1-core">List All Namespaces</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1-core">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-event-v1-core">Watch</H2>
+<P>watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-event-v1-core">Watch List</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-event-v1-core">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /api/v1/watch/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="event-v1beta1-events-k8s-io">Event v1beta1 events.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Event</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#event-v1-events-k8s-io">v1</a>
+<a href="#event-v1-core">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#eventlist-v1beta1-events-k8s-io">EventList [events/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>action</CODE><BR /><I>string</I></TD><TD>action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>deprecatedCount</CODE><BR /><I>integer</I></TD><TD>deprecatedCount is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedFirstTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>deprecatedFirstTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedLastTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>deprecatedLastTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>deprecatedSource</CODE><BR /><I><a href="#eventsource-v1-core">EventSource</a></I></TD><TD>deprecatedSource is the deprecated field assuring backward compatibility with core.v1 Event type.</TD></TR>
+<TR><TD><CODE>eventTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>eventTime is the time when this Event was first observed. It is required.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>note</CODE><BR /><I>string</I></TD><TD>note is a human-readable description of the status of this operation. Maximal length of the note is 1kB, but libraries should be prepared to handle values up to 64kB.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is why the action was taken. It is human-readable. This field can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>regarding</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>regarding contains the object this Event is about. In most cases it&#39;s an Object reporting controller implements, e.g. ReplicaSetController implements ReplicaSets and this event is emitted because it acts on some changes in a ReplicaSet object.</TD></TR>
+<TR><TD><CODE>related</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>related is the optional secondary object for more complex actions. E.g. when regarding object triggers a creation or deletion of related object.</TD></TR>
+<TR><TD><CODE>reportingController</CODE><BR /><I>string</I></TD><TD>reportingController is the name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`. This field cannot be empty for new Events.</TD></TR>
+<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>reportingInstance is the ID of the controller instance, e.g. `kubelet-xyzf`. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
+<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1beta1-events-k8s-io">EventSeries</a></I></TD><TD>series is data about the Event series this event represents or nil if it&#39;s a singleton Event.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of this event (Normal, Warning), new types could be added in the future. It is machine-readable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="eventlist-v1beta1-events-k8s-io">EventList v1beta1 events</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1beta1-events-k8s-io">Event</a> array</I></TD><TD>items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-event-v1beta1-events-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-event-v1beta1-events-k8s-io">Create</H2>
+<P>create an Event</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-event-v1beta1-events-k8s-io">Patch</H2>
+<P>partially update the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-event-v1beta1-events-k8s-io">Replace</H2>
+<P>replace the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-event-v1beta1-events-k8s-io">Delete</H2>
+<P>delete an Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-event-v1beta1-events-k8s-io">Delete Collection</H2>
+<P>delete collection of Event</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-event-v1beta1-events-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-event-v1beta1-events-k8s-io">Read</H2>
+<P>read the specified Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-event-v1beta1-events-k8s-io">List</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1beta1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-event-v1beta1-events-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind Event</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#eventlist-v1beta1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-event-v1beta1-events-k8s-io">Watch</H2>
+<P>watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/watch/namespaces/{namespace}/events/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-event-v1beta1-events-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/watch/namespaces/{namespace}/events</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-event-v1beta1-events-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/events.k8s.io/v1beta1/watch/events</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="eventseries-v1-core">EventSeries v1 core</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EventSeries</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#eventseries-v1beta1-events-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#event-v1-core">Event [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Number of occurrences in this series up to the last heartbeat time</TD></TR>
+<TR><TD><CODE>lastObservedTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Time of the last occurrence observed</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="eventseries-v1beta1-events-k8s-io">EventSeries v1beta1 events.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EventSeries</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#eventseries-v1-events-k8s-io">v1</a>
+<a href="#eventseries-v1-core">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>count is the number of occurrences in this series up to the last heartbeat time.</TD></TR>
+<TR><TD><CODE>lastObservedTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>lastObservedTime is the time when last Event from the series was seen before last heartbeat.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="externalmetricsource-v2beta2-autoscaling">ExternalMetricSource v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ExternalMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricsource-v2-autoscaling">v2</a>
+<a href="#externalmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta2-autoscaling">MetricSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2beta2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="externalmetricsource-v2beta1-autoscaling">ExternalMetricSource v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ExternalMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricsource-v2-autoscaling">v2</a>
+<a href="#externalmetricsource-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
+<TR><TD><CODE>metricSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>metricSelector is used to identify a specific time series within a given metric.</TD></TR>
+<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target per-pod value of global metric (as a quantity). Mutually exclusive with TargetValue.</TD></TR>
+<TR><TD><CODE>targetValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="externalmetricstatus-v2beta2-autoscaling">ExternalMetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ExternalMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricstatus-v2-autoscaling">v2</a>
+<a href="#externalmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta2-autoscaling">MetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ExternalMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#externalmetricstatus-v2-autoscaling">v2</a>
+<a href="#externalmetricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of metric averaged over autoscaled pods.</TD></TR>
+<TR><TD><CODE>currentValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentValue is the current value of the metric (as a quantity)</TD></TR>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of a metric used for autoscaling in metric system.</TD></TR>
+<TR><TD><CODE>metricSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>metricSelector is used to identify a specific time series within a given metric.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FlowDistinguisherMethod</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of flow distinguisher method The supported types are &#34;ByUser&#34; and &#34;ByNamespace&#34;. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FlowSchema</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#flowschemastatus-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus</a></I></TD><TD>`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>distinguisherMethod</CODE><BR /><I><a href="#flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod</a></I></TD><TD>`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.</TD></TR>
+<TR><TD><CODE>matchingPrecedence</CODE><BR /><I>integer</I></TD><TD>`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence.  Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.</TD></TR>
+<TR><TD><CODE>priorityLevelConfiguration</CODE><BR /><I><a href="#prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference</a></I></TD><TD>`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects</a> array</I></TD><TD>`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemastatus-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition</a> array</I></TD><TD>`conditions` is a list of the current states of FlowSchema.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList v1beta1 flowcontrol</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a> array</I></TD><TD>`items` is a list of FlowSchemas.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>`metadata` is the standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">List</H2>
+<P>list or watch objects of kind FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschemalist-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Watch</H2>
+<P>watch changes to an object of kind FlowSchema. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/flowschemas/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of FlowSchema. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/flowschemas</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Patch Status</H2>
+<P>partially update status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Read Status</H2>
+<P>read status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io">Replace Status</H2>
+<P>replace status of the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/flowschemas/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FlowSchemaCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemastatus-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>`lastTransitionTime` is the last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>`message` is a human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>`status` is the status of the condition. Can be True, False, Unknown. Required.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="forzone-v1beta1-discovery-k8s-io">ForZone v1beta1 discovery.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ForZone</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#forzone-v1-discovery-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#endpointhints-v1beta1-discovery-k8s-io">EndpointHints [discovery/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name represents the name of the zone.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="groupsubject-v1beta1-flowcontrol-apiserver-k8s-io">GroupSubject v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>GroupSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#groupsubject-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the user group that matches, or &#34;*&#34; to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="hpascalingpolicy-v2beta2-autoscaling">HPAScalingPolicy v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>HPAScalingPolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#hpascalingpolicy-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#hpascalingrules-v2beta2-autoscaling">HPAScalingRules [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>periodSeconds</CODE><BR /><I>integer</I></TD><TD>PeriodSeconds specifies the window of time for which the policy should hold true. PeriodSeconds must be greater than zero and less than or equal to 1800 (30 min).</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is used to specify the scaling policy.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>Value contains the amount of change which is permitted by the policy. It must be greater than zero</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="hpascalingrules-v2beta2-autoscaling">HPAScalingRules v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>HPAScalingRules</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#hpascalingrules-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerbehavior-v2beta2-autoscaling">HorizontalPodAutoscalerBehavior [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policies</CODE><BR /><I><a href="#hpascalingpolicy-v2beta2-autoscaling">HPAScalingPolicy</a> array</I></TD><TD>policies is a list of potential scaling polices which can be used during scaling. At least one policy must be specified, otherwise the HPAScalingRules will be discarded as invalid</TD></TR>
+<TR><TD><CODE>selectPolicy</CODE><BR /><I>string</I></TD><TD>selectPolicy is used to specify which policy should be used. If not set, the default value MaxPolicySelect is used.</TD></TR>
+<TR><TD><CODE>stabilizationWindowSeconds</CODE><BR /><I>integer</I></TD><TD>StabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler v1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscaler-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscaler-v2beta2-autoscaling">v2beta2</a>
+<a href="#horizontalpodautoscaler-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>current information about the autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec v1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.</TD></TR>
+<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.</TD></TR>
+<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource.</TD></TR>
+<TR><TD><CODE>targetCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus v1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>currentCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU.</TD></TR>
+<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>current number of replicas of pods managed by this autoscaler.</TD></TR>
+<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desired number of replicas of pods managed by this autoscaler.</TD></TR>
+<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>most recent generation observed by this autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList v1 autoscaling</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>list of horizontal pod autoscaler objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-horizontalpodautoscaler-v1-autoscaling">Create</H2>
+<P>create a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-horizontalpodautoscaler-v1-autoscaling">Patch</H2>
+<P>partially update the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-horizontalpodautoscaler-v1-autoscaling">Replace</H2>
+<P>replace the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-horizontalpodautoscaler-v1-autoscaling">Delete</H2>
+<P>delete a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-horizontalpodautoscaler-v1-autoscaling">Delete Collection</H2>
+<P>delete collection of HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-horizontalpodautoscaler-v1-autoscaling">Read</H2>
+<P>read the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-horizontalpodautoscaler-v1-autoscaling">List</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">List All Namespaces</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-horizontalpodautoscaler-v1-autoscaling">Watch</H2>
+<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-horizontalpodautoscaler-v1-autoscaling">Watch List</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/watch/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-horizontalpodautoscaler-v1-autoscaling">Patch Status</H2>
+<P>partially update status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-horizontalpodautoscaler-v1-autoscaling">Read Status</H2>
+<P>read status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-horizontalpodautoscaler-v1-autoscaling">Replace Status</H2>
+<P>replace status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscaler-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscaler-v1-autoscaling">v1</a>
+<a href="#horizontalpodautoscaler-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerlist-v2beta2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v2beta2-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v2beta2-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>status is the current information about the autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerspec-v2beta2-autoscaling">HorizontalPodAutoscalerSpec v2beta2 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>behavior</CODE><BR /><I><a href="#horizontalpodautoscalerbehavior-v2beta2-autoscaling">HorizontalPodAutoscalerBehavior</a></I></TD><TD>behavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively). If not set, the default HPAScalingRules for scale up and scale down are used.</TD></TR>
+<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.</TD></TR>
+<TR><TD><CODE>metrics</CODE><BR /><I><a href="#metricspec-v2beta2-autoscaling">MetricSpec</a> array</I></TD><TD>metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used).  The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods.  Ergo, metrics used must decrease as the pod count is increased, and vice-versa.  See the individual metric source types for more information about how each type of metric must respond. If not set, the default metric will be set to 80% average CPU utilization.</TD></TR>
+<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.</TD></TR>
+<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v2beta2-autoscaling">CrossVersionObjectReference</a></I></TD><TD>scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerstatus-v2beta2-autoscaling">HorizontalPodAutoscalerStatus v2beta2 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#horizontalpodautoscalercondition-v2beta2-autoscaling">HorizontalPodAutoscalerCondition</a> array</I></TD><TD>conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.</TD></TR>
+<TR><TD><CODE>currentMetrics</CODE><BR /><I><a href="#metricstatus-v2beta2-autoscaling">MetricStatus</a> array</I></TD><TD>currentMetrics is the last read state of the metrics used by this autoscaler.</TD></TR>
+<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.</TD></TR>
+<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.</TD></TR>
+<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed by this autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerlist-v2beta2-autoscaling">HorizontalPodAutoscalerList v2beta2 autoscaling</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>items is the list of horizontal pod autoscaler objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>metadata is the standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-horizontalpodautoscaler-v2beta2-autoscaling">Create</H2>
+<P>create a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-horizontalpodautoscaler-v2beta2-autoscaling">Patch</H2>
+<P>partially update the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-horizontalpodautoscaler-v2beta2-autoscaling">Replace</H2>
+<P>replace the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-horizontalpodautoscaler-v2beta2-autoscaling">Delete</H2>
+<P>delete a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-horizontalpodautoscaler-v2beta2-autoscaling">Delete Collection</H2>
+<P>delete collection of HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-horizontalpodautoscaler-v2beta2-autoscaling">Read</H2>
+<P>read the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-horizontalpodautoscaler-v2beta2-autoscaling">List</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling">List All Namespaces</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-horizontalpodautoscaler-v2beta2-autoscaling">Watch</H2>
+<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-horizontalpodautoscaler-v2beta2-autoscaling">Watch List</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/watch/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-horizontalpodautoscaler-v2beta2-autoscaling">Patch Status</H2>
+<P>partially update status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-horizontalpodautoscaler-v2beta2-autoscaling">Read Status</H2>
+<P>read status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-horizontalpodautoscaler-v2beta2-autoscaling">Replace Status</H2>
+<P>replace status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2beta2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscaler-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscaler-v1-autoscaling">v1</a>
+<a href="#horizontalpodautoscaler-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>status is the current information about the autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec v2beta1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.</TD></TR>
+<TR><TD><CODE>metrics</CODE><BR /><I><a href="#metricspec-v2beta1-autoscaling">MetricSpec</a> array</I></TD><TD>metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used).  The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods.  Ergo, metrics used must decrease as the pod count is increased, and vice-versa.  See the individual metric source types for more information about how each type of metric must respond.</TD></TR>
+<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.</TD></TR>
+<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus v2beta1 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition</a> array</I></TD><TD>conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.</TD></TR>
+<TR><TD><CODE>currentMetrics</CODE><BR /><I><a href="#metricstatus-v2beta1-autoscaling">MetricStatus</a> array</I></TD><TD>currentMetrics is the last read state of the metrics used by this autoscaler.</TD></TR>
+<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.</TD></TR>
+<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.</TD></TR>
+<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed by this autoscaler.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList v2beta1 autoscaling</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>items is the list of horizontal pod autoscaler objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>metadata is the standard list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-horizontalpodautoscaler-v2beta1-autoscaling">Create</H2>
+<P>create a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-horizontalpodautoscaler-v2beta1-autoscaling">Patch</H2>
+<P>partially update the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-horizontalpodautoscaler-v2beta1-autoscaling">Replace</H2>
+<P>replace the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-horizontalpodautoscaler-v2beta1-autoscaling">Delete</H2>
+<P>delete a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-horizontalpodautoscaler-v2beta1-autoscaling">Delete Collection</H2>
+<P>delete collection of HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-horizontalpodautoscaler-v2beta1-autoscaling">Read</H2>
+<P>read the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-horizontalpodautoscaler-v2beta1-autoscaling">List</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling">List All Namespaces</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-horizontalpodautoscaler-v2beta1-autoscaling">Watch</H2>
+<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-horizontalpodautoscaler-v2beta1-autoscaling">Watch List</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/watch/horizontalpodautoscalers</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-horizontalpodautoscaler-v2beta1-autoscaling">Patch Status</H2>
+<P>partially update status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-horizontalpodautoscaler-v2beta1-autoscaling">Read Status</H2>
+<P>read status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-horizontalpodautoscaler-v2beta1-autoscaling">Replace Status</H2>
+<P>replace status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscalerbehavior-v2beta2-autoscaling">HorizontalPodAutoscalerBehavior v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>HorizontalPodAutoscalerBehavior</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscalerbehavior-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2beta2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>scaleDown</CODE><BR /><I><a href="#hpascalingrules-v2beta2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleDown is scaling policy for scaling Down. If not set, the default value is to allow to scale down to minReplicas pods, with a 300 second stabilization window (i.e., the highest recommendation for the last 300sec is used).</TD></TR>
+<TR><TD><CODE>scaleUp</CODE><BR /><I><a href="#hpascalingrules-v2beta2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleUp is scaling policy for scaling Up. If not set, the default value is the higher of:   * increase no more than 4 pods per 60 seconds   * double the number of pods per 60 seconds No stabilization is used.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscalercondition-v2beta2-autoscaling">HorizontalPodAutoscalerCondition v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>HorizontalPodAutoscalerCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscalercondition-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the last time the condition transitioned from one status to another</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human-readable explanation containing details about the transition</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is the reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status is the status of the condition (True, False, Unknown)</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type describes the current condition</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>HorizontalPodAutoscalerCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#horizontalpodautoscalercondition-v2-autoscaling">v2</a>
+<a href="#horizontalpodautoscalercondition-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the last time the condition transitioned from one status to another</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human-readable explanation containing details about the transition</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is the reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status is the status of the condition (True, False, Unknown)</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type describes the current condition</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="jobtemplatespec-v1beta1-batch">JobTemplateSpec v1beta1 batch</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JobTemplateSpec</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#jobtemplatespec-v1-batch">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#cronjobspec-v1beta1-batch">CronJobSpec [batch/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="limitresponse-v1beta1-flowcontrol-apiserver-k8s-io">LimitResponse v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>LimitResponse</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#limitresponse-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>queuing</CODE><BR /><I><a href="#queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">QueuingConfiguration</a></I></TD><TD>`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `&#34;Queue&#34;`.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is &#34;Queue&#34; or &#34;Reject&#34;. &#34;Queue&#34; means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. &#34;Reject&#34; means that requests that can not be executed upon arrival are rejected. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>LimitedPriorityLevelConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationspec-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>assuredConcurrencyShares</CODE><BR /><I>integer</I></TD><TD>`assuredConcurrencyShares` (ACS) configures the execution limit, which is a limit on the number of requests of this priority level that may be exeucting at a given time.  ACS must be a positive number. The server&#39;s concurrency limit (SCL) is divided among the concurrency-controlled priority levels in proportion to their assured concurrency shares. This produces the assured concurrency value (ACV) --- the number of requests that may be executing at a time --- for each such priority level:              ACV(l) = ceil( SCL * ACS(l) / ( sum[priority levels k] ACS(k) ) )  bigger numbers of ACS mean more reserved concurrent requests (at the expense of every other PL). This field has a default value of 30.</TD></TR>
+<TR><TD><CODE>limitResponse</CODE><BR /><I><a href="#limitresponse-v1beta1-flowcontrol-apiserver-k8s-io">LimitResponse</a></I></TD><TD>`limitResponse` indicates what to do with requests that can not be executed right now</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricidentifier-v2beta2-autoscaling">MetricIdentifier v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>MetricIdentifier</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricidentifier-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#externalmetricsource-v2beta2-autoscaling">ExternalMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#externalmetricstatus-v2beta2-autoscaling">ExternalMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta2-autoscaling">ObjectMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta2-autoscaling">ObjectMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#podsmetricsource-v2beta2-autoscaling">PodsMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#podsmetricstatus-v2beta2-autoscaling">PodsMetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the given metric</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricspec-v2beta2-autoscaling">MetricSpec v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>MetricSpec</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricspec-v2-autoscaling">v2</a>
+<a href="#metricspec-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2beta2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricsource-v2beta2-autoscaling">ContainerResourceMetricSource</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricsource-v2beta2-autoscaling">ExternalMetricSource</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricsource-v2beta2-autoscaling">ObjectMetricSource</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricsource-v2beta2-autoscaling">PodsMetricSource</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricsource-v2beta2-autoscaling">ResourceMetricSource</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It should be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each mapping to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricspec-v2beta1-autoscaling">MetricSpec v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>MetricSpec</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricspec-v2-autoscaling">v2</a>
+<a href="#metricspec-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricsource-v2beta1-autoscaling">ContainerResourceMetricSource</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricsource-v2beta1-autoscaling">PodsMetricSource</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It should be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each mapping to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricstatus-v2beta2-autoscaling">MetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>MetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricstatus-v2-autoscaling">v2</a>
+<a href="#metricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricstatus-v2beta2-autoscaling">ContainerResourceMetricStatus</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricstatus-v2beta2-autoscaling">ExternalMetricStatus</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricstatus-v2beta2-autoscaling">ObjectMetricStatus</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricstatus-v2beta2-autoscaling">PodsMetricStatus</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricstatus-v2beta2-autoscaling">ResourceMetricStatus</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It will be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each corresponds to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricstatus-v2beta1-autoscaling">MetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>MetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricstatus-v2-autoscaling">v2</a>
+<a href="#metricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricstatus-v2beta1-autoscaling">ContainerResourceMetricStatus</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
+<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
+<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source.  It will be one of &#34;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each corresponds to a matching field in the object. Note: &#34;ContainerResource&#34; type is available on when the feature-gate HPAContainerMetrics is enabled</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metrictarget-v2beta2-autoscaling">MetricTarget v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>MetricTarget</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metrictarget-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerresourcemetricsource-v2beta2-autoscaling">ContainerResourceMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#externalmetricsource-v2beta2-autoscaling">ExternalMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricsource-v2beta2-autoscaling">ObjectMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#podsmetricsource-v2beta2-autoscaling">PodsMetricSource [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#resourcemetricsource-v2beta2-autoscaling">ResourceMetricSource [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageUtilization</CODE><BR /><I>integer</I></TD><TD>averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. Currently only valid for Resource metric source type</TD></TR>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type represents whether the metric type is Utilization, Value, or AverageValue</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the target value of the metric (as a quantity).</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="metricvaluestatus-v2beta2-autoscaling">MetricValueStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>MetricValueStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#metricvaluestatus-v2-autoscaling">v2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#containerresourcemetricstatus-v2beta2-autoscaling">ContainerResourceMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#externalmetricstatus-v2beta2-autoscaling">ExternalMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#objectmetricstatus-v2beta2-autoscaling">ObjectMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#podsmetricstatus-v2beta2-autoscaling">PodsMetricStatus [autoscaling/v2beta2]</a></LI>
+  <LI><a href="#resourcemetricstatus-v2beta2-autoscaling">ResourceMetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageUtilization</CODE><BR /><I>integer</I></TD><TD>currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.</TD></TR>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the current value of the metric (as a quantity).</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NonResourcePolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>`nonResourceURLs` is a set of url prefixes that a user should have access to and may not be empty. For example:   - &#34;/healthz&#34; is legal   - &#34;/hea*&#34; is illegal   - &#34;/hea&#34; is legal but matches nothing   - &#34;/hea/*&#34; also matches nothing   - &#34;/healthz/*&#34; matches all per-component health checks. &#34;*&#34; matches all non-resource urls. if it is present, it must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs. If it is present, it must be the only entry. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="objectmetricsource-v2beta2-autoscaling">ObjectMetricSource v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ObjectMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricsource-v2-autoscaling">v2</a>
+<a href="#objectmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta2-autoscaling">MetricSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2beta2-autoscaling">CrossVersionObjectReference</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2beta2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="objectmetricsource-v2beta1-autoscaling">ObjectMetricSource v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ObjectMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricsource-v2-autoscaling">v2</a>
+<a href="#objectmetricsource-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>target is the described Kubernetes object.</TD></TR>
+<TR><TD><CODE>targetValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetValue is the target value of the metric (as a quantity).</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="objectmetricstatus-v2beta2-autoscaling">ObjectMetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ObjectMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricstatus-v2-autoscaling">v2</a>
+<a href="#objectmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta2-autoscaling">MetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2beta2-autoscaling">CrossVersionObjectReference</a></I></TD><TD></TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ObjectMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#objectmetricstatus-v2-autoscaling">v2</a>
+<a href="#objectmetricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>currentValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentValue is the current value of the metric (as a quantity).</TD></TR>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the ObjectMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>target is the described Kubernetes object.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="overhead-v1beta1-node-k8s-io">Overhead v1beta1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Overhead</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#overhead-v1-node-k8s-io">v1</a>
+<a href="#overhead-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass [node/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>podFixed</CODE><BR /><I>object</I></TD><TD>PodFixed represents the fixed resource overhead associated with running a pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="overhead-v1alpha1-node-k8s-io">Overhead v1alpha1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Overhead</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#overhead-v1-node-k8s-io">v1</a>
+<a href="#overhead-v1beta1-node-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclassspec-v1alpha1-node-k8s-io">RuntimeClassSpec [node/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>podFixed</CODE><BR /><I>object</I></TD><TD>PodFixed represents the fixed resource overhead associated with running a pod.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="poddisruptionbudget-v1beta1-policy">PodDisruptionBudget v1beta1 policy</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PodDisruptionBudget</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#poddisruptionbudget-v1-policy">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec</a></I></TD><TD>Specification of the desired behavior of the PodDisruptionBudget.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#poddisruptionbudgetstatus-v1beta1-policy">PodDisruptionBudgetStatus</a></I></TD><TD>Most recently observed status of the PodDisruptionBudget.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec v1beta1 policy</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>maxUnavailable</CODE></TD><TD>An eviction is allowed if at most &#34;maxUnavailable&#34; pods selected by &#34;selector&#34; are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with &#34;minAvailable&#34;.</TD></TR>
+<TR><TD><CODE>minAvailable</CODE></TD><TD>An eviction is allowed if at least &#34;minAvailable&#34; pods selected by &#34;selector&#34; will still be available after the eviction, i.e. even in the absence of the evicted pod.  So for example you can prevent all voluntary evictions by specifying &#34;100%&#34;.</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I><BR /><B>patch strategy</B>: <I>replace</I></TD><TD>Label query over pods whose evictions are managed by the disruption budget. A null selector selects no pods. An empty selector ({}) also selects no pods, which differs from standard behavior of selecting all pods. In policy/v1, an empty selector will select all pods in the namespace.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetstatus-v1beta1-policy">PodDisruptionBudgetStatus v1beta1 policy</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#condition-v1-meta">Condition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn&#39;t able to compute               the number of allowed disruptions. Therefore no disruptions are               allowed and the status of the condition will be False. - InsufficientPods: The number of pods are either at or below the number                     required by the PodDisruptionBudget. No disruptions are                     allowed and the status of the condition will be False. - SufficientPods: There are more pods than required by the PodDisruptionBudget.                   The condition will be True, and the number of allowed                   disruptions are provided by the disruptionsAllowed property.</TD></TR>
+<TR><TD><CODE>currentHealthy</CODE><BR /><I>integer</I></TD><TD>current number of healthy pods</TD></TR>
+<TR><TD><CODE>desiredHealthy</CODE><BR /><I>integer</I></TD><TD>minimum desired number of healthy pods</TD></TR>
+<TR><TD><CODE>disruptedPods</CODE><BR /><I>object</I></TD><TD>DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn&#39;t occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.</TD></TR>
+<TR><TD><CODE>disruptionsAllowed</CODE><BR /><I>integer</I></TD><TD>Number of pod disruptions that are currently allowed.</TD></TR>
+<TR><TD><CODE>expectedPods</CODE><BR /><I>integer</I></TD><TD>total number of pods counted by this disruption budget</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>Most recent generation observed when updating this PDB status. DisruptionsAllowed and other status information is valid only if observedGeneration equals to PDB&#39;s object generation.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList v1beta1 policy</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a> array</I></TD><TD>items list individual PodDisruptionBudget objects</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-poddisruptionbudget-v1beta1-policy">Create</H2>
+<P>create a PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-poddisruptionbudget-v1beta1-policy">Patch</H2>
+<P>partially update the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-poddisruptionbudget-v1beta1-policy">Replace</H2>
+<P>replace the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-poddisruptionbudget-v1beta1-policy">Delete</H2>
+<P>delete a PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-poddisruptionbudget-v1beta1-policy">Delete Collection</H2>
+<P>delete collection of PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-poddisruptionbudget-v1beta1-policy">Read</H2>
+<P>read the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-poddisruptionbudget-v1beta1-policy">List</H2>
+<P>list or watch objects of kind PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-poddisruptionbudget-v1beta1-policy">List All Namespaces</H2>
+<P>list or watch objects of kind PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/poddisruptionbudgets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-poddisruptionbudget-v1beta1-policy">Watch</H2>
+<P>watch changes to an object of kind PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/watch/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-poddisruptionbudget-v1beta1-policy">Watch List</H2>
+<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/watch/namespaces/{namespace}/poddisruptionbudgets</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/watch/poddisruptionbudgets</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-poddisruptionbudget-v1beta1-policy">Patch Status</H2>
+<P>partially update status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-poddisruptionbudget-v1beta1-policy">Read Status</H2>
+<P>read status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-poddisruptionbudget-v1beta1-policy">Replace Status</H2>
+<P>replace status of the specified PodDisruptionBudget</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podsmetricsource-v2beta2-autoscaling">PodsMetricSource v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>PodsMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricsource-v2-autoscaling">v2</a>
+<a href="#podsmetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta2-autoscaling">MetricSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2beta2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podsmetricsource-v2beta1-autoscaling">PodsMetricSource v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>PodsMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricsource-v2-autoscaling">v2</a>
+<a href="#podsmetricsource-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.</TD></TR>
+<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podsmetricstatus-v2beta2-autoscaling">PodsMetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>PodsMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricstatus-v2-autoscaling">v2</a>
+<a href="#podsmetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta2-autoscaling">MetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2beta2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>PodsMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#podsmetricstatus-v2-autoscaling">v2</a>
+<a href="#podsmetricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
+<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question</TD></TR>
+<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the PodsMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PolicyRulesWithSubjects</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule</a> array</I></TD><TD>`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.</TD></TR>
+<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">ResourcePolicyRule</a> array</I></TD><TD>`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.</TD></TR>
+<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">Subject</a> array</I></TD><TD>subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PriorityLevelConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#prioritylevelconfigurationspec-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#prioritylevelconfigurationstatus-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus</a></I></TD><TD>`status` is the current status of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationspec-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>limited</CODE><BR /><I><a href="#limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration</a></I></TD><TD>`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `&#34;Limited&#34;`.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` indicates whether this priority level is subject to limitation on request execution.  A value of `&#34;Exempt&#34;` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels.  A value of `&#34;Limited&#34;` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server&#39;s limited capacity is made available exclusively to this priority level. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationstatus-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus v1beta1 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>conditions</CODE><BR /><I><a href="#prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition</a> array</I></TD><TD>`conditions` is the current state of &#34;request-priority&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList v1beta1 flowcontrol</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a> array</I></TD><TD>`items` is a list of request-priorities.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>`metadata` is the standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">List</H2>
+<P>list or watch objects of kind PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfigurationlist-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Watch</H2>
+<P>watch changes to an object of kind PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/prioritylevelconfigurations/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/watch/prioritylevelconfigurations</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Patch Status</H2>
+<P>partially update status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Read Status</H2>
+<P>read status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">Replace Status</H2>
+<P>replace status of the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta1/prioritylevelconfigurations/{name}/status</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PriorityLevelConfigurationCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfigurationstatus-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>`lastTransitionTime` is the last time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>`message` is a human-readable message indicating details about last transition.</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>`status` is the status of the condition. Can be True, False, Unknown. Required.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PriorityLevelConfigurationReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschemaspec-v1beta1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of the priority level configuration being referenced Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io">QueuingConfiguration v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>QueuingConfiguration</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#limitresponse-v1beta1-flowcontrol-apiserver-k8s-io">LimitResponse [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>handSize</CODE><BR /><I>integer</I></TD><TD>`handSize` is a small positive number that configures the shuffle sharding of requests into queues.  When enqueuing a request at this priority level the request&#39;s flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here.  The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues).  See the user-facing documentation for more extensive guidance on setting this field.  This field has a default value of 8.</TD></TR>
+<TR><TD><CODE>queueLengthLimit</CODE><BR /><I>integer</I></TD><TD>`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected.  This value must be positive.  If not specified, it will be defaulted to 50.</TD></TR>
+<TR><TD><CODE>queues</CODE><BR /><I>integer</I></TD><TD>`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive.  Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant.  This field has a default value of 64.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcemetricsource-v2beta2-autoscaling">ResourceMetricSource v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricsource-v2-autoscaling">v2</a>
+<a href="#resourcemetricsource-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta2-autoscaling">MetricSpec [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2beta2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ResourceMetricSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricsource-v2-autoscaling">v2</a>
+<a href="#resourcemetricsource-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+<TR><TD><CODE>targetAverageUtilization</CODE><BR /><I>integer</I></TD><TD>targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.</TD></TR>
+<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcemetricstatus-v2beta2-autoscaling">ResourceMetricStatus v2beta2 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta2</CODE></TD><TD><CODE>ResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricstatus-v2-autoscaling">v2</a>
+<a href="#resourcemetricstatus-v2beta1-autoscaling">v2beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta2-autoscaling">MetricStatus [autoscaling/v2beta2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2beta2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus v2beta1 autoscaling</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ResourceMetricStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcemetricstatus-v2-autoscaling">v2</a>
+<a href="#resourcemetricstatus-v2beta2-autoscaling">v2beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>currentAverageUtilization</CODE><BR /><I>integer</I></TD><TD>currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.</TD></TR>
+<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type. It will always be set, regardless of the corresponding metric specification.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io">ResourcePolicyRule v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourcePolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>`apiGroups` is a list of matching API groups and may not be empty. &#34;*&#34; matches all API groups and, if present, must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>clusterScope</CODE><BR /><I>boolean</I></TD><TD>`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.</TD></TR>
+<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>`namespaces` is a list of target namespaces that restricts matches.  A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains &#34;*&#34;.  Note that &#34;*&#34; matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource.  For example, [ &#34;services&#34;, &#34;nodes/status&#34; ].  This list may not be empty. &#34;*&#34; matches all resources and, if present, must be the only entry. Required.</TD></TR>
+<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs and, if present, must be the only entry. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="runtimeclass-v1beta1-node-k8s-io">RuntimeClass v1beta1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RuntimeClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#runtimeclass-v1-node-k8s-io">v1</a>
+<a href="#runtimeclass-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclasslist-v1beta1-node-k8s-io">RuntimeClassList [node/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node &amp; CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called &#34;runc&#34; might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.</TD></TR>
+<TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1beta1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="runtimeclasslist-v1beta1-node-k8s-io">RuntimeClassList v1beta1 node</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-runtimeclass-v1beta1-node-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-runtimeclass-v1beta1-node-k8s-io">Create</H2>
+<P>create a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/node.k8s.io/v1beta1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-runtimeclass-v1beta1-node-k8s-io">Patch</H2>
+<P>partially update the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/node.k8s.io/v1beta1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-runtimeclass-v1beta1-node-k8s-io">Replace</H2>
+<P>replace the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/node.k8s.io/v1beta1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-runtimeclass-v1beta1-node-k8s-io">Delete</H2>
+<P>delete a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1beta1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-runtimeclass-v1beta1-node-k8s-io">Delete Collection</H2>
+<P>delete collection of RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1beta1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-runtimeclass-v1beta1-node-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-runtimeclass-v1beta1-node-k8s-io">Read</H2>
+<P>read the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1beta1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-runtimeclass-v1beta1-node-k8s-io">List</H2>
+<P>list or watch objects of kind RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1beta1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclasslist-v1beta1-node-k8s-io">RuntimeClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-runtimeclass-v1beta1-node-k8s-io">Watch</H2>
+<P>watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1beta1/watch/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-runtimeclass-v1beta1-node-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1beta1/watch/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="runtimeclass-v1alpha1-node-k8s-io">RuntimeClass v1alpha1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>RuntimeClass</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#runtimeclass-v1-node-k8s-io">v1</a>
+<a href="#runtimeclass-v1beta1-node-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclasslist-v1alpha1-node-k8s-io">RuntimeClassList [node/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#runtimeclassspec-v1alpha1-node-k8s-io">RuntimeClassSpec</a></I></TD><TD>Specification of the RuntimeClass More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="runtimeclassspec-v1alpha1-node-k8s-io">RuntimeClassSpec v1alpha1 node</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass [node/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.</TD></TR>
+<TR><TD><CODE>runtimeHandler</CODE><BR /><I>string</I></TD><TD>RuntimeHandler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node &amp; CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called &#34;runc&#34; might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The RuntimeHandler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR>
+<TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1alpha1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="runtimeclasslist-v1alpha1-node-k8s-io">RuntimeClassList v1alpha1 node</H3>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</TD></TR>
+<TR><TD><CODE>items</CODE><BR /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
+<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-runtimeclass-v1alpha1-node-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-runtimeclass-v1alpha1-node-k8s-io">Create</H2>
+<P>create a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/node.k8s.io/v1alpha1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-runtimeclass-v1alpha1-node-k8s-io">Patch</H2>
+<P>partially update the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/node.k8s.io/v1alpha1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-runtimeclass-v1alpha1-node-k8s-io">Replace</H2>
+<P>replace the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/node.k8s.io/v1alpha1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
+<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-runtimeclass-v1alpha1-node-k8s-io">Delete</H2>
+<P>delete a RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1alpha1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-runtimeclass-v1alpha1-node-k8s-io">Delete Collection</H2>
+<P>delete collection of RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/node.k8s.io/v1alpha1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>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.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
+<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-read-operations-runtimeclass-v1alpha1-node-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-runtimeclass-v1alpha1-node-k8s-io">Read</H2>
+<P>read the specified RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1alpha1/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclass-v1alpha1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-runtimeclass-v1alpha1-node-k8s-io">List</H2>
+<P>list or watch objects of kind RuntimeClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1alpha1/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#runtimeclasslist-v1alpha1-node-k8s-io">RuntimeClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-runtimeclass-v1alpha1-node-k8s-io">Watch</H2>
+<P>watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1alpha1/watch/runtimeclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-list-runtimeclass-v1alpha1-node-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/node.k8s.io/v1alpha1/watch/runtimeclasses</CODE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</TD></TR>
+<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
+<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
+<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
+<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="scheduling-v1beta1-node-k8s-io">Scheduling v1beta1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Scheduling</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#scheduling-v1-node-k8s-io">v1</a>
+<a href="#scheduling-v1alpha1-node-k8s-io">v1alpha1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclass-v1beta1-node-k8s-io">RuntimeClass [node/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod&#39;s existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.</TD></TR>
+<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="scheduling-v1alpha1-node-k8s-io">Scheduling v1alpha1 node.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Scheduling</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#scheduling-v1-node-k8s-io">v1</a>
+<a href="#scheduling-v1beta1-node-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#runtimeclassspec-v1alpha1-node-k8s-io">RuntimeClassSpec [node/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod&#39;s existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.</TD></TR>
+<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io">ServiceAccountSubject v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ServiceAccountSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of matching ServiceAccount objects, or &#34;*&#34; to match regardless of name. Required.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>`namespace` is the namespace of matching ServiceAccount objects. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="servicereference-v1-apiextensions-k8s-io">ServiceReference v1 apiextensions.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#webhookclientconfig-v1-apiextensions-k8s-io">WebhookClientConfig [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the service. Required</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>namespace is the namespace of the service. Required</TD></TR>
+<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>path is an optional URL path at which the webhook will be contacted.</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>port is an optional service port at which the webhook will be contacted. `port` should be a valid port number (1-65535, inclusive). Defaults to 443 for backward compatibility.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="servicereference-v1-apiregistration-k8s-io">ServiceReference v1 apiregistration.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec [apiregistration/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the service</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the service</TD></TR>
+<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="subject-v1-rbac-authorization-k8s-io">Subject v1 rbac.authorization.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+<a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">v1beta1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
+  <LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup holds the API group of the referenced subject. Defaults to &#34;&#34; for ServiceAccount subjects. Defaults to &#34;rbac.authorization.k8s.io&#34; for User and Group subjects.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of object being referenced. Values defined by this API group are &#34;User&#34;, &#34;Group&#34;, and &#34;ServiceAccount&#34;. If the Authorizer does not recognized the kind value, the Authorizer should report an error.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the object being referenced.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referenced object.  If the object kind is non-namespace, such as &#34;User&#34; or &#34;Group&#34;, and this value is not empty the Authorizer should report an error.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="subject-v1beta1-flowcontrol-apiserver-k8s-io">Subject v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#subject-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+<a href="#subject-v1-rbac-authorization-k8s-io">v1</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>group</CODE><BR /><I><a href="#groupsubject-v1beta1-flowcontrol-apiserver-k8s-io">GroupSubject</a></I></TD><TD>`group` matches based on user group name.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>`kind` indicates which one of the other fields is non-empty. Required</TD></TR>
+<TR><TD><CODE>serviceAccount</CODE><BR /><I><a href="#serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io">ServiceAccountSubject</a></I></TD><TD>`serviceAccount` matches ServiceAccounts.</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I><a href="#usersubject-v1beta1-flowcontrol-apiserver-k8s-io">UserSubject</a></I></TD><TD>`user` matches based on username.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="tokenrequest-v1-storage-k8s-io">TokenRequest v1 storage.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TokenRequest</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#csidriverspec-v1-storage-k8s-io">CSIDriverSpec [storage/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>audience</CODE><BR /><I>string</I></TD><TD>Audience is the intended audience of the token in &#34;TokenRequestSpec&#34;. It will default to the audiences of kube apiserver.</TD></TR>
+<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>ExpirationSeconds is the duration of validity of the token in &#34;TokenRequestSpec&#34;. It has the same default value of &#34;ExpirationSeconds&#34; in &#34;TokenRequestSpec&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="usersubject-v1beta1-flowcontrol-apiserver-k8s-io">UserSubject v1beta1 flowcontrol.apiserver.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>UserSubject</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
+<a href="#usersubject-v1beta2-flowcontrol-apiserver-k8s-io">v1beta2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#subject-v1beta1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the username that matches, or &#34;*&#34; to match all usernames. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="webhookclientconfig-v1-apiextensions-k8s-io">WebhookClientConfig v1 apiextensions.k8s.io</H1>
+<TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WebhookClientConfig</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#webhookconversion-v1-apiextensions-k8s-io">WebhookConversion [apiextensions/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>caBundle is a PEM encoded CA bundle which will be used to validate the webhook&#39;s server certificate. If unspecified, system trust roots on the apiserver are used.</TD></TR>
+<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-apiextensions-k8s-io">ServiceReference</a></I></TD><TD>service is a reference to the service for this webhook. Either service or url must be specified.  If the webhook is running within the cluster, then you should use `service`.</TD></TR>
+<TR><TD><CODE>url</CODE><BR /><I>string</I></TD><TD>url gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.  The `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.  Please note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.  The scheme must be &#34;https&#34;; the URL must begin with &#34;https://&#34;.  A path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.  Attempting to use a user or basic auth e.g. &#34;user:password@&#34; is not allowed. Fragments (&#34;#...&#34;) and query parameters (&#34;?...&#34;) are not allowed, either.</TD></TR>
+</TBODY>
+</TABLE>
+
+</DIV>
+</DIV>
+</DIV>
+<SCRIPT src="/js/jquery-3.3.1.min.js"></SCRIPT>
+<SCRIPT src="/js/jquery.scrollTo-2.1.2.min.js"></SCRIPT>
+<SCRIPT src="/js/bootstrap-4.3.1.min.js"></SCRIPT>
+<SCRIPT src="js/navData.js"></SCRIPT>
+<SCRIPT src="/js/scroll-apiref.js"></SCRIPT>
+</BODY>
+</HTML>
diff --git a/static/docs/reference/generated/kubernetes-api/v1.23/js/navData.js b/static/docs/reference/generated/kubernetes-api/v1.23/js/navData.js
new file mode 100644
index 0000000000000..3f54c376ef5ad
--- /dev/null
+++ b/static/docs/reference/generated/kubernetes-api/v1.23/js/navData.js
@@ -0,0 +1 @@
+(function(){navData={"toc":[{"section":"webhookclientconfig-v1-apiextensions-k8s-io","subsections":[]},{"section":"usersubject-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"tokenrequest-v1-storage-k8s-io","subsections":[]},{"section":"subject-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"subject-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"servicereference-v1-apiregistration-k8s-io","subsections":[]},{"section":"servicereference-v1-apiextensions-k8s-io","subsections":[]},{"section":"serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"scheduling-v1alpha1-node-k8s-io","subsections":[]},{"section":"scheduling-v1beta1-node-k8s-io","subsections":[]},{"section":"runtimeclass-v1alpha1-node-k8s-io","subsections":[{"section":"-strong-read-operations-runtimeclass-v1alpha1-node-k8s-io-strong-","subsections":[{"section":"watch-list-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"watch-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"list-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"read-runtimeclass-v1alpha1-node-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-runtimeclass-v1alpha1-node-k8s-io-strong-","subsections":[{"section":"delete-collection-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"delete-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"replace-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"patch-runtimeclass-v1alpha1-node-k8s-io","subsections":[]},{"section":"create-runtimeclass-v1alpha1-node-k8s-io","subsections":[]}]}]},{"section":"runtimeclass-v1beta1-node-k8s-io","subsections":[{"section":"-strong-read-operations-runtimeclass-v1beta1-node-k8s-io-strong-","subsections":[{"section":"watch-list-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"watch-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"list-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"read-runtimeclass-v1beta1-node-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-runtimeclass-v1beta1-node-k8s-io-strong-","subsections":[{"section":"delete-collection-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"delete-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"replace-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"patch-runtimeclass-v1beta1-node-k8s-io","subsections":[]},{"section":"create-runtimeclass-v1beta1-node-k8s-io","subsections":[]}]}]},{"section":"resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"resourcemetricstatus-v2beta1-autoscaling","subsections":[]},{"section":"resourcemetricstatus-v2beta2-autoscaling","subsections":[]},{"section":"resourcemetricsource-v2beta1-autoscaling","subsections":[]},{"section":"resourcemetricsource-v2beta2-autoscaling","subsections":[]},{"section":"queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"podsmetricstatus-v2beta1-autoscaling","subsections":[]},{"section":"podsmetricstatus-v2beta2-autoscaling","subsections":[]},{"section":"podsmetricsource-v2beta1-autoscaling","subsections":[]},{"section":"podsmetricsource-v2beta2-autoscaling","subsections":[]},{"section":"poddisruptionbudget-v1beta1-policy","subsections":[{"section":"-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-","subsections":[{"section":"replace-status-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"read-status-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"patch-status-poddisruptionbudget-v1beta1-policy","subsections":[]}]},{"section":"-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-","subsections":[{"section":"watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"watch-list-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"watch-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"list-all-namespaces-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"list-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"read-poddisruptionbudget-v1beta1-policy","subsections":[]}]},{"section":"-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-","subsections":[{"section":"delete-collection-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"delete-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"replace-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"patch-poddisruptionbudget-v1beta1-policy","subsections":[]},{"section":"create-poddisruptionbudget-v1beta1-policy","subsections":[]}]}]},{"section":"overhead-v1alpha1-node-k8s-io","subsections":[]},{"section":"overhead-v1beta1-node-k8s-io","subsections":[]},{"section":"objectmetricstatus-v2beta1-autoscaling","subsections":[]},{"section":"objectmetricstatus-v2beta2-autoscaling","subsections":[]},{"section":"objectmetricsource-v2beta1-autoscaling","subsections":[]},{"section":"objectmetricsource-v2beta2-autoscaling","subsections":[]},{"section":"nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"metricvaluestatus-v2beta2-autoscaling","subsections":[]},{"section":"metrictarget-v2beta2-autoscaling","subsections":[]},{"section":"metricstatus-v2beta1-autoscaling","subsections":[]},{"section":"metricstatus-v2beta2-autoscaling","subsections":[]},{"section":"metricspec-v2beta1-autoscaling","subsections":[]},{"section":"metricspec-v2beta2-autoscaling","subsections":[]},{"section":"metricidentifier-v2beta2-autoscaling","subsections":[]},{"section":"limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"limitresponse-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"jobtemplatespec-v1beta1-batch","subsections":[]},{"section":"horizontalpodautoscalercondition-v2beta1-autoscaling","subsections":[]},{"section":"horizontalpodautoscalercondition-v2beta2-autoscaling","subsections":[]},{"section":"horizontalpodautoscalerbehavior-v2beta2-autoscaling","subsections":[]},{"section":"horizontalpodautoscaler-v2beta1-autoscaling","subsections":[{"section":"-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","subsections":[{"section":"replace-status-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"read-status-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"patch-status-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]}]},{"section":"-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","subsections":[{"section":"watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"watch-list-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"watch-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"list-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"read-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]}]},{"section":"-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","subsections":[{"section":"delete-collection-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"delete-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"replace-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"patch-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]},{"section":"create-horizontalpodautoscaler-v2beta1-autoscaling","subsections":[]}]}]},{"section":"horizontalpodautoscaler-v2beta2-autoscaling","subsections":[{"section":"-strong-status-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","subsections":[{"section":"replace-status-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"read-status-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"patch-status-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]}]},{"section":"-strong-read-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","subsections":[{"section":"watch-list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"watch-list-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"watch-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"list-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"read-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]}]},{"section":"-strong-write-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","subsections":[{"section":"delete-collection-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"delete-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"replace-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"patch-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]},{"section":"create-horizontalpodautoscaler-v2beta2-autoscaling","subsections":[]}]}]},{"section":"horizontalpodautoscaler-v1-autoscaling","subsections":[{"section":"-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"replace-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"read-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"patch-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]},{"section":"-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"watch-list-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"watch-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"list-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"read-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]},{"section":"-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"delete-collection-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"delete-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"replace-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"patch-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"create-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]}]},{"section":"hpascalingrules-v2beta2-autoscaling","subsections":[]},{"section":"hpascalingpolicy-v2beta2-autoscaling","subsections":[]},{"section":"groupsubject-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"forzone-v1beta1-discovery-k8s-io","subsections":[]},{"section":"flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"externalmetricstatus-v2beta1-autoscaling","subsections":[]},{"section":"externalmetricstatus-v2beta2-autoscaling","subsections":[]},{"section":"externalmetricsource-v2beta1-autoscaling","subsections":[]},{"section":"externalmetricsource-v2beta2-autoscaling","subsections":[]},{"section":"eventseries-v1beta1-events-k8s-io","subsections":[]},{"section":"eventseries-v1-core","subsections":[]},{"section":"event-v1beta1-events-k8s-io","subsections":[{"section":"-strong-read-operations-event-v1beta1-events-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-event-v1beta1-events-k8s-io","subsections":[]},{"section":"watch-list-event-v1beta1-events-k8s-io","subsections":[]},{"section":"watch-event-v1beta1-events-k8s-io","subsections":[]},{"section":"list-all-namespaces-event-v1beta1-events-k8s-io","subsections":[]},{"section":"list-event-v1beta1-events-k8s-io","subsections":[]},{"section":"read-event-v1beta1-events-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-event-v1beta1-events-k8s-io-strong-","subsections":[{"section":"delete-collection-event-v1beta1-events-k8s-io","subsections":[]},{"section":"delete-event-v1beta1-events-k8s-io","subsections":[]},{"section":"replace-event-v1beta1-events-k8s-io","subsections":[]},{"section":"patch-event-v1beta1-events-k8s-io","subsections":[]},{"section":"create-event-v1beta1-events-k8s-io","subsections":[]}]}]},{"section":"event-v1-core","subsections":[{"section":"-strong-read-operations-event-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-event-v1-core","subsections":[]},{"section":"watch-list-event-v1-core","subsections":[]},{"section":"watch-event-v1-core","subsections":[]},{"section":"list-all-namespaces-event-v1-core","subsections":[]},{"section":"list-event-v1-core","subsections":[]},{"section":"read-event-v1-core","subsections":[]}]},{"section":"-strong-write-operations-event-v1-core-strong-","subsections":[{"section":"delete-collection-event-v1-core","subsections":[]},{"section":"delete-event-v1-core","subsections":[]},{"section":"replace-event-v1-core","subsections":[]},{"section":"patch-event-v1-core","subsections":[]},{"section":"create-event-v1-core","subsections":[]}]}]},{"section":"endpointslice-v1beta1-discovery-k8s-io","subsections":[{"section":"-strong-read-operations-endpointslice-v1beta1-discovery-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"watch-list-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"watch-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"list-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"read-endpointslice-v1beta1-discovery-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-endpointslice-v1beta1-discovery-k8s-io-strong-","subsections":[{"section":"delete-collection-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"delete-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"replace-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"patch-endpointslice-v1beta1-discovery-k8s-io","subsections":[]},{"section":"create-endpointslice-v1beta1-discovery-k8s-io","subsections":[]}]}]},{"section":"endpointport-v1beta1-discovery-k8s-io","subsections":[]},{"section":"endpointport-v1-discovery-k8s-io","subsections":[]},{"section":"endpointhints-v1beta1-discovery-k8s-io","subsections":[]},{"section":"endpointconditions-v1beta1-discovery-k8s-io","subsections":[]},{"section":"endpoint-v1beta1-discovery-k8s-io","subsections":[]},{"section":"crossversionobjectreference-v2beta1-autoscaling","subsections":[]},{"section":"crossversionobjectreference-v2beta2-autoscaling","subsections":[]},{"section":"crossversionobjectreference-v2-autoscaling","subsections":[]},{"section":"cronjob-v1beta1-batch","subsections":[{"section":"-strong-status-operations-cronjob-v1beta1-batch-strong-","subsections":[{"section":"replace-status-cronjob-v1beta1-batch","subsections":[]},{"section":"read-status-cronjob-v1beta1-batch","subsections":[]},{"section":"patch-status-cronjob-v1beta1-batch","subsections":[]}]},{"section":"-strong-read-operations-cronjob-v1beta1-batch-strong-","subsections":[{"section":"watch-list-all-namespaces-cronjob-v1beta1-batch","subsections":[]},{"section":"watch-list-cronjob-v1beta1-batch","subsections":[]},{"section":"watch-cronjob-v1beta1-batch","subsections":[]},{"section":"list-all-namespaces-cronjob-v1beta1-batch","subsections":[]},{"section":"list-cronjob-v1beta1-batch","subsections":[]},{"section":"read-cronjob-v1beta1-batch","subsections":[]}]},{"section":"-strong-write-operations-cronjob-v1beta1-batch-strong-","subsections":[{"section":"delete-collection-cronjob-v1beta1-batch","subsections":[]},{"section":"delete-cronjob-v1beta1-batch","subsections":[]},{"section":"replace-cronjob-v1beta1-batch","subsections":[]},{"section":"patch-cronjob-v1beta1-batch","subsections":[]},{"section":"create-cronjob-v1beta1-batch","subsections":[]}]}]},{"section":"containerresourcemetricstatus-v2beta1-autoscaling","subsections":[]},{"section":"containerresourcemetricstatus-v2beta2-autoscaling","subsections":[]},{"section":"containerresourcemetricsource-v2beta1-autoscaling","subsections":[]},{"section":"containerresourcemetricsource-v2beta2-autoscaling","subsections":[]},{"section":"csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"watch-list-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"watch-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"list-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"read-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"delete-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"replace-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"patch-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]},{"section":"create-csistoragecapacity-v1alpha1-storage-k8s-io","subsections":[]}]}]},{"section":"-strong-old-api-versions-strong-","subsections":[]},{"section":"windowssecuritycontextoptions-v1-core","subsections":[]},{"section":"weightedpodaffinityterm-v1-core","subsections":[]},{"section":"webhookconversion-v1-apiextensions-k8s-io","subsections":[]},{"section":"webhookclientconfig-v1-admissionregistration-k8s-io","subsections":[]},{"section":"watchevent-v1-meta","subsections":[]},{"section":"vspherevirtualdiskvolumesource-v1-core","subsections":[]},{"section":"volumeprojection-v1-core","subsections":[]},{"section":"volumenoderesources-v1-storage-k8s-io","subsections":[]},{"section":"volumenodeaffinity-v1-core","subsections":[]},{"section":"volumemount-v1-core","subsections":[]},{"section":"volumeerror-v1-storage-k8s-io","subsections":[]},{"section":"volumedevice-v1-core","subsections":[]},{"section":"volumeattachmentsource-v1-storage-k8s-io","subsections":[]},{"section":"validationrule-v1-apiextensions-k8s-io","subsections":[]},{"section":"validatingwebhook-v1-admissionregistration-k8s-io","subsections":[]},{"section":"usersubject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"userinfo-v1-authentication-k8s-io","subsections":[]},{"section":"uncountedterminatedpods-v1-batch","subsections":[]},{"section":"typedlocalobjectreference-v1-core","subsections":[]},{"section":"topologyspreadconstraint-v1-core","subsections":[]},{"section":"topologyselectorterm-v1-core","subsections":[]},{"section":"topologyselectorlabelrequirement-v1-core","subsections":[]},{"section":"toleration-v1-core","subsections":[]},{"section":"time-v1-meta","subsections":[]},{"section":"taint-v1-core","subsections":[]},{"section":"tcpsocketaction-v1-core","subsections":[]},{"section":"sysctl-v1-core","subsections":[]},{"section":"supplementalgroupsstrategyoptions-v1beta1-policy","subsections":[]},{"section":"subjectrulesreviewstatus-v1-authorization-k8s-io","subsections":[]},{"section":"subject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"storageversioncondition-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"storageosvolumesource-v1-core","subsections":[]},{"section":"storageospersistentvolumesource-v1-core","subsections":[]},{"section":"statusdetails-v1-meta","subsections":[]},{"section":"statuscause-v1-meta","subsections":[]},{"section":"status-v1-meta","subsections":[]},{"section":"statefulsetupdatestrategy-v1-apps","subsections":[]},{"section":"statefulsetpersistentvolumeclaimretentionpolicy-v1-apps","subsections":[]},{"section":"statefulsetcondition-v1-apps","subsections":[]},{"section":"sessionaffinityconfig-v1-core","subsections":[]},{"section":"servicereference-v1-admissionregistration-k8s-io","subsections":[]},{"section":"serviceport-v1-core","subsections":[]},{"section":"servicebackendport-v1-networking-k8s-io","subsections":[]},{"section":"serviceaccounttokenprojection-v1-core","subsections":[]},{"section":"serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"serverstorageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"serveraddressbyclientcidr-v1-meta","subsections":[]},{"section":"securitycontext-v1-core","subsections":[]},{"section":"secretvolumesource-v1-core","subsections":[]},{"section":"secretreference-v1-core","subsections":[]},{"section":"secretprojection-v1-core","subsections":[]},{"section":"secretkeyselector-v1-core","subsections":[]},{"section":"secretenvsource-v1-core","subsections":[]},{"section":"seccompprofile-v1-core","subsections":[]},{"section":"scopedresourceselectorrequirement-v1-core","subsections":[]},{"section":"scopeselector-v1-core","subsections":[]},{"section":"scheduling-v1-node-k8s-io","subsections":[]},{"section":"scaleiovolumesource-v1-core","subsections":[]},{"section":"scaleiopersistentvolumesource-v1-core","subsections":[]},{"section":"scale-v1-autoscaling","subsections":[]},{"section":"selinuxstrategyoptions-v1beta1-policy","subsections":[]},{"section":"selinuxoptions-v1-core","subsections":[]},{"section":"runtimeclassstrategyoptions-v1beta1-policy","subsections":[]},{"section":"runasuserstrategyoptions-v1beta1-policy","subsections":[]},{"section":"runasgroupstrategyoptions-v1beta1-policy","subsections":[]},{"section":"rulewithoperations-v1-admissionregistration-k8s-io","subsections":[]},{"section":"rollingupdatestatefulsetstrategy-v1-apps","subsections":[]},{"section":"roleref-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"resourcerule-v1-authorization-k8s-io","subsections":[]},{"section":"resourcerequirements-v1-core","subsections":[]},{"section":"resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"resourcemetricstatus-v2-autoscaling","subsections":[]},{"section":"resourcemetricsource-v2-autoscaling","subsections":[]},{"section":"resourcefieldselector-v1-core","subsections":[]},{"section":"resourceattributes-v1-authorization-k8s-io","subsections":[]},{"section":"replicationcontrollercondition-v1-core","subsections":[]},{"section":"replicasetcondition-v1-apps","subsections":[]},{"section":"rbdvolumesource-v1-core","subsections":[]},{"section":"rbdpersistentvolumesource-v1-core","subsections":[]},{"section":"quobytevolumesource-v1-core","subsections":[]},{"section":"queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"quantity-resource-core","subsections":[]},{"section":"projectedvolumesource-v1-core","subsections":[]},{"section":"probe-v1-core","subsections":[]},{"section":"prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"preferredschedulingterm-v1-core","subsections":[]},{"section":"preconditions-v1-meta","subsections":[]},{"section":"portworxvolumesource-v1-core","subsections":[]},{"section":"portstatus-v1-core","subsections":[]},{"section":"policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"policyrule-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"podsmetricstatus-v2-autoscaling","subsections":[]},{"section":"podsmetricsource-v2-autoscaling","subsections":[]},{"section":"podsecuritycontext-v1-core","subsections":[]},{"section":"podreadinessgate-v1-core","subsections":[]},{"section":"podos-v1-core","subsections":[]},{"section":"podip-v1-core","subsections":[]},{"section":"poddnsconfigoption-v1-core","subsections":[]},{"section":"poddnsconfig-v1-core","subsections":[]},{"section":"podcondition-v1-core","subsections":[]},{"section":"podantiaffinity-v1-core","subsections":[]},{"section":"podaffinityterm-v1-core","subsections":[]},{"section":"podaffinity-v1-core","subsections":[]},{"section":"photonpersistentdiskvolumesource-v1-core","subsections":[]},{"section":"persistentvolumeclaimvolumesource-v1-core","subsections":[]},{"section":"persistentvolumeclaimtemplate-v1-core","subsections":[]},{"section":"persistentvolumeclaimcondition-v1-core","subsections":[]},{"section":"patch-v1-meta","subsections":[]},{"section":"ownerreference-v1-meta","subsections":[]},{"section":"overhead-v1-node-k8s-io","subsections":[]},{"section":"objectreference-v1-core","subsections":[]},{"section":"objectmetricstatus-v2-autoscaling","subsections":[]},{"section":"objectmetricsource-v2-autoscaling","subsections":[]},{"section":"objectmeta-v1-meta","subsections":[]},{"section":"objectfieldselector-v1-core","subsections":[]},{"section":"nonresourcerule-v1-authorization-k8s-io","subsections":[]},{"section":"nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"nonresourceattributes-v1-authorization-k8s-io","subsections":[]},{"section":"nodesysteminfo-v1-core","subsections":[]},{"section":"nodeselectorterm-v1-core","subsections":[]},{"section":"nodeselectorrequirement-v1-core","subsections":[]},{"section":"nodeselector-v1-core","subsections":[]},{"section":"nodedaemonendpoints-v1-core","subsections":[]},{"section":"nodeconfigstatus-v1-core","subsections":[]},{"section":"nodeconfigsource-v1-core","subsections":[]},{"section":"nodecondition-v1-core","subsections":[]},{"section":"nodeaffinity-v1-core","subsections":[]},{"section":"nodeaddress-v1-core","subsections":[]},{"section":"networkpolicyport-v1-networking-k8s-io","subsections":[]},{"section":"networkpolicypeer-v1-networking-k8s-io","subsections":[]},{"section":"networkpolicyingressrule-v1-networking-k8s-io","subsections":[]},{"section":"networkpolicyegressrule-v1-networking-k8s-io","subsections":[]},{"section":"namespacecondition-v1-core","subsections":[]},{"section":"nfsvolumesource-v1-core","subsections":[]},{"section":"mutatingwebhook-v1-admissionregistration-k8s-io","subsections":[]},{"section":"microtime-v1-meta","subsections":[]},{"section":"metricvaluestatus-v2-autoscaling","subsections":[]},{"section":"metrictarget-v2-autoscaling","subsections":[]},{"section":"metricstatus-v2-autoscaling","subsections":[]},{"section":"metricspec-v2-autoscaling","subsections":[]},{"section":"metricidentifier-v2-autoscaling","subsections":[]},{"section":"managedfieldsentry-v1-meta","subsections":[]},{"section":"localvolumesource-v1-core","subsections":[]},{"section":"localobjectreference-v1-core","subsections":[]},{"section":"loadbalancerstatus-v1-core","subsections":[]},{"section":"loadbalanceringress-v1-core","subsections":[]},{"section":"listmeta-v1-meta","subsections":[]},{"section":"limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"limitresponse-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"limitrangeitem-v1-core","subsections":[]},{"section":"lifecyclehandler-v1-core","subsections":[]},{"section":"lifecycle-v1-core","subsections":[]},{"section":"labelselectorrequirement-v1-meta","subsections":[]},{"section":"labelselector-v1-meta","subsections":[]},{"section":"keytopath-v1-core","subsections":[]},{"section":"jobtemplatespec-v1-batch","subsections":[]},{"section":"jobcondition-v1-batch","subsections":[]},{"section":"jsonschemapropsorbool-v1-apiextensions-k8s-io","subsections":[]},{"section":"jsonschemapropsorarray-v1-apiextensions-k8s-io","subsections":[]},{"section":"jsonschemaprops-v1-apiextensions-k8s-io","subsections":[]},{"section":"json-v1-apiextensions-k8s-io","subsections":[]},{"section":"ingresstls-v1-networking-k8s-io","subsections":[]},{"section":"ingressservicebackend-v1-networking-k8s-io","subsections":[]},{"section":"ingressrule-v1-networking-k8s-io","subsections":[]},{"section":"ingressclassparametersreference-v1-networking-k8s-io","subsections":[]},{"section":"ingressbackend-v1-networking-k8s-io","subsections":[]},{"section":"iscsivolumesource-v1-core","subsections":[]},{"section":"iscsipersistentvolumesource-v1-core","subsections":[]},{"section":"ipblock-v1-networking-k8s-io","subsections":[]},{"section":"idrange-v1beta1-policy","subsections":[]},{"section":"hostportrange-v1beta1-policy","subsections":[]},{"section":"hostpathvolumesource-v1-core","subsections":[]},{"section":"hostalias-v1-core","subsections":[]},{"section":"horizontalpodautoscalercondition-v2-autoscaling","subsections":[]},{"section":"horizontalpodautoscalerbehavior-v2-autoscaling","subsections":[]},{"section":"horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"httpingressrulevalue-v1-networking-k8s-io","subsections":[]},{"section":"httpingresspath-v1-networking-k8s-io","subsections":[]},{"section":"httpheader-v1-core","subsections":[]},{"section":"httpgetaction-v1-core","subsections":[]},{"section":"hpascalingrules-v2-autoscaling","subsections":[]},{"section":"hpascalingpolicy-v2-autoscaling","subsections":[]},{"section":"groupversionfordiscovery-v1-meta","subsections":[]},{"section":"groupsubject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"glusterfsvolumesource-v1-core","subsections":[]},{"section":"glusterfspersistentvolumesource-v1-core","subsections":[]},{"section":"gitrepovolumesource-v1-core","subsections":[]},{"section":"grpcaction-v1-core","subsections":[]},{"section":"gcepersistentdiskvolumesource-v1-core","subsections":[]},{"section":"forzone-v1-discovery-k8s-io","subsections":[]},{"section":"flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flockervolumesource-v1-core","subsections":[]},{"section":"flexvolumesource-v1-core","subsections":[]},{"section":"flexpersistentvolumesource-v1-core","subsections":[]},{"section":"fieldsv1-v1-meta","subsections":[]},{"section":"fsgroupstrategyoptions-v1beta1-policy","subsections":[]},{"section":"fcvolumesource-v1-core","subsections":[]},{"section":"externalmetricstatus-v2-autoscaling","subsections":[]},{"section":"externalmetricsource-v2-autoscaling","subsections":[]},{"section":"externaldocumentation-v1-apiextensions-k8s-io","subsections":[]},{"section":"execaction-v1-core","subsections":[]},{"section":"eviction-v1-policy","subsections":[]},{"section":"eventsource-v1-core","subsections":[]},{"section":"eventseries-v1-events-k8s-io","subsections":[]},{"section":"ephemeralvolumesource-v1-core","subsections":[]},{"section":"ephemeralcontainer-v1-core","subsections":[]},{"section":"envvarsource-v1-core","subsections":[]},{"section":"envvar-v1-core","subsections":[]},{"section":"envfromsource-v1-core","subsections":[]},{"section":"endpointsubset-v1-core","subsections":[]},{"section":"endpointport-v1-core","subsections":[]},{"section":"endpointhints-v1-discovery-k8s-io","subsections":[]},{"section":"endpointconditions-v1-discovery-k8s-io","subsections":[]},{"section":"endpointaddress-v1-core","subsections":[]},{"section":"endpoint-v1-discovery-k8s-io","subsections":[]},{"section":"emptydirvolumesource-v1-core","subsections":[]},{"section":"downwardapivolumesource-v1-core","subsections":[]},{"section":"downwardapivolumefile-v1-core","subsections":[]},{"section":"downwardapiprojection-v1-core","subsections":[]},{"section":"deploymentcondition-v1-apps","subsections":[]},{"section":"deleteoptions-v1-meta","subsections":[]},{"section":"daemonsetupdatestrategy-v1-apps","subsections":[]},{"section":"daemonsetcondition-v1-apps","subsections":[]},{"section":"daemonendpoint-v1-core","subsections":[]},{"section":"customresourcevalidation-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcesubresources-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcesubresourcestatus-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcesubresourcescale-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcedefinitionversion-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcedefinitionnames-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcedefinitioncondition-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourceconversion-v1-apiextensions-k8s-io","subsections":[]},{"section":"customresourcecolumndefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"crossversionobjectreference-v1-autoscaling","subsections":[]},{"section":"containerstatewaiting-v1-core","subsections":[]},{"section":"containerstateterminated-v1-core","subsections":[]},{"section":"containerstaterunning-v1-core","subsections":[]},{"section":"containerstate-v1-core","subsections":[]},{"section":"containerresourcemetricstatus-v2-autoscaling","subsections":[]},{"section":"containerresourcemetricsource-v2-autoscaling","subsections":[]},{"section":"containerport-v1-core","subsections":[]},{"section":"containerimage-v1-core","subsections":[]},{"section":"configmapvolumesource-v1-core","subsections":[]},{"section":"configmapprojection-v1-core","subsections":[]},{"section":"configmapnodeconfigsource-v1-core","subsections":[]},{"section":"configmapkeyselector-v1-core","subsections":[]},{"section":"configmapenvsource-v1-core","subsections":[]},{"section":"condition-v1-meta","subsections":[]},{"section":"componentcondition-v1-core","subsections":[]},{"section":"clientipconfig-v1-core","subsections":[]},{"section":"cindervolumesource-v1-core","subsections":[]},{"section":"cinderpersistentvolumesource-v1-core","subsections":[]},{"section":"certificatesigningrequestcondition-v1-certificates-k8s-io","subsections":[]},{"section":"cephfsvolumesource-v1-core","subsections":[]},{"section":"cephfspersistentvolumesource-v1-core","subsections":[]},{"section":"capabilities-v1-core","subsections":[]},{"section":"csivolumesource-v1-core","subsections":[]},{"section":"csipersistentvolumesource-v1-core","subsections":[]},{"section":"csinodedriver-v1-storage-k8s-io","subsections":[]},{"section":"boundobjectreference-v1-authentication-k8s-io","subsections":[]},{"section":"azurefilevolumesource-v1-core","subsections":[]},{"section":"azurefilepersistentvolumesource-v1-core","subsections":[]},{"section":"azurediskvolumesource-v1-core","subsections":[]},{"section":"attachedvolume-v1-core","subsections":[]},{"section":"allowedhostpath-v1beta1-policy","subsections":[]},{"section":"allowedflexvolume-v1beta1-policy","subsections":[]},{"section":"allowedcsidriver-v1beta1-policy","subsections":[]},{"section":"aggregationrule-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"affinity-v1-core","subsections":[]},{"section":"awselasticblockstorevolumesource-v1-core","subsections":[]},{"section":"apiversions-v1-meta","subsections":[]},{"section":"apiservicecondition-v1-apiregistration-k8s-io","subsections":[]},{"section":"apiresource-v1-meta","subsections":[]},{"section":"apigroup-v1-meta","subsections":[]},{"section":"-strong-definitions-strong-","subsections":[]},{"section":"networkpolicy-v1-networking-k8s-io","subsections":[{"section":"-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"watch-list-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"watch-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"list-all-namespaces-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"list-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"read-networkpolicy-v1-networking-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-","subsections":[{"section":"delete-collection-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"delete-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"replace-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"patch-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"create-networkpolicy-v1-networking-k8s-io","subsections":[]}]}]},{"section":"tokenreview-v1-authentication-k8s-io","subsections":[{"section":"-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-","subsections":[{"section":"create-tokenreview-v1-authentication-k8s-io","subsections":[]}]}]},{"section":"tokenrequest-v1-authentication-k8s-io","subsections":[]},{"section":"subjectaccessreview-v1-authorization-k8s-io","subsections":[{"section":"-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-","subsections":[{"section":"create-subjectaccessreview-v1-authorization-k8s-io","subsections":[]}]}]},{"section":"storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"read-status-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"watch-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"list-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"read-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"delete-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"replace-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"patch-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]},{"section":"create-storageversion-v1alpha1-internal-apiserver-k8s-io","subsections":[]}]}]},{"section":"serviceaccount-v1-core","subsections":[{"section":"-strong-read-operations-serviceaccount-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-serviceaccount-v1-core","subsections":[]},{"section":"watch-list-serviceaccount-v1-core","subsections":[]},{"section":"watch-serviceaccount-v1-core","subsections":[]},{"section":"list-all-namespaces-serviceaccount-v1-core","subsections":[]},{"section":"list-serviceaccount-v1-core","subsections":[]},{"section":"read-serviceaccount-v1-core","subsections":[]}]},{"section":"-strong-write-operations-serviceaccount-v1-core-strong-","subsections":[{"section":"delete-collection-serviceaccount-v1-core","subsections":[]},{"section":"delete-serviceaccount-v1-core","subsections":[]},{"section":"replace-serviceaccount-v1-core","subsections":[]},{"section":"patch-serviceaccount-v1-core","subsections":[]},{"section":"create-serviceaccount-v1-core","subsections":[]}]}]},{"section":"selfsubjectrulesreview-v1-authorization-k8s-io","subsections":[{"section":"-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-","subsections":[{"section":"create-selfsubjectrulesreview-v1-authorization-k8s-io","subsections":[]}]}]},{"section":"selfsubjectaccessreview-v1-authorization-k8s-io","subsections":[{"section":"-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-","subsections":[{"section":"create-selfsubjectaccessreview-v1-authorization-k8s-io","subsections":[]}]}]},{"section":"runtimeclass-v1-node-k8s-io","subsections":[{"section":"-strong-read-operations-runtimeclass-v1-node-k8s-io-strong-","subsections":[{"section":"watch-list-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"watch-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"list-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"read-runtimeclass-v1-node-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-runtimeclass-v1-node-k8s-io-strong-","subsections":[{"section":"delete-collection-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"delete-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"replace-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"patch-runtimeclass-v1-node-k8s-io","subsections":[]},{"section":"create-runtimeclass-v1-node-k8s-io","subsections":[]}]}]},{"section":"rolebinding-v1-rbac-authorization-k8s-io","subsections":[{"section":"-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-list-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"read-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"delete-collection-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"delete-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"replace-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"patch-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"create-rolebinding-v1-rbac-authorization-k8s-io","subsections":[]}]}]},{"section":"role-v1-rbac-authorization-k8s-io","subsections":[{"section":"-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-list-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-all-namespaces-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"read-role-v1-rbac-authorization-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"delete-collection-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"delete-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"replace-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"patch-role-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"create-role-v1-rbac-authorization-k8s-io","subsections":[]}]}]},{"section":"resourcequota-v1-core","subsections":[{"section":"-strong-status-operations-resourcequota-v1-core-strong-","subsections":[{"section":"replace-status-resourcequota-v1-core","subsections":[]},{"section":"read-status-resourcequota-v1-core","subsections":[]},{"section":"patch-status-resourcequota-v1-core","subsections":[]}]},{"section":"-strong-read-operations-resourcequota-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-resourcequota-v1-core","subsections":[]},{"section":"watch-list-resourcequota-v1-core","subsections":[]},{"section":"watch-resourcequota-v1-core","subsections":[]},{"section":"list-all-namespaces-resourcequota-v1-core","subsections":[]},{"section":"list-resourcequota-v1-core","subsections":[]},{"section":"read-resourcequota-v1-core","subsections":[]}]},{"section":"-strong-write-operations-resourcequota-v1-core-strong-","subsections":[{"section":"delete-collection-resourcequota-v1-core","subsections":[]},{"section":"delete-resourcequota-v1-core","subsections":[]},{"section":"replace-resourcequota-v1-core","subsections":[]},{"section":"patch-resourcequota-v1-core","subsections":[]},{"section":"create-resourcequota-v1-core","subsections":[]}]}]},{"section":"prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"persistentvolume-v1-core","subsections":[{"section":"-strong-status-operations-persistentvolume-v1-core-strong-","subsections":[{"section":"replace-status-persistentvolume-v1-core","subsections":[]},{"section":"read-status-persistentvolume-v1-core","subsections":[]},{"section":"patch-status-persistentvolume-v1-core","subsections":[]}]},{"section":"-strong-read-operations-persistentvolume-v1-core-strong-","subsections":[{"section":"watch-list-persistentvolume-v1-core","subsections":[]},{"section":"watch-persistentvolume-v1-core","subsections":[]},{"section":"list-persistentvolume-v1-core","subsections":[]},{"section":"read-persistentvolume-v1-core","subsections":[]}]},{"section":"-strong-write-operations-persistentvolume-v1-core-strong-","subsections":[{"section":"delete-collection-persistentvolume-v1-core","subsections":[]},{"section":"delete-persistentvolume-v1-core","subsections":[]},{"section":"replace-persistentvolume-v1-core","subsections":[]},{"section":"patch-persistentvolume-v1-core","subsections":[]},{"section":"create-persistentvolume-v1-core","subsections":[]}]}]},{"section":"node-v1-core","subsections":[{"section":"-strong-proxy-operations-node-v1-core-strong-","subsections":[{"section":"replace-connect-proxy-path-node-v1-core","subsections":[]},{"section":"replace-connect-proxy-node-v1-core","subsections":[]},{"section":"head-connect-proxy-path-node-v1-core","subsections":[]},{"section":"head-connect-proxy-node-v1-core","subsections":[]},{"section":"get-connect-proxy-path-node-v1-core","subsections":[]},{"section":"get-connect-proxy-node-v1-core","subsections":[]},{"section":"delete-connect-proxy-path-node-v1-core","subsections":[]},{"section":"delete-connect-proxy-node-v1-core","subsections":[]},{"section":"create-connect-proxy-path-node-v1-core","subsections":[]},{"section":"create-connect-proxy-node-v1-core","subsections":[]}]},{"section":"-strong-status-operations-node-v1-core-strong-","subsections":[{"section":"replace-status-node-v1-core","subsections":[]},{"section":"read-status-node-v1-core","subsections":[]},{"section":"patch-status-node-v1-core","subsections":[]}]},{"section":"-strong-read-operations-node-v1-core-strong-","subsections":[{"section":"watch-list-node-v1-core","subsections":[]},{"section":"watch-node-v1-core","subsections":[]},{"section":"list-node-v1-core","subsections":[]},{"section":"read-node-v1-core","subsections":[]}]},{"section":"-strong-write-operations-node-v1-core-strong-","subsections":[{"section":"delete-collection-node-v1-core","subsections":[]},{"section":"delete-node-v1-core","subsections":[]},{"section":"replace-node-v1-core","subsections":[]},{"section":"patch-node-v1-core","subsections":[]},{"section":"create-node-v1-core","subsections":[]}]}]},{"section":"namespace-v1-core","subsections":[{"section":"-strong-status-operations-namespace-v1-core-strong-","subsections":[{"section":"replace-status-namespace-v1-core","subsections":[]},{"section":"read-status-namespace-v1-core","subsections":[]},{"section":"patch-status-namespace-v1-core","subsections":[]}]},{"section":"-strong-read-operations-namespace-v1-core-strong-","subsections":[{"section":"watch-list-namespace-v1-core","subsections":[]},{"section":"watch-namespace-v1-core","subsections":[]},{"section":"list-namespace-v1-core","subsections":[]},{"section":"read-namespace-v1-core","subsections":[]}]},{"section":"-strong-write-operations-namespace-v1-core-strong-","subsections":[{"section":"delete-namespace-v1-core","subsections":[]},{"section":"replace-namespace-v1-core","subsections":[]},{"section":"patch-namespace-v1-core","subsections":[]},{"section":"create-namespace-v1-core","subsections":[]}]}]},{"section":"localsubjectaccessreview-v1-authorization-k8s-io","subsections":[{"section":"-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-","subsections":[{"section":"create-localsubjectaccessreview-v1-authorization-k8s-io","subsections":[]}]}]},{"section":"lease-v1-coordination-k8s-io","subsections":[{"section":"-strong-read-operations-lease-v1-coordination-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-lease-v1-coordination-k8s-io","subsections":[]},{"section":"watch-list-lease-v1-coordination-k8s-io","subsections":[]},{"section":"watch-lease-v1-coordination-k8s-io","subsections":[]},{"section":"list-all-namespaces-lease-v1-coordination-k8s-io","subsections":[]},{"section":"list-lease-v1-coordination-k8s-io","subsections":[]},{"section":"read-lease-v1-coordination-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-lease-v1-coordination-k8s-io-strong-","subsections":[{"section":"delete-collection-lease-v1-coordination-k8s-io","subsections":[]},{"section":"delete-lease-v1-coordination-k8s-io","subsections":[]},{"section":"replace-lease-v1-coordination-k8s-io","subsections":[]},{"section":"patch-lease-v1-coordination-k8s-io","subsections":[]},{"section":"create-lease-v1-coordination-k8s-io","subsections":[]}]}]},{"section":"flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"componentstatus-v1-core","subsections":[{"section":"-strong-read-operations-componentstatus-v1-core-strong-","subsections":[{"section":"list-componentstatus-v1-core","subsections":[]},{"section":"read-componentstatus-v1-core","subsections":[]}]}]},{"section":"clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[{"section":"-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"read-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"delete-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"replace-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"patch-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"create-clusterrolebinding-v1-rbac-authorization-k8s-io","subsections":[]}]}]},{"section":"clusterrole-v1-rbac-authorization-k8s-io","subsections":[{"section":"-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"watch-list-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"watch-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"list-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"read-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-","subsections":[{"section":"delete-collection-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"delete-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"replace-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"patch-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]},{"section":"create-clusterrole-v1-rbac-authorization-k8s-io","subsections":[]}]}]},{"section":"certificatesigningrequest-v1-certificates-k8s-io","subsections":[{"section":"-strong-status-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","subsections":[{"section":"replace-status-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"read-status-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"patch-status-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","subsections":[{"section":"watch-list-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"watch-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"list-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"read-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","subsections":[{"section":"delete-collection-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"delete-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"replace-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"patch-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]},{"section":"create-certificatesigningrequest-v1-certificates-k8s-io","subsections":[]}]}]},{"section":"binding-v1-core","subsections":[{"section":"-strong-write-operations-binding-v1-core-strong-","subsections":[{"section":"create-binding-v1-core","subsections":[]}]}]},{"section":"apiservice-v1-apiregistration-k8s-io","subsections":[{"section":"-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-","subsections":[{"section":"replace-status-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"read-status-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"patch-status-apiservice-v1-apiregistration-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-","subsections":[{"section":"watch-list-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"watch-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"list-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"read-apiservice-v1-apiregistration-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-","subsections":[{"section":"delete-collection-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"delete-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"replace-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"patch-apiservice-v1-apiregistration-k8s-io","subsections":[]},{"section":"create-apiservice-v1-apiregistration-k8s-io","subsections":[]}]}]},{"section":"-strong-cluster-apis-strong-","subsections":[]},{"section":"podsecuritypolicy-v1beta1-policy","subsections":[{"section":"-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-","subsections":[{"section":"watch-list-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"watch-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"list-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"read-podsecuritypolicy-v1beta1-policy","subsections":[]}]},{"section":"-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-","subsections":[{"section":"delete-collection-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"delete-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"replace-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"patch-podsecuritypolicy-v1beta1-policy","subsections":[]},{"section":"create-podsecuritypolicy-v1beta1-policy","subsections":[]}]}]},{"section":"priorityclass-v1-scheduling-k8s-io","subsections":[{"section":"-strong-read-operations-priorityclass-v1-scheduling-k8s-io-strong-","subsections":[{"section":"watch-list-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"watch-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"list-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"read-priorityclass-v1-scheduling-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-priorityclass-v1-scheduling-k8s-io-strong-","subsections":[{"section":"delete-collection-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"delete-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"replace-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"patch-priorityclass-v1-scheduling-k8s-io","subsections":[]},{"section":"create-priorityclass-v1-scheduling-k8s-io","subsections":[]}]}]},{"section":"poddisruptionbudget-v1-policy","subsections":[{"section":"-strong-status-operations-poddisruptionbudget-v1-policy-strong-","subsections":[{"section":"replace-status-poddisruptionbudget-v1-policy","subsections":[]},{"section":"read-status-poddisruptionbudget-v1-policy","subsections":[]},{"section":"patch-status-poddisruptionbudget-v1-policy","subsections":[]}]},{"section":"-strong-read-operations-poddisruptionbudget-v1-policy-strong-","subsections":[{"section":"watch-list-all-namespaces-poddisruptionbudget-v1-policy","subsections":[]},{"section":"watch-list-poddisruptionbudget-v1-policy","subsections":[]},{"section":"watch-poddisruptionbudget-v1-policy","subsections":[]},{"section":"list-all-namespaces-poddisruptionbudget-v1-policy","subsections":[]},{"section":"list-poddisruptionbudget-v1-policy","subsections":[]},{"section":"read-poddisruptionbudget-v1-policy","subsections":[]}]},{"section":"-strong-write-operations-poddisruptionbudget-v1-policy-strong-","subsections":[{"section":"delete-collection-poddisruptionbudget-v1-policy","subsections":[]},{"section":"delete-poddisruptionbudget-v1-policy","subsections":[]},{"section":"replace-poddisruptionbudget-v1-policy","subsections":[]},{"section":"patch-poddisruptionbudget-v1-policy","subsections":[]},{"section":"create-poddisruptionbudget-v1-policy","subsections":[]}]}]},{"section":"podtemplate-v1-core","subsections":[{"section":"-strong-read-operations-podtemplate-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-podtemplate-v1-core","subsections":[]},{"section":"watch-list-podtemplate-v1-core","subsections":[]},{"section":"watch-podtemplate-v1-core","subsections":[]},{"section":"list-all-namespaces-podtemplate-v1-core","subsections":[]},{"section":"list-podtemplate-v1-core","subsections":[]},{"section":"read-podtemplate-v1-core","subsections":[]}]},{"section":"-strong-write-operations-podtemplate-v1-core-strong-","subsections":[{"section":"delete-collection-podtemplate-v1-core","subsections":[]},{"section":"delete-podtemplate-v1-core","subsections":[]},{"section":"replace-podtemplate-v1-core","subsections":[]},{"section":"patch-podtemplate-v1-core","subsections":[]},{"section":"create-podtemplate-v1-core","subsections":[]}]}]},{"section":"validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[{"section":"-strong-read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","subsections":[{"section":"watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","subsections":[{"section":"delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]}]}]},{"section":"mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[{"section":"-strong-read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","subsections":[{"section":"watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","subsections":[{"section":"delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]},{"section":"create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","subsections":[]}]}]},{"section":"horizontalpodautoscaler-v1-autoscaling","subsections":[{"section":"-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"replace-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"read-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"patch-status-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]},{"section":"-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"watch-list-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"watch-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"list-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"read-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]},{"section":"-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-","subsections":[{"section":"delete-collection-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"delete-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"replace-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"patch-horizontalpodautoscaler-v1-autoscaling","subsections":[]},{"section":"create-horizontalpodautoscaler-v1-autoscaling","subsections":[]}]}]},{"section":"limitrange-v1-core","subsections":[{"section":"-strong-read-operations-limitrange-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-limitrange-v1-core","subsections":[]},{"section":"watch-list-limitrange-v1-core","subsections":[]},{"section":"watch-limitrange-v1-core","subsections":[]},{"section":"list-all-namespaces-limitrange-v1-core","subsections":[]},{"section":"list-limitrange-v1-core","subsections":[]},{"section":"read-limitrange-v1-core","subsections":[]}]},{"section":"-strong-write-operations-limitrange-v1-core-strong-","subsections":[{"section":"delete-collection-limitrange-v1-core","subsections":[]},{"section":"delete-limitrange-v1-core","subsections":[]},{"section":"replace-limitrange-v1-core","subsections":[]},{"section":"patch-limitrange-v1-core","subsections":[]},{"section":"create-limitrange-v1-core","subsections":[]}]}]},{"section":"event-v1-events-k8s-io","subsections":[{"section":"-strong-read-operations-event-v1-events-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-event-v1-events-k8s-io","subsections":[]},{"section":"watch-list-event-v1-events-k8s-io","subsections":[]},{"section":"watch-event-v1-events-k8s-io","subsections":[]},{"section":"list-all-namespaces-event-v1-events-k8s-io","subsections":[]},{"section":"list-event-v1-events-k8s-io","subsections":[]},{"section":"read-event-v1-events-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-event-v1-events-k8s-io-strong-","subsections":[{"section":"delete-collection-event-v1-events-k8s-io","subsections":[]},{"section":"delete-event-v1-events-k8s-io","subsections":[]},{"section":"replace-event-v1-events-k8s-io","subsections":[]},{"section":"patch-event-v1-events-k8s-io","subsections":[]},{"section":"create-event-v1-events-k8s-io","subsections":[]}]}]},{"section":"customresourcedefinition-v1-apiextensions-k8s-io","subsections":[{"section":"-strong-status-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","subsections":[{"section":"replace-status-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"read-status-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"patch-status-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","subsections":[{"section":"watch-list-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"watch-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"list-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"read-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","subsections":[{"section":"delete-collection-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"delete-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"replace-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"patch-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]},{"section":"create-customresourcedefinition-v1-apiextensions-k8s-io","subsections":[]}]}]},{"section":"controllerrevision-v1-apps","subsections":[{"section":"-strong-read-operations-controllerrevision-v1-apps-strong-","subsections":[{"section":"watch-list-all-namespaces-controllerrevision-v1-apps","subsections":[]},{"section":"watch-list-controllerrevision-v1-apps","subsections":[]},{"section":"watch-controllerrevision-v1-apps","subsections":[]},{"section":"list-all-namespaces-controllerrevision-v1-apps","subsections":[]},{"section":"list-controllerrevision-v1-apps","subsections":[]},{"section":"read-controllerrevision-v1-apps","subsections":[]}]},{"section":"-strong-write-operations-controllerrevision-v1-apps-strong-","subsections":[{"section":"delete-collection-controllerrevision-v1-apps","subsections":[]},{"section":"delete-controllerrevision-v1-apps","subsections":[]},{"section":"replace-controllerrevision-v1-apps","subsections":[]},{"section":"patch-controllerrevision-v1-apps","subsections":[]},{"section":"create-controllerrevision-v1-apps","subsections":[]}]}]},{"section":"-strong-metadata-apis-strong-","subsections":[]},{"section":"volumeattachment-v1-storage-k8s-io","subsections":[{"section":"-strong-status-operations-volumeattachment-v1-storage-k8s-io-strong-","subsections":[{"section":"replace-status-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"read-status-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"patch-status-volumeattachment-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-volumeattachment-v1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"watch-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"list-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"read-volumeattachment-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-volumeattachment-v1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"delete-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"replace-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"patch-volumeattachment-v1-storage-k8s-io","subsections":[]},{"section":"create-volumeattachment-v1-storage-k8s-io","subsections":[]}]}]},{"section":"volume-v1-core","subsections":[]},{"section":"csistoragecapacity-v1beta1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"watch-list-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"watch-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"list-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"read-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"delete-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"replace-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"patch-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]},{"section":"create-csistoragecapacity-v1beta1-storage-k8s-io","subsections":[]}]}]},{"section":"storageclass-v1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-storageclass-v1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"watch-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"list-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"read-storageclass-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-storageclass-v1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"delete-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"replace-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"patch-storageclass-v1-storage-k8s-io","subsections":[]},{"section":"create-storageclass-v1-storage-k8s-io","subsections":[]}]}]},{"section":"persistentvolumeclaim-v1-core","subsections":[{"section":"-strong-status-operations-persistentvolumeclaim-v1-core-strong-","subsections":[{"section":"replace-status-persistentvolumeclaim-v1-core","subsections":[]},{"section":"read-status-persistentvolumeclaim-v1-core","subsections":[]},{"section":"patch-status-persistentvolumeclaim-v1-core","subsections":[]}]},{"section":"-strong-read-operations-persistentvolumeclaim-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-persistentvolumeclaim-v1-core","subsections":[]},{"section":"watch-list-persistentvolumeclaim-v1-core","subsections":[]},{"section":"watch-persistentvolumeclaim-v1-core","subsections":[]},{"section":"list-all-namespaces-persistentvolumeclaim-v1-core","subsections":[]},{"section":"list-persistentvolumeclaim-v1-core","subsections":[]},{"section":"read-persistentvolumeclaim-v1-core","subsections":[]}]},{"section":"-strong-write-operations-persistentvolumeclaim-v1-core-strong-","subsections":[{"section":"delete-collection-persistentvolumeclaim-v1-core","subsections":[]},{"section":"delete-persistentvolumeclaim-v1-core","subsections":[]},{"section":"replace-persistentvolumeclaim-v1-core","subsections":[]},{"section":"patch-persistentvolumeclaim-v1-core","subsections":[]},{"section":"create-persistentvolumeclaim-v1-core","subsections":[]}]}]},{"section":"secret-v1-core","subsections":[{"section":"-strong-read-operations-secret-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-secret-v1-core","subsections":[]},{"section":"watch-list-secret-v1-core","subsections":[]},{"section":"watch-secret-v1-core","subsections":[]},{"section":"list-all-namespaces-secret-v1-core","subsections":[]},{"section":"list-secret-v1-core","subsections":[]},{"section":"read-secret-v1-core","subsections":[]}]},{"section":"-strong-write-operations-secret-v1-core-strong-","subsections":[{"section":"delete-collection-secret-v1-core","subsections":[]},{"section":"delete-secret-v1-core","subsections":[]},{"section":"replace-secret-v1-core","subsections":[]},{"section":"patch-secret-v1-core","subsections":[]},{"section":"create-secret-v1-core","subsections":[]}]}]},{"section":"csinode-v1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-csinode-v1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-csinode-v1-storage-k8s-io","subsections":[]},{"section":"watch-csinode-v1-storage-k8s-io","subsections":[]},{"section":"list-csinode-v1-storage-k8s-io","subsections":[]},{"section":"read-csinode-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-csinode-v1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-csinode-v1-storage-k8s-io","subsections":[]},{"section":"delete-csinode-v1-storage-k8s-io","subsections":[]},{"section":"replace-csinode-v1-storage-k8s-io","subsections":[]},{"section":"patch-csinode-v1-storage-k8s-io","subsections":[]},{"section":"create-csinode-v1-storage-k8s-io","subsections":[]}]}]},{"section":"csidriver-v1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-csidriver-v1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"watch-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"list-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"read-csidriver-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-csidriver-v1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"delete-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"replace-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"patch-csidriver-v1-storage-k8s-io","subsections":[]},{"section":"create-csidriver-v1-storage-k8s-io","subsections":[]}]}]},{"section":"configmap-v1-core","subsections":[{"section":"-strong-read-operations-configmap-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-configmap-v1-core","subsections":[]},{"section":"watch-list-configmap-v1-core","subsections":[]},{"section":"watch-configmap-v1-core","subsections":[]},{"section":"list-all-namespaces-configmap-v1-core","subsections":[]},{"section":"list-configmap-v1-core","subsections":[]},{"section":"read-configmap-v1-core","subsections":[]}]},{"section":"-strong-write-operations-configmap-v1-core-strong-","subsections":[{"section":"delete-collection-configmap-v1-core","subsections":[]},{"section":"delete-configmap-v1-core","subsections":[]},{"section":"replace-configmap-v1-core","subsections":[]},{"section":"patch-configmap-v1-core","subsections":[]},{"section":"create-configmap-v1-core","subsections":[]}]}]},{"section":"-strong-config-and-storage-apis-strong-","subsections":[]},{"section":"service-v1-core","subsections":[{"section":"-strong-proxy-operations-service-v1-core-strong-","subsections":[{"section":"replace-connect-proxy-path-service-v1-core","subsections":[]},{"section":"replace-connect-proxy-service-v1-core","subsections":[]},{"section":"head-connect-proxy-path-service-v1-core","subsections":[]},{"section":"head-connect-proxy-service-v1-core","subsections":[]},{"section":"get-connect-proxy-path-service-v1-core","subsections":[]},{"section":"get-connect-proxy-service-v1-core","subsections":[]},{"section":"delete-connect-proxy-path-service-v1-core","subsections":[]},{"section":"delete-connect-proxy-service-v1-core","subsections":[]},{"section":"create-connect-proxy-path-service-v1-core","subsections":[]},{"section":"create-connect-proxy-service-v1-core","subsections":[]}]},{"section":"-strong-status-operations-service-v1-core-strong-","subsections":[{"section":"replace-status-service-v1-core","subsections":[]},{"section":"read-status-service-v1-core","subsections":[]},{"section":"patch-status-service-v1-core","subsections":[]}]},{"section":"-strong-read-operations-service-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-service-v1-core","subsections":[]},{"section":"watch-list-service-v1-core","subsections":[]},{"section":"watch-service-v1-core","subsections":[]},{"section":"list-all-namespaces-service-v1-core","subsections":[]},{"section":"list-service-v1-core","subsections":[]},{"section":"read-service-v1-core","subsections":[]}]},{"section":"-strong-write-operations-service-v1-core-strong-","subsections":[{"section":"delete-collection-service-v1-core","subsections":[]},{"section":"delete-service-v1-core","subsections":[]},{"section":"replace-service-v1-core","subsections":[]},{"section":"patch-service-v1-core","subsections":[]},{"section":"create-service-v1-core","subsections":[]}]}]},{"section":"ingressclass-v1-networking-k8s-io","subsections":[{"section":"-strong-read-operations-ingressclass-v1-networking-k8s-io-strong-","subsections":[{"section":"watch-list-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"watch-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"list-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"read-ingressclass-v1-networking-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-ingressclass-v1-networking-k8s-io-strong-","subsections":[{"section":"delete-collection-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"delete-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"replace-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"patch-ingressclass-v1-networking-k8s-io","subsections":[]},{"section":"create-ingressclass-v1-networking-k8s-io","subsections":[]}]}]},{"section":"ingress-v1-networking-k8s-io","subsections":[{"section":"-strong-status-operations-ingress-v1-networking-k8s-io-strong-","subsections":[{"section":"replace-status-ingress-v1-networking-k8s-io","subsections":[]},{"section":"read-status-ingress-v1-networking-k8s-io","subsections":[]},{"section":"patch-status-ingress-v1-networking-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-ingress-v1-networking-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-ingress-v1-networking-k8s-io","subsections":[]},{"section":"watch-list-ingress-v1-networking-k8s-io","subsections":[]},{"section":"watch-ingress-v1-networking-k8s-io","subsections":[]},{"section":"list-all-namespaces-ingress-v1-networking-k8s-io","subsections":[]},{"section":"list-ingress-v1-networking-k8s-io","subsections":[]},{"section":"read-ingress-v1-networking-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-ingress-v1-networking-k8s-io-strong-","subsections":[{"section":"delete-collection-ingress-v1-networking-k8s-io","subsections":[]},{"section":"delete-ingress-v1-networking-k8s-io","subsections":[]},{"section":"replace-ingress-v1-networking-k8s-io","subsections":[]},{"section":"patch-ingress-v1-networking-k8s-io","subsections":[]},{"section":"create-ingress-v1-networking-k8s-io","subsections":[]}]}]},{"section":"endpointslice-v1-discovery-k8s-io","subsections":[{"section":"-strong-read-operations-endpointslice-v1-discovery-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"watch-list-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"watch-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"list-all-namespaces-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"list-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"read-endpointslice-v1-discovery-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-endpointslice-v1-discovery-k8s-io-strong-","subsections":[{"section":"delete-collection-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"delete-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"replace-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"patch-endpointslice-v1-discovery-k8s-io","subsections":[]},{"section":"create-endpointslice-v1-discovery-k8s-io","subsections":[]}]}]},{"section":"endpoints-v1-core","subsections":[{"section":"-strong-read-operations-endpoints-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-endpoints-v1-core","subsections":[]},{"section":"watch-list-endpoints-v1-core","subsections":[]},{"section":"watch-endpoints-v1-core","subsections":[]},{"section":"list-all-namespaces-endpoints-v1-core","subsections":[]},{"section":"list-endpoints-v1-core","subsections":[]},{"section":"read-endpoints-v1-core","subsections":[]}]},{"section":"-strong-write-operations-endpoints-v1-core-strong-","subsections":[{"section":"delete-collection-endpoints-v1-core","subsections":[]},{"section":"delete-endpoints-v1-core","subsections":[]},{"section":"replace-endpoints-v1-core","subsections":[]},{"section":"patch-endpoints-v1-core","subsections":[]},{"section":"create-endpoints-v1-core","subsections":[]}]}]},{"section":"-strong-service-apis-strong-","subsections":[]},{"section":"statefulset-v1-apps","subsections":[{"section":"-strong-misc-operations-statefulset-v1-apps-strong-","subsections":[{"section":"patch-scale-statefulset-v1-apps","subsections":[]},{"section":"replace-scale-statefulset-v1-apps","subsections":[]},{"section":"read-scale-statefulset-v1-apps","subsections":[]}]},{"section":"-strong-status-operations-statefulset-v1-apps-strong-","subsections":[{"section":"replace-status-statefulset-v1-apps","subsections":[]},{"section":"read-status-statefulset-v1-apps","subsections":[]},{"section":"patch-status-statefulset-v1-apps","subsections":[]}]},{"section":"-strong-read-operations-statefulset-v1-apps-strong-","subsections":[{"section":"watch-list-all-namespaces-statefulset-v1-apps","subsections":[]},{"section":"watch-list-statefulset-v1-apps","subsections":[]},{"section":"watch-statefulset-v1-apps","subsections":[]},{"section":"list-all-namespaces-statefulset-v1-apps","subsections":[]},{"section":"list-statefulset-v1-apps","subsections":[]},{"section":"read-statefulset-v1-apps","subsections":[]}]},{"section":"-strong-write-operations-statefulset-v1-apps-strong-","subsections":[{"section":"delete-collection-statefulset-v1-apps","subsections":[]},{"section":"delete-statefulset-v1-apps","subsections":[]},{"section":"replace-statefulset-v1-apps","subsections":[]},{"section":"patch-statefulset-v1-apps","subsections":[]},{"section":"create-statefulset-v1-apps","subsections":[]}]}]},{"section":"replicationcontroller-v1-core","subsections":[{"section":"-strong-misc-operations-replicationcontroller-v1-core-strong-","subsections":[{"section":"patch-scale-replicationcontroller-v1-core","subsections":[]},{"section":"replace-scale-replicationcontroller-v1-core","subsections":[]},{"section":"read-scale-replicationcontroller-v1-core","subsections":[]}]},{"section":"-strong-status-operations-replicationcontroller-v1-core-strong-","subsections":[{"section":"replace-status-replicationcontroller-v1-core","subsections":[]},{"section":"read-status-replicationcontroller-v1-core","subsections":[]},{"section":"patch-status-replicationcontroller-v1-core","subsections":[]}]},{"section":"-strong-read-operations-replicationcontroller-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-replicationcontroller-v1-core","subsections":[]},{"section":"watch-list-replicationcontroller-v1-core","subsections":[]},{"section":"watch-replicationcontroller-v1-core","subsections":[]},{"section":"list-all-namespaces-replicationcontroller-v1-core","subsections":[]},{"section":"list-replicationcontroller-v1-core","subsections":[]},{"section":"read-replicationcontroller-v1-core","subsections":[]}]},{"section":"-strong-write-operations-replicationcontroller-v1-core-strong-","subsections":[{"section":"delete-collection-replicationcontroller-v1-core","subsections":[]},{"section":"delete-replicationcontroller-v1-core","subsections":[]},{"section":"replace-replicationcontroller-v1-core","subsections":[]},{"section":"patch-replicationcontroller-v1-core","subsections":[]},{"section":"create-replicationcontroller-v1-core","subsections":[]}]}]},{"section":"replicaset-v1-apps","subsections":[{"section":"-strong-misc-operations-replicaset-v1-apps-strong-","subsections":[{"section":"patch-scale-replicaset-v1-apps","subsections":[]},{"section":"replace-scale-replicaset-v1-apps","subsections":[]},{"section":"read-scale-replicaset-v1-apps","subsections":[]}]},{"section":"-strong-status-operations-replicaset-v1-apps-strong-","subsections":[{"section":"replace-status-replicaset-v1-apps","subsections":[]},{"section":"read-status-replicaset-v1-apps","subsections":[]},{"section":"patch-status-replicaset-v1-apps","subsections":[]}]},{"section":"-strong-read-operations-replicaset-v1-apps-strong-","subsections":[{"section":"watch-list-all-namespaces-replicaset-v1-apps","subsections":[]},{"section":"watch-list-replicaset-v1-apps","subsections":[]},{"section":"watch-replicaset-v1-apps","subsections":[]},{"section":"list-all-namespaces-replicaset-v1-apps","subsections":[]},{"section":"list-replicaset-v1-apps","subsections":[]},{"section":"read-replicaset-v1-apps","subsections":[]}]},{"section":"-strong-write-operations-replicaset-v1-apps-strong-","subsections":[{"section":"delete-collection-replicaset-v1-apps","subsections":[]},{"section":"delete-replicaset-v1-apps","subsections":[]},{"section":"replace-replicaset-v1-apps","subsections":[]},{"section":"patch-replicaset-v1-apps","subsections":[]},{"section":"create-replicaset-v1-apps","subsections":[]}]}]},{"section":"pod-v1-core","subsections":[{"section":"-strong-misc-operations-pod-v1-core-strong-","subsections":[{"section":"read-log-pod-v1-core","subsections":[]}]},{"section":"-strong-proxy-operations-pod-v1-core-strong-","subsections":[{"section":"replace-connect-proxy-path-pod-v1-core","subsections":[]},{"section":"replace-connect-proxy-pod-v1-core","subsections":[]},{"section":"head-connect-proxy-path-pod-v1-core","subsections":[]},{"section":"head-connect-proxy-pod-v1-core","subsections":[]},{"section":"get-connect-proxy-path-pod-v1-core","subsections":[]},{"section":"get-connect-proxy-pod-v1-core","subsections":[]},{"section":"get-connect-portforward-pod-v1-core","subsections":[]},{"section":"delete-connect-proxy-path-pod-v1-core","subsections":[]},{"section":"delete-connect-proxy-pod-v1-core","subsections":[]},{"section":"create-connect-proxy-path-pod-v1-core","subsections":[]},{"section":"create-connect-proxy-pod-v1-core","subsections":[]},{"section":"create-connect-portforward-pod-v1-core","subsections":[]}]},{"section":"-strong-ephemeralcontainers-operations-pod-v1-core-strong-","subsections":[{"section":"replace-ephemeralcontainers-pod-v1-core","subsections":[]},{"section":"read-ephemeralcontainers-pod-v1-core","subsections":[]},{"section":"patch-ephemeralcontainers-pod-v1-core","subsections":[]}]},{"section":"-strong-status-operations-pod-v1-core-strong-","subsections":[{"section":"replace-status-pod-v1-core","subsections":[]},{"section":"read-status-pod-v1-core","subsections":[]},{"section":"patch-status-pod-v1-core","subsections":[]}]},{"section":"-strong-read-operations-pod-v1-core-strong-","subsections":[{"section":"watch-list-all-namespaces-pod-v1-core","subsections":[]},{"section":"watch-list-pod-v1-core","subsections":[]},{"section":"watch-pod-v1-core","subsections":[]},{"section":"list-all-namespaces-pod-v1-core","subsections":[]},{"section":"list-pod-v1-core","subsections":[]},{"section":"read-pod-v1-core","subsections":[]}]},{"section":"-strong-write-operations-pod-v1-core-strong-","subsections":[{"section":"delete-collection-pod-v1-core","subsections":[]},{"section":"delete-pod-v1-core","subsections":[]},{"section":"replace-pod-v1-core","subsections":[]},{"section":"patch-pod-v1-core","subsections":[]},{"section":"create-eviction-pod-v1-core","subsections":[]},{"section":"create-pod-v1-core","subsections":[]}]}]},{"section":"job-v1-batch","subsections":[{"section":"-strong-status-operations-job-v1-batch-strong-","subsections":[{"section":"replace-status-job-v1-batch","subsections":[]},{"section":"read-status-job-v1-batch","subsections":[]},{"section":"patch-status-job-v1-batch","subsections":[]}]},{"section":"-strong-read-operations-job-v1-batch-strong-","subsections":[{"section":"watch-list-all-namespaces-job-v1-batch","subsections":[]},{"section":"watch-list-job-v1-batch","subsections":[]},{"section":"watch-job-v1-batch","subsections":[]},{"section":"list-all-namespaces-job-v1-batch","subsections":[]},{"section":"list-job-v1-batch","subsections":[]},{"section":"read-job-v1-batch","subsections":[]}]},{"section":"-strong-write-operations-job-v1-batch-strong-","subsections":[{"section":"delete-collection-job-v1-batch","subsections":[]},{"section":"delete-job-v1-batch","subsections":[]},{"section":"replace-job-v1-batch","subsections":[]},{"section":"patch-job-v1-batch","subsections":[]},{"section":"create-job-v1-batch","subsections":[]}]}]},{"section":"deployment-v1-apps","subsections":[{"section":"-strong-misc-operations-deployment-v1-apps-strong-","subsections":[{"section":"patch-scale-deployment-v1-apps","subsections":[]},{"section":"replace-scale-deployment-v1-apps","subsections":[]},{"section":"read-scale-deployment-v1-apps","subsections":[]}]},{"section":"-strong-status-operations-deployment-v1-apps-strong-","subsections":[{"section":"replace-status-deployment-v1-apps","subsections":[]},{"section":"read-status-deployment-v1-apps","subsections":[]},{"section":"patch-status-deployment-v1-apps","subsections":[]}]},{"section":"-strong-read-operations-deployment-v1-apps-strong-","subsections":[{"section":"watch-list-all-namespaces-deployment-v1-apps","subsections":[]},{"section":"watch-list-deployment-v1-apps","subsections":[]},{"section":"watch-deployment-v1-apps","subsections":[]},{"section":"list-all-namespaces-deployment-v1-apps","subsections":[]},{"section":"list-deployment-v1-apps","subsections":[]},{"section":"read-deployment-v1-apps","subsections":[]}]},{"section":"-strong-write-operations-deployment-v1-apps-strong-","subsections":[{"section":"delete-collection-deployment-v1-apps","subsections":[]},{"section":"delete-deployment-v1-apps","subsections":[]},{"section":"replace-deployment-v1-apps","subsections":[]},{"section":"patch-deployment-v1-apps","subsections":[]},{"section":"create-deployment-v1-apps","subsections":[]}]}]},{"section":"daemonset-v1-apps","subsections":[{"section":"-strong-status-operations-daemonset-v1-apps-strong-","subsections":[{"section":"replace-status-daemonset-v1-apps","subsections":[]},{"section":"read-status-daemonset-v1-apps","subsections":[]},{"section":"patch-status-daemonset-v1-apps","subsections":[]}]},{"section":"-strong-read-operations-daemonset-v1-apps-strong-","subsections":[{"section":"watch-list-all-namespaces-daemonset-v1-apps","subsections":[]},{"section":"watch-list-daemonset-v1-apps","subsections":[]},{"section":"watch-daemonset-v1-apps","subsections":[]},{"section":"list-all-namespaces-daemonset-v1-apps","subsections":[]},{"section":"list-daemonset-v1-apps","subsections":[]},{"section":"read-daemonset-v1-apps","subsections":[]}]},{"section":"-strong-write-operations-daemonset-v1-apps-strong-","subsections":[{"section":"delete-collection-daemonset-v1-apps","subsections":[]},{"section":"delete-daemonset-v1-apps","subsections":[]},{"section":"replace-daemonset-v1-apps","subsections":[]},{"section":"patch-daemonset-v1-apps","subsections":[]},{"section":"create-daemonset-v1-apps","subsections":[]}]}]},{"section":"cronjob-v1-batch","subsections":[{"section":"-strong-status-operations-cronjob-v1-batch-strong-","subsections":[{"section":"replace-status-cronjob-v1-batch","subsections":[]},{"section":"read-status-cronjob-v1-batch","subsections":[]},{"section":"patch-status-cronjob-v1-batch","subsections":[]}]},{"section":"-strong-read-operations-cronjob-v1-batch-strong-","subsections":[{"section":"watch-list-all-namespaces-cronjob-v1-batch","subsections":[]},{"section":"watch-list-cronjob-v1-batch","subsections":[]},{"section":"watch-cronjob-v1-batch","subsections":[]},{"section":"list-all-namespaces-cronjob-v1-batch","subsections":[]},{"section":"list-cronjob-v1-batch","subsections":[]},{"section":"read-cronjob-v1-batch","subsections":[]}]},{"section":"-strong-write-operations-cronjob-v1-batch-strong-","subsections":[{"section":"delete-collection-cronjob-v1-batch","subsections":[]},{"section":"delete-cronjob-v1-batch","subsections":[]},{"section":"replace-cronjob-v1-batch","subsections":[]},{"section":"patch-cronjob-v1-batch","subsections":[]},{"section":"create-cronjob-v1-batch","subsections":[]}]}]},{"section":"container-v1-core","subsections":[]},{"section":"-strong-workloads-apis-strong-","subsections":[]},{"section":"-strong-api-groups-strong-","subsections":[]},{"section":"-strong-api-overview-strong-","subsections":[]}],"flatToc":["webhookclientconfig-v1-apiextensions-k8s-io","usersubject-v1beta1-flowcontrol-apiserver-k8s-io","tokenrequest-v1-storage-k8s-io","subject-v1beta1-flowcontrol-apiserver-k8s-io","subject-v1-rbac-authorization-k8s-io","servicereference-v1-apiregistration-k8s-io","servicereference-v1-apiextensions-k8s-io","serviceaccountsubject-v1beta1-flowcontrol-apiserver-k8s-io","scheduling-v1alpha1-node-k8s-io","scheduling-v1beta1-node-k8s-io","watch-list-runtimeclass-v1alpha1-node-k8s-io","watch-runtimeclass-v1alpha1-node-k8s-io","list-runtimeclass-v1alpha1-node-k8s-io","read-runtimeclass-v1alpha1-node-k8s-io","-strong-read-operations-runtimeclass-v1alpha1-node-k8s-io-strong-","delete-collection-runtimeclass-v1alpha1-node-k8s-io","delete-runtimeclass-v1alpha1-node-k8s-io","replace-runtimeclass-v1alpha1-node-k8s-io","patch-runtimeclass-v1alpha1-node-k8s-io","create-runtimeclass-v1alpha1-node-k8s-io","-strong-write-operations-runtimeclass-v1alpha1-node-k8s-io-strong-","runtimeclass-v1alpha1-node-k8s-io","watch-list-runtimeclass-v1beta1-node-k8s-io","watch-runtimeclass-v1beta1-node-k8s-io","list-runtimeclass-v1beta1-node-k8s-io","read-runtimeclass-v1beta1-node-k8s-io","-strong-read-operations-runtimeclass-v1beta1-node-k8s-io-strong-","delete-collection-runtimeclass-v1beta1-node-k8s-io","delete-runtimeclass-v1beta1-node-k8s-io","replace-runtimeclass-v1beta1-node-k8s-io","patch-runtimeclass-v1beta1-node-k8s-io","create-runtimeclass-v1beta1-node-k8s-io","-strong-write-operations-runtimeclass-v1beta1-node-k8s-io-strong-","runtimeclass-v1beta1-node-k8s-io","resourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io","resourcemetricstatus-v2beta1-autoscaling","resourcemetricstatus-v2beta2-autoscaling","resourcemetricsource-v2beta1-autoscaling","resourcemetricsource-v2beta2-autoscaling","queuingconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationreference-v1beta1-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationcondition-v1beta1-flowcontrol-apiserver-k8s-io","replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","policyruleswithsubjects-v1beta1-flowcontrol-apiserver-k8s-io","podsmetricstatus-v2beta1-autoscaling","podsmetricstatus-v2beta2-autoscaling","podsmetricsource-v2beta1-autoscaling","podsmetricsource-v2beta2-autoscaling","replace-status-poddisruptionbudget-v1beta1-policy","read-status-poddisruptionbudget-v1beta1-policy","patch-status-poddisruptionbudget-v1beta1-policy","-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-","watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy","watch-list-poddisruptionbudget-v1beta1-policy","watch-poddisruptionbudget-v1beta1-policy","list-all-namespaces-poddisruptionbudget-v1beta1-policy","list-poddisruptionbudget-v1beta1-policy","read-poddisruptionbudget-v1beta1-policy","-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-","delete-collection-poddisruptionbudget-v1beta1-policy","delete-poddisruptionbudget-v1beta1-policy","replace-poddisruptionbudget-v1beta1-policy","patch-poddisruptionbudget-v1beta1-policy","create-poddisruptionbudget-v1beta1-policy","-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-","poddisruptionbudget-v1beta1-policy","overhead-v1alpha1-node-k8s-io","overhead-v1beta1-node-k8s-io","objectmetricstatus-v2beta1-autoscaling","objectmetricstatus-v2beta2-autoscaling","objectmetricsource-v2beta1-autoscaling","objectmetricsource-v2beta2-autoscaling","nonresourcepolicyrule-v1beta1-flowcontrol-apiserver-k8s-io","metricvaluestatus-v2beta2-autoscaling","metrictarget-v2beta2-autoscaling","metricstatus-v2beta1-autoscaling","metricstatus-v2beta2-autoscaling","metricspec-v2beta1-autoscaling","metricspec-v2beta2-autoscaling","metricidentifier-v2beta2-autoscaling","limitedprioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","limitresponse-v1beta1-flowcontrol-apiserver-k8s-io","jobtemplatespec-v1beta1-batch","horizontalpodautoscalercondition-v2beta1-autoscaling","horizontalpodautoscalercondition-v2beta2-autoscaling","horizontalpodautoscalerbehavior-v2beta2-autoscaling","replace-status-horizontalpodautoscaler-v2beta1-autoscaling","read-status-horizontalpodautoscaler-v2beta1-autoscaling","patch-status-horizontalpodautoscaler-v2beta1-autoscaling","-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling","watch-list-horizontalpodautoscaler-v2beta1-autoscaling","watch-horizontalpodautoscaler-v2beta1-autoscaling","list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling","list-horizontalpodautoscaler-v2beta1-autoscaling","read-horizontalpodautoscaler-v2beta1-autoscaling","-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","delete-collection-horizontalpodautoscaler-v2beta1-autoscaling","delete-horizontalpodautoscaler-v2beta1-autoscaling","replace-horizontalpodautoscaler-v2beta1-autoscaling","patch-horizontalpodautoscaler-v2beta1-autoscaling","create-horizontalpodautoscaler-v2beta1-autoscaling","-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-","horizontalpodautoscaler-v2beta1-autoscaling","replace-status-horizontalpodautoscaler-v2beta2-autoscaling","read-status-horizontalpodautoscaler-v2beta2-autoscaling","patch-status-horizontalpodautoscaler-v2beta2-autoscaling","-strong-status-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","watch-list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling","watch-list-horizontalpodautoscaler-v2beta2-autoscaling","watch-horizontalpodautoscaler-v2beta2-autoscaling","list-all-namespaces-horizontalpodautoscaler-v2beta2-autoscaling","list-horizontalpodautoscaler-v2beta2-autoscaling","read-horizontalpodautoscaler-v2beta2-autoscaling","-strong-read-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","delete-collection-horizontalpodautoscaler-v2beta2-autoscaling","delete-horizontalpodautoscaler-v2beta2-autoscaling","replace-horizontalpodautoscaler-v2beta2-autoscaling","patch-horizontalpodautoscaler-v2beta2-autoscaling","create-horizontalpodautoscaler-v2beta2-autoscaling","-strong-write-operations-horizontalpodautoscaler-v2beta2-autoscaling-strong-","horizontalpodautoscaler-v2beta2-autoscaling","replace-status-horizontalpodautoscaler-v1-autoscaling","read-status-horizontalpodautoscaler-v1-autoscaling","patch-status-horizontalpodautoscaler-v1-autoscaling","-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-","watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","watch-list-horizontalpodautoscaler-v1-autoscaling","watch-horizontalpodautoscaler-v1-autoscaling","list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","list-horizontalpodautoscaler-v1-autoscaling","read-horizontalpodautoscaler-v1-autoscaling","-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-","delete-collection-horizontalpodautoscaler-v1-autoscaling","delete-horizontalpodautoscaler-v1-autoscaling","replace-horizontalpodautoscaler-v1-autoscaling","patch-horizontalpodautoscaler-v1-autoscaling","create-horizontalpodautoscaler-v1-autoscaling","-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-","horizontalpodautoscaler-v1-autoscaling","hpascalingrules-v2beta2-autoscaling","hpascalingpolicy-v2beta2-autoscaling","groupsubject-v1beta1-flowcontrol-apiserver-k8s-io","forzone-v1beta1-discovery-k8s-io","flowschemacondition-v1beta1-flowcontrol-apiserver-k8s-io","replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","flowschema-v1beta1-flowcontrol-apiserver-k8s-io","flowdistinguishermethod-v1beta1-flowcontrol-apiserver-k8s-io","externalmetricstatus-v2beta1-autoscaling","externalmetricstatus-v2beta2-autoscaling","externalmetricsource-v2beta1-autoscaling","externalmetricsource-v2beta2-autoscaling","eventseries-v1beta1-events-k8s-io","eventseries-v1-core","watch-list-all-namespaces-event-v1beta1-events-k8s-io","watch-list-event-v1beta1-events-k8s-io","watch-event-v1beta1-events-k8s-io","list-all-namespaces-event-v1beta1-events-k8s-io","list-event-v1beta1-events-k8s-io","read-event-v1beta1-events-k8s-io","-strong-read-operations-event-v1beta1-events-k8s-io-strong-","delete-collection-event-v1beta1-events-k8s-io","delete-event-v1beta1-events-k8s-io","replace-event-v1beta1-events-k8s-io","patch-event-v1beta1-events-k8s-io","create-event-v1beta1-events-k8s-io","-strong-write-operations-event-v1beta1-events-k8s-io-strong-","event-v1beta1-events-k8s-io","watch-list-all-namespaces-event-v1-core","watch-list-event-v1-core","watch-event-v1-core","list-all-namespaces-event-v1-core","list-event-v1-core","read-event-v1-core","-strong-read-operations-event-v1-core-strong-","delete-collection-event-v1-core","delete-event-v1-core","replace-event-v1-core","patch-event-v1-core","create-event-v1-core","-strong-write-operations-event-v1-core-strong-","event-v1-core","watch-list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io","watch-list-endpointslice-v1beta1-discovery-k8s-io","watch-endpointslice-v1beta1-discovery-k8s-io","list-all-namespaces-endpointslice-v1beta1-discovery-k8s-io","list-endpointslice-v1beta1-discovery-k8s-io","read-endpointslice-v1beta1-discovery-k8s-io","-strong-read-operations-endpointslice-v1beta1-discovery-k8s-io-strong-","delete-collection-endpointslice-v1beta1-discovery-k8s-io","delete-endpointslice-v1beta1-discovery-k8s-io","replace-endpointslice-v1beta1-discovery-k8s-io","patch-endpointslice-v1beta1-discovery-k8s-io","create-endpointslice-v1beta1-discovery-k8s-io","-strong-write-operations-endpointslice-v1beta1-discovery-k8s-io-strong-","endpointslice-v1beta1-discovery-k8s-io","endpointport-v1beta1-discovery-k8s-io","endpointport-v1-discovery-k8s-io","endpointhints-v1beta1-discovery-k8s-io","endpointconditions-v1beta1-discovery-k8s-io","endpoint-v1beta1-discovery-k8s-io","crossversionobjectreference-v2beta1-autoscaling","crossversionobjectreference-v2beta2-autoscaling","crossversionobjectreference-v2-autoscaling","replace-status-cronjob-v1beta1-batch","read-status-cronjob-v1beta1-batch","patch-status-cronjob-v1beta1-batch","-strong-status-operations-cronjob-v1beta1-batch-strong-","watch-list-all-namespaces-cronjob-v1beta1-batch","watch-list-cronjob-v1beta1-batch","watch-cronjob-v1beta1-batch","list-all-namespaces-cronjob-v1beta1-batch","list-cronjob-v1beta1-batch","read-cronjob-v1beta1-batch","-strong-read-operations-cronjob-v1beta1-batch-strong-","delete-collection-cronjob-v1beta1-batch","delete-cronjob-v1beta1-batch","replace-cronjob-v1beta1-batch","patch-cronjob-v1beta1-batch","create-cronjob-v1beta1-batch","-strong-write-operations-cronjob-v1beta1-batch-strong-","cronjob-v1beta1-batch","containerresourcemetricstatus-v2beta1-autoscaling","containerresourcemetricstatus-v2beta2-autoscaling","containerresourcemetricsource-v2beta1-autoscaling","containerresourcemetricsource-v2beta2-autoscaling","watch-list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io","watch-list-csistoragecapacity-v1alpha1-storage-k8s-io","watch-csistoragecapacity-v1alpha1-storage-k8s-io","list-all-namespaces-csistoragecapacity-v1alpha1-storage-k8s-io","list-csistoragecapacity-v1alpha1-storage-k8s-io","read-csistoragecapacity-v1alpha1-storage-k8s-io","-strong-read-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-","delete-collection-csistoragecapacity-v1alpha1-storage-k8s-io","delete-csistoragecapacity-v1alpha1-storage-k8s-io","replace-csistoragecapacity-v1alpha1-storage-k8s-io","patch-csistoragecapacity-v1alpha1-storage-k8s-io","create-csistoragecapacity-v1alpha1-storage-k8s-io","-strong-write-operations-csistoragecapacity-v1alpha1-storage-k8s-io-strong-","csistoragecapacity-v1alpha1-storage-k8s-io","-strong-old-api-versions-strong-","windowssecuritycontextoptions-v1-core","weightedpodaffinityterm-v1-core","webhookconversion-v1-apiextensions-k8s-io","webhookclientconfig-v1-admissionregistration-k8s-io","watchevent-v1-meta","vspherevirtualdiskvolumesource-v1-core","volumeprojection-v1-core","volumenoderesources-v1-storage-k8s-io","volumenodeaffinity-v1-core","volumemount-v1-core","volumeerror-v1-storage-k8s-io","volumedevice-v1-core","volumeattachmentsource-v1-storage-k8s-io","validationrule-v1-apiextensions-k8s-io","validatingwebhook-v1-admissionregistration-k8s-io","usersubject-v1beta2-flowcontrol-apiserver-k8s-io","userinfo-v1-authentication-k8s-io","uncountedterminatedpods-v1-batch","typedlocalobjectreference-v1-core","topologyspreadconstraint-v1-core","topologyselectorterm-v1-core","topologyselectorlabelrequirement-v1-core","toleration-v1-core","time-v1-meta","taint-v1-core","tcpsocketaction-v1-core","sysctl-v1-core","supplementalgroupsstrategyoptions-v1beta1-policy","subjectrulesreviewstatus-v1-authorization-k8s-io","subject-v1beta2-flowcontrol-apiserver-k8s-io","storageversioncondition-v1alpha1-internal-apiserver-k8s-io","storageosvolumesource-v1-core","storageospersistentvolumesource-v1-core","statusdetails-v1-meta","statuscause-v1-meta","status-v1-meta","statefulsetupdatestrategy-v1-apps","statefulsetpersistentvolumeclaimretentionpolicy-v1-apps","statefulsetcondition-v1-apps","sessionaffinityconfig-v1-core","servicereference-v1-admissionregistration-k8s-io","serviceport-v1-core","servicebackendport-v1-networking-k8s-io","serviceaccounttokenprojection-v1-core","serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io","serverstorageversion-v1alpha1-internal-apiserver-k8s-io","serveraddressbyclientcidr-v1-meta","securitycontext-v1-core","secretvolumesource-v1-core","secretreference-v1-core","secretprojection-v1-core","secretkeyselector-v1-core","secretenvsource-v1-core","seccompprofile-v1-core","scopedresourceselectorrequirement-v1-core","scopeselector-v1-core","scheduling-v1-node-k8s-io","scaleiovolumesource-v1-core","scaleiopersistentvolumesource-v1-core","scale-v1-autoscaling","selinuxstrategyoptions-v1beta1-policy","selinuxoptions-v1-core","runtimeclassstrategyoptions-v1beta1-policy","runasuserstrategyoptions-v1beta1-policy","runasgroupstrategyoptions-v1beta1-policy","rulewithoperations-v1-admissionregistration-k8s-io","rollingupdatestatefulsetstrategy-v1-apps","roleref-v1-rbac-authorization-k8s-io","resourcerule-v1-authorization-k8s-io","resourcerequirements-v1-core","resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","resourcemetricstatus-v2-autoscaling","resourcemetricsource-v2-autoscaling","resourcefieldselector-v1-core","resourceattributes-v1-authorization-k8s-io","replicationcontrollercondition-v1-core","replicasetcondition-v1-apps","rbdvolumesource-v1-core","rbdpersistentvolumesource-v1-core","quobytevolumesource-v1-core","queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","quantity-resource-core","projectedvolumesource-v1-core","probe-v1-core","prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io","prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","preferredschedulingterm-v1-core","preconditions-v1-meta","portworxvolumesource-v1-core","portstatus-v1-core","policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io","policyrule-v1-rbac-authorization-k8s-io","podsmetricstatus-v2-autoscaling","podsmetricsource-v2-autoscaling","podsecuritycontext-v1-core","podreadinessgate-v1-core","podos-v1-core","podip-v1-core","poddnsconfigoption-v1-core","poddnsconfig-v1-core","podcondition-v1-core","podantiaffinity-v1-core","podaffinityterm-v1-core","podaffinity-v1-core","photonpersistentdiskvolumesource-v1-core","persistentvolumeclaimvolumesource-v1-core","persistentvolumeclaimtemplate-v1-core","persistentvolumeclaimcondition-v1-core","patch-v1-meta","ownerreference-v1-meta","overhead-v1-node-k8s-io","objectreference-v1-core","objectmetricstatus-v2-autoscaling","objectmetricsource-v2-autoscaling","objectmeta-v1-meta","objectfieldselector-v1-core","nonresourcerule-v1-authorization-k8s-io","nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","nonresourceattributes-v1-authorization-k8s-io","nodesysteminfo-v1-core","nodeselectorterm-v1-core","nodeselectorrequirement-v1-core","nodeselector-v1-core","nodedaemonendpoints-v1-core","nodeconfigstatus-v1-core","nodeconfigsource-v1-core","nodecondition-v1-core","nodeaffinity-v1-core","nodeaddress-v1-core","networkpolicyport-v1-networking-k8s-io","networkpolicypeer-v1-networking-k8s-io","networkpolicyingressrule-v1-networking-k8s-io","networkpolicyegressrule-v1-networking-k8s-io","namespacecondition-v1-core","nfsvolumesource-v1-core","mutatingwebhook-v1-admissionregistration-k8s-io","microtime-v1-meta","metricvaluestatus-v2-autoscaling","metrictarget-v2-autoscaling","metricstatus-v2-autoscaling","metricspec-v2-autoscaling","metricidentifier-v2-autoscaling","managedfieldsentry-v1-meta","localvolumesource-v1-core","localobjectreference-v1-core","loadbalancerstatus-v1-core","loadbalanceringress-v1-core","listmeta-v1-meta","limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","limitresponse-v1beta2-flowcontrol-apiserver-k8s-io","limitrangeitem-v1-core","lifecyclehandler-v1-core","lifecycle-v1-core","labelselectorrequirement-v1-meta","labelselector-v1-meta","keytopath-v1-core","jobtemplatespec-v1-batch","jobcondition-v1-batch","jsonschemapropsorbool-v1-apiextensions-k8s-io","jsonschemapropsorarray-v1-apiextensions-k8s-io","jsonschemaprops-v1-apiextensions-k8s-io","json-v1-apiextensions-k8s-io","ingresstls-v1-networking-k8s-io","ingressservicebackend-v1-networking-k8s-io","ingressrule-v1-networking-k8s-io","ingressclassparametersreference-v1-networking-k8s-io","ingressbackend-v1-networking-k8s-io","iscsivolumesource-v1-core","iscsipersistentvolumesource-v1-core","ipblock-v1-networking-k8s-io","idrange-v1beta1-policy","hostportrange-v1beta1-policy","hostpathvolumesource-v1-core","hostalias-v1-core","horizontalpodautoscalercondition-v2-autoscaling","horizontalpodautoscalerbehavior-v2-autoscaling","horizontalpodautoscaler-v2-autoscaling","httpingressrulevalue-v1-networking-k8s-io","httpingresspath-v1-networking-k8s-io","httpheader-v1-core","httpgetaction-v1-core","hpascalingrules-v2-autoscaling","hpascalingpolicy-v2-autoscaling","groupversionfordiscovery-v1-meta","groupsubject-v1beta2-flowcontrol-apiserver-k8s-io","glusterfsvolumesource-v1-core","glusterfspersistentvolumesource-v1-core","gitrepovolumesource-v1-core","grpcaction-v1-core","gcepersistentdiskvolumesource-v1-core","forzone-v1-discovery-k8s-io","flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io","flowschema-v1beta2-flowcontrol-apiserver-k8s-io","flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io","flockervolumesource-v1-core","flexvolumesource-v1-core","flexpersistentvolumesource-v1-core","fieldsv1-v1-meta","fsgroupstrategyoptions-v1beta1-policy","fcvolumesource-v1-core","externalmetricstatus-v2-autoscaling","externalmetricsource-v2-autoscaling","externaldocumentation-v1-apiextensions-k8s-io","execaction-v1-core","eviction-v1-policy","eventsource-v1-core","eventseries-v1-events-k8s-io","ephemeralvolumesource-v1-core","ephemeralcontainer-v1-core","envvarsource-v1-core","envvar-v1-core","envfromsource-v1-core","endpointsubset-v1-core","endpointport-v1-core","endpointhints-v1-discovery-k8s-io","endpointconditions-v1-discovery-k8s-io","endpointaddress-v1-core","endpoint-v1-discovery-k8s-io","emptydirvolumesource-v1-core","downwardapivolumesource-v1-core","downwardapivolumefile-v1-core","downwardapiprojection-v1-core","deploymentcondition-v1-apps","deleteoptions-v1-meta","daemonsetupdatestrategy-v1-apps","daemonsetcondition-v1-apps","daemonendpoint-v1-core","customresourcevalidation-v1-apiextensions-k8s-io","customresourcesubresources-v1-apiextensions-k8s-io","customresourcesubresourcestatus-v1-apiextensions-k8s-io","customresourcesubresourcescale-v1-apiextensions-k8s-io","customresourcedefinitionversion-v1-apiextensions-k8s-io","customresourcedefinitionnames-v1-apiextensions-k8s-io","customresourcedefinitioncondition-v1-apiextensions-k8s-io","customresourceconversion-v1-apiextensions-k8s-io","customresourcecolumndefinition-v1-apiextensions-k8s-io","crossversionobjectreference-v1-autoscaling","containerstatewaiting-v1-core","containerstateterminated-v1-core","containerstaterunning-v1-core","containerstate-v1-core","containerresourcemetricstatus-v2-autoscaling","containerresourcemetricsource-v2-autoscaling","containerport-v1-core","containerimage-v1-core","configmapvolumesource-v1-core","configmapprojection-v1-core","configmapnodeconfigsource-v1-core","configmapkeyselector-v1-core","configmapenvsource-v1-core","condition-v1-meta","componentcondition-v1-core","clientipconfig-v1-core","cindervolumesource-v1-core","cinderpersistentvolumesource-v1-core","certificatesigningrequestcondition-v1-certificates-k8s-io","cephfsvolumesource-v1-core","cephfspersistentvolumesource-v1-core","capabilities-v1-core","csivolumesource-v1-core","csipersistentvolumesource-v1-core","csinodedriver-v1-storage-k8s-io","boundobjectreference-v1-authentication-k8s-io","azurefilevolumesource-v1-core","azurefilepersistentvolumesource-v1-core","azurediskvolumesource-v1-core","attachedvolume-v1-core","allowedhostpath-v1beta1-policy","allowedflexvolume-v1beta1-policy","allowedcsidriver-v1beta1-policy","aggregationrule-v1-rbac-authorization-k8s-io","affinity-v1-core","awselasticblockstorevolumesource-v1-core","apiversions-v1-meta","apiservicecondition-v1-apiregistration-k8s-io","apiresource-v1-meta","apigroup-v1-meta","-strong-definitions-strong-","watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io","watch-list-networkpolicy-v1-networking-k8s-io","watch-networkpolicy-v1-networking-k8s-io","list-all-namespaces-networkpolicy-v1-networking-k8s-io","list-networkpolicy-v1-networking-k8s-io","read-networkpolicy-v1-networking-k8s-io","-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-","delete-collection-networkpolicy-v1-networking-k8s-io","delete-networkpolicy-v1-networking-k8s-io","replace-networkpolicy-v1-networking-k8s-io","patch-networkpolicy-v1-networking-k8s-io","create-networkpolicy-v1-networking-k8s-io","-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-","networkpolicy-v1-networking-k8s-io","create-tokenreview-v1-authentication-k8s-io","-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-","tokenreview-v1-authentication-k8s-io","tokenrequest-v1-authentication-k8s-io","create-subjectaccessreview-v1-authorization-k8s-io","-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-","subjectaccessreview-v1-authorization-k8s-io","replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io","read-status-storageversion-v1alpha1-internal-apiserver-k8s-io","patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io","-strong-status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io","watch-storageversion-v1alpha1-internal-apiserver-k8s-io","list-storageversion-v1alpha1-internal-apiserver-k8s-io","read-storageversion-v1alpha1-internal-apiserver-k8s-io","-strong-read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io","delete-storageversion-v1alpha1-internal-apiserver-k8s-io","replace-storageversion-v1alpha1-internal-apiserver-k8s-io","patch-storageversion-v1alpha1-internal-apiserver-k8s-io","create-storageversion-v1alpha1-internal-apiserver-k8s-io","-strong-write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-strong-","storageversion-v1alpha1-internal-apiserver-k8s-io","watch-list-all-namespaces-serviceaccount-v1-core","watch-list-serviceaccount-v1-core","watch-serviceaccount-v1-core","list-all-namespaces-serviceaccount-v1-core","list-serviceaccount-v1-core","read-serviceaccount-v1-core","-strong-read-operations-serviceaccount-v1-core-strong-","delete-collection-serviceaccount-v1-core","delete-serviceaccount-v1-core","replace-serviceaccount-v1-core","patch-serviceaccount-v1-core","create-serviceaccount-v1-core","-strong-write-operations-serviceaccount-v1-core-strong-","serviceaccount-v1-core","create-selfsubjectrulesreview-v1-authorization-k8s-io","-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-","selfsubjectrulesreview-v1-authorization-k8s-io","create-selfsubjectaccessreview-v1-authorization-k8s-io","-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-","selfsubjectaccessreview-v1-authorization-k8s-io","watch-list-runtimeclass-v1-node-k8s-io","watch-runtimeclass-v1-node-k8s-io","list-runtimeclass-v1-node-k8s-io","read-runtimeclass-v1-node-k8s-io","-strong-read-operations-runtimeclass-v1-node-k8s-io-strong-","delete-collection-runtimeclass-v1-node-k8s-io","delete-runtimeclass-v1-node-k8s-io","replace-runtimeclass-v1-node-k8s-io","patch-runtimeclass-v1-node-k8s-io","create-runtimeclass-v1-node-k8s-io","-strong-write-operations-runtimeclass-v1-node-k8s-io-strong-","runtimeclass-v1-node-k8s-io","watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io","watch-list-rolebinding-v1-rbac-authorization-k8s-io","watch-rolebinding-v1-rbac-authorization-k8s-io","list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io","list-rolebinding-v1-rbac-authorization-k8s-io","read-rolebinding-v1-rbac-authorization-k8s-io","-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-","delete-collection-rolebinding-v1-rbac-authorization-k8s-io","delete-rolebinding-v1-rbac-authorization-k8s-io","replace-rolebinding-v1-rbac-authorization-k8s-io","patch-rolebinding-v1-rbac-authorization-k8s-io","create-rolebinding-v1-rbac-authorization-k8s-io","-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-","rolebinding-v1-rbac-authorization-k8s-io","watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io","watch-list-role-v1-rbac-authorization-k8s-io","watch-role-v1-rbac-authorization-k8s-io","list-all-namespaces-role-v1-rbac-authorization-k8s-io","list-role-v1-rbac-authorization-k8s-io","read-role-v1-rbac-authorization-k8s-io","-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-","delete-collection-role-v1-rbac-authorization-k8s-io","delete-role-v1-rbac-authorization-k8s-io","replace-role-v1-rbac-authorization-k8s-io","patch-role-v1-rbac-authorization-k8s-io","create-role-v1-rbac-authorization-k8s-io","-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-","role-v1-rbac-authorization-k8s-io","replace-status-resourcequota-v1-core","read-status-resourcequota-v1-core","patch-status-resourcequota-v1-core","-strong-status-operations-resourcequota-v1-core-strong-","watch-list-all-namespaces-resourcequota-v1-core","watch-list-resourcequota-v1-core","watch-resourcequota-v1-core","list-all-namespaces-resourcequota-v1-core","list-resourcequota-v1-core","read-resourcequota-v1-core","-strong-read-operations-resourcequota-v1-core-strong-","delete-collection-resourcequota-v1-core","delete-resourcequota-v1-core","replace-resourcequota-v1-core","patch-resourcequota-v1-core","create-resourcequota-v1-core","-strong-write-operations-resourcequota-v1-core-strong-","resourcequota-v1-core","replace-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","read-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","patch-status-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-status-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","watch-list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","watch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","list-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","read-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-read-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","delete-collection-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","delete-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","replace-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","patch-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","create-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","-strong-write-operations-prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io-strong-","prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io","replace-status-persistentvolume-v1-core","read-status-persistentvolume-v1-core","patch-status-persistentvolume-v1-core","-strong-status-operations-persistentvolume-v1-core-strong-","watch-list-persistentvolume-v1-core","watch-persistentvolume-v1-core","list-persistentvolume-v1-core","read-persistentvolume-v1-core","-strong-read-operations-persistentvolume-v1-core-strong-","delete-collection-persistentvolume-v1-core","delete-persistentvolume-v1-core","replace-persistentvolume-v1-core","patch-persistentvolume-v1-core","create-persistentvolume-v1-core","-strong-write-operations-persistentvolume-v1-core-strong-","persistentvolume-v1-core","replace-connect-proxy-path-node-v1-core","replace-connect-proxy-node-v1-core","head-connect-proxy-path-node-v1-core","head-connect-proxy-node-v1-core","get-connect-proxy-path-node-v1-core","get-connect-proxy-node-v1-core","delete-connect-proxy-path-node-v1-core","delete-connect-proxy-node-v1-core","create-connect-proxy-path-node-v1-core","create-connect-proxy-node-v1-core","-strong-proxy-operations-node-v1-core-strong-","replace-status-node-v1-core","read-status-node-v1-core","patch-status-node-v1-core","-strong-status-operations-node-v1-core-strong-","watch-list-node-v1-core","watch-node-v1-core","list-node-v1-core","read-node-v1-core","-strong-read-operations-node-v1-core-strong-","delete-collection-node-v1-core","delete-node-v1-core","replace-node-v1-core","patch-node-v1-core","create-node-v1-core","-strong-write-operations-node-v1-core-strong-","node-v1-core","replace-status-namespace-v1-core","read-status-namespace-v1-core","patch-status-namespace-v1-core","-strong-status-operations-namespace-v1-core-strong-","watch-list-namespace-v1-core","watch-namespace-v1-core","list-namespace-v1-core","read-namespace-v1-core","-strong-read-operations-namespace-v1-core-strong-","delete-namespace-v1-core","replace-namespace-v1-core","patch-namespace-v1-core","create-namespace-v1-core","-strong-write-operations-namespace-v1-core-strong-","namespace-v1-core","create-localsubjectaccessreview-v1-authorization-k8s-io","-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-","localsubjectaccessreview-v1-authorization-k8s-io","watch-list-all-namespaces-lease-v1-coordination-k8s-io","watch-list-lease-v1-coordination-k8s-io","watch-lease-v1-coordination-k8s-io","list-all-namespaces-lease-v1-coordination-k8s-io","list-lease-v1-coordination-k8s-io","read-lease-v1-coordination-k8s-io","-strong-read-operations-lease-v1-coordination-k8s-io-strong-","delete-collection-lease-v1-coordination-k8s-io","delete-lease-v1-coordination-k8s-io","replace-lease-v1-coordination-k8s-io","patch-lease-v1-coordination-k8s-io","create-lease-v1-coordination-k8s-io","-strong-write-operations-lease-v1-coordination-k8s-io-strong-","lease-v1-coordination-k8s-io","replace-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","read-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","patch-status-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-status-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","watch-list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","watch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","list-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","read-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-read-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","delete-collection-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","delete-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","replace-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","patch-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","create-flowschema-v1beta1-flowcontrol-apiserver-k8s-io","-strong-write-operations-flowschema-v1beta1-flowcontrol-apiserver-k8s-io-strong-","flowschema-v1beta1-flowcontrol-apiserver-k8s-io","list-componentstatus-v1-core","read-componentstatus-v1-core","-strong-read-operations-componentstatus-v1-core-strong-","componentstatus-v1-core","watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io","watch-clusterrolebinding-v1-rbac-authorization-k8s-io","list-clusterrolebinding-v1-rbac-authorization-k8s-io","read-clusterrolebinding-v1-rbac-authorization-k8s-io","-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-","delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io","delete-clusterrolebinding-v1-rbac-authorization-k8s-io","replace-clusterrolebinding-v1-rbac-authorization-k8s-io","patch-clusterrolebinding-v1-rbac-authorization-k8s-io","create-clusterrolebinding-v1-rbac-authorization-k8s-io","-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-","clusterrolebinding-v1-rbac-authorization-k8s-io","watch-list-clusterrole-v1-rbac-authorization-k8s-io","watch-clusterrole-v1-rbac-authorization-k8s-io","list-clusterrole-v1-rbac-authorization-k8s-io","read-clusterrole-v1-rbac-authorization-k8s-io","-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-","delete-collection-clusterrole-v1-rbac-authorization-k8s-io","delete-clusterrole-v1-rbac-authorization-k8s-io","replace-clusterrole-v1-rbac-authorization-k8s-io","patch-clusterrole-v1-rbac-authorization-k8s-io","create-clusterrole-v1-rbac-authorization-k8s-io","-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-","clusterrole-v1-rbac-authorization-k8s-io","replace-status-certificatesigningrequest-v1-certificates-k8s-io","read-status-certificatesigningrequest-v1-certificates-k8s-io","patch-status-certificatesigningrequest-v1-certificates-k8s-io","-strong-status-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","watch-list-certificatesigningrequest-v1-certificates-k8s-io","watch-certificatesigningrequest-v1-certificates-k8s-io","list-certificatesigningrequest-v1-certificates-k8s-io","read-certificatesigningrequest-v1-certificates-k8s-io","-strong-read-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","delete-collection-certificatesigningrequest-v1-certificates-k8s-io","delete-certificatesigningrequest-v1-certificates-k8s-io","replace-certificatesigningrequest-v1-certificates-k8s-io","patch-certificatesigningrequest-v1-certificates-k8s-io","create-certificatesigningrequest-v1-certificates-k8s-io","-strong-write-operations-certificatesigningrequest-v1-certificates-k8s-io-strong-","certificatesigningrequest-v1-certificates-k8s-io","create-binding-v1-core","-strong-write-operations-binding-v1-core-strong-","binding-v1-core","replace-status-apiservice-v1-apiregistration-k8s-io","read-status-apiservice-v1-apiregistration-k8s-io","patch-status-apiservice-v1-apiregistration-k8s-io","-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-","watch-list-apiservice-v1-apiregistration-k8s-io","watch-apiservice-v1-apiregistration-k8s-io","list-apiservice-v1-apiregistration-k8s-io","read-apiservice-v1-apiregistration-k8s-io","-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-","delete-collection-apiservice-v1-apiregistration-k8s-io","delete-apiservice-v1-apiregistration-k8s-io","replace-apiservice-v1-apiregistration-k8s-io","patch-apiservice-v1-apiregistration-k8s-io","create-apiservice-v1-apiregistration-k8s-io","-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-","apiservice-v1-apiregistration-k8s-io","-strong-cluster-apis-strong-","watch-list-podsecuritypolicy-v1beta1-policy","watch-podsecuritypolicy-v1beta1-policy","list-podsecuritypolicy-v1beta1-policy","read-podsecuritypolicy-v1beta1-policy","-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-","delete-collection-podsecuritypolicy-v1beta1-policy","delete-podsecuritypolicy-v1beta1-policy","replace-podsecuritypolicy-v1beta1-policy","patch-podsecuritypolicy-v1beta1-policy","create-podsecuritypolicy-v1beta1-policy","-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-","podsecuritypolicy-v1beta1-policy","watch-list-priorityclass-v1-scheduling-k8s-io","watch-priorityclass-v1-scheduling-k8s-io","list-priorityclass-v1-scheduling-k8s-io","read-priorityclass-v1-scheduling-k8s-io","-strong-read-operations-priorityclass-v1-scheduling-k8s-io-strong-","delete-collection-priorityclass-v1-scheduling-k8s-io","delete-priorityclass-v1-scheduling-k8s-io","replace-priorityclass-v1-scheduling-k8s-io","patch-priorityclass-v1-scheduling-k8s-io","create-priorityclass-v1-scheduling-k8s-io","-strong-write-operations-priorityclass-v1-scheduling-k8s-io-strong-","priorityclass-v1-scheduling-k8s-io","replace-status-poddisruptionbudget-v1-policy","read-status-poddisruptionbudget-v1-policy","patch-status-poddisruptionbudget-v1-policy","-strong-status-operations-poddisruptionbudget-v1-policy-strong-","watch-list-all-namespaces-poddisruptionbudget-v1-policy","watch-list-poddisruptionbudget-v1-policy","watch-poddisruptionbudget-v1-policy","list-all-namespaces-poddisruptionbudget-v1-policy","list-poddisruptionbudget-v1-policy","read-poddisruptionbudget-v1-policy","-strong-read-operations-poddisruptionbudget-v1-policy-strong-","delete-collection-poddisruptionbudget-v1-policy","delete-poddisruptionbudget-v1-policy","replace-poddisruptionbudget-v1-policy","patch-poddisruptionbudget-v1-policy","create-poddisruptionbudget-v1-policy","-strong-write-operations-poddisruptionbudget-v1-policy-strong-","poddisruptionbudget-v1-policy","watch-list-all-namespaces-podtemplate-v1-core","watch-list-podtemplate-v1-core","watch-podtemplate-v1-core","list-all-namespaces-podtemplate-v1-core","list-podtemplate-v1-core","read-podtemplate-v1-core","-strong-read-operations-podtemplate-v1-core-strong-","delete-collection-podtemplate-v1-core","delete-podtemplate-v1-core","replace-podtemplate-v1-core","patch-podtemplate-v1-core","create-podtemplate-v1-core","-strong-write-operations-podtemplate-v1-core-strong-","podtemplate-v1-core","watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","-strong-read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io","-strong-write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","validatingwebhookconfiguration-v1-admissionregistration-k8s-io","watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","-strong-read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","-strong-write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-strong-","mutatingwebhookconfiguration-v1-admissionregistration-k8s-io","replace-status-horizontalpodautoscaler-v1-autoscaling","read-status-horizontalpodautoscaler-v1-autoscaling","patch-status-horizontalpodautoscaler-v1-autoscaling","-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-","watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","watch-list-horizontalpodautoscaler-v1-autoscaling","watch-horizontalpodautoscaler-v1-autoscaling","list-all-namespaces-horizontalpodautoscaler-v1-autoscaling","list-horizontalpodautoscaler-v1-autoscaling","read-horizontalpodautoscaler-v1-autoscaling","-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-","delete-collection-horizontalpodautoscaler-v1-autoscaling","delete-horizontalpodautoscaler-v1-autoscaling","replace-horizontalpodautoscaler-v1-autoscaling","patch-horizontalpodautoscaler-v1-autoscaling","create-horizontalpodautoscaler-v1-autoscaling","-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-","horizontalpodautoscaler-v1-autoscaling","watch-list-all-namespaces-limitrange-v1-core","watch-list-limitrange-v1-core","watch-limitrange-v1-core","list-all-namespaces-limitrange-v1-core","list-limitrange-v1-core","read-limitrange-v1-core","-strong-read-operations-limitrange-v1-core-strong-","delete-collection-limitrange-v1-core","delete-limitrange-v1-core","replace-limitrange-v1-core","patch-limitrange-v1-core","create-limitrange-v1-core","-strong-write-operations-limitrange-v1-core-strong-","limitrange-v1-core","watch-list-all-namespaces-event-v1-events-k8s-io","watch-list-event-v1-events-k8s-io","watch-event-v1-events-k8s-io","list-all-namespaces-event-v1-events-k8s-io","list-event-v1-events-k8s-io","read-event-v1-events-k8s-io","-strong-read-operations-event-v1-events-k8s-io-strong-","delete-collection-event-v1-events-k8s-io","delete-event-v1-events-k8s-io","replace-event-v1-events-k8s-io","patch-event-v1-events-k8s-io","create-event-v1-events-k8s-io","-strong-write-operations-event-v1-events-k8s-io-strong-","event-v1-events-k8s-io","replace-status-customresourcedefinition-v1-apiextensions-k8s-io","read-status-customresourcedefinition-v1-apiextensions-k8s-io","patch-status-customresourcedefinition-v1-apiextensions-k8s-io","-strong-status-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","watch-list-customresourcedefinition-v1-apiextensions-k8s-io","watch-customresourcedefinition-v1-apiextensions-k8s-io","list-customresourcedefinition-v1-apiextensions-k8s-io","read-customresourcedefinition-v1-apiextensions-k8s-io","-strong-read-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","delete-collection-customresourcedefinition-v1-apiextensions-k8s-io","delete-customresourcedefinition-v1-apiextensions-k8s-io","replace-customresourcedefinition-v1-apiextensions-k8s-io","patch-customresourcedefinition-v1-apiextensions-k8s-io","create-customresourcedefinition-v1-apiextensions-k8s-io","-strong-write-operations-customresourcedefinition-v1-apiextensions-k8s-io-strong-","customresourcedefinition-v1-apiextensions-k8s-io","watch-list-all-namespaces-controllerrevision-v1-apps","watch-list-controllerrevision-v1-apps","watch-controllerrevision-v1-apps","list-all-namespaces-controllerrevision-v1-apps","list-controllerrevision-v1-apps","read-controllerrevision-v1-apps","-strong-read-operations-controllerrevision-v1-apps-strong-","delete-collection-controllerrevision-v1-apps","delete-controllerrevision-v1-apps","replace-controllerrevision-v1-apps","patch-controllerrevision-v1-apps","create-controllerrevision-v1-apps","-strong-write-operations-controllerrevision-v1-apps-strong-","controllerrevision-v1-apps","-strong-metadata-apis-strong-","replace-status-volumeattachment-v1-storage-k8s-io","read-status-volumeattachment-v1-storage-k8s-io","patch-status-volumeattachment-v1-storage-k8s-io","-strong-status-operations-volumeattachment-v1-storage-k8s-io-strong-","watch-list-volumeattachment-v1-storage-k8s-io","watch-volumeattachment-v1-storage-k8s-io","list-volumeattachment-v1-storage-k8s-io","read-volumeattachment-v1-storage-k8s-io","-strong-read-operations-volumeattachment-v1-storage-k8s-io-strong-","delete-collection-volumeattachment-v1-storage-k8s-io","delete-volumeattachment-v1-storage-k8s-io","replace-volumeattachment-v1-storage-k8s-io","patch-volumeattachment-v1-storage-k8s-io","create-volumeattachment-v1-storage-k8s-io","-strong-write-operations-volumeattachment-v1-storage-k8s-io-strong-","volumeattachment-v1-storage-k8s-io","volume-v1-core","watch-list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io","watch-list-csistoragecapacity-v1beta1-storage-k8s-io","watch-csistoragecapacity-v1beta1-storage-k8s-io","list-all-namespaces-csistoragecapacity-v1beta1-storage-k8s-io","list-csistoragecapacity-v1beta1-storage-k8s-io","read-csistoragecapacity-v1beta1-storage-k8s-io","-strong-read-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-","delete-collection-csistoragecapacity-v1beta1-storage-k8s-io","delete-csistoragecapacity-v1beta1-storage-k8s-io","replace-csistoragecapacity-v1beta1-storage-k8s-io","patch-csistoragecapacity-v1beta1-storage-k8s-io","create-csistoragecapacity-v1beta1-storage-k8s-io","-strong-write-operations-csistoragecapacity-v1beta1-storage-k8s-io-strong-","csistoragecapacity-v1beta1-storage-k8s-io","watch-list-storageclass-v1-storage-k8s-io","watch-storageclass-v1-storage-k8s-io","list-storageclass-v1-storage-k8s-io","read-storageclass-v1-storage-k8s-io","-strong-read-operations-storageclass-v1-storage-k8s-io-strong-","delete-collection-storageclass-v1-storage-k8s-io","delete-storageclass-v1-storage-k8s-io","replace-storageclass-v1-storage-k8s-io","patch-storageclass-v1-storage-k8s-io","create-storageclass-v1-storage-k8s-io","-strong-write-operations-storageclass-v1-storage-k8s-io-strong-","storageclass-v1-storage-k8s-io","replace-status-persistentvolumeclaim-v1-core","read-status-persistentvolumeclaim-v1-core","patch-status-persistentvolumeclaim-v1-core","-strong-status-operations-persistentvolumeclaim-v1-core-strong-","watch-list-all-namespaces-persistentvolumeclaim-v1-core","watch-list-persistentvolumeclaim-v1-core","watch-persistentvolumeclaim-v1-core","list-all-namespaces-persistentvolumeclaim-v1-core","list-persistentvolumeclaim-v1-core","read-persistentvolumeclaim-v1-core","-strong-read-operations-persistentvolumeclaim-v1-core-strong-","delete-collection-persistentvolumeclaim-v1-core","delete-persistentvolumeclaim-v1-core","replace-persistentvolumeclaim-v1-core","patch-persistentvolumeclaim-v1-core","create-persistentvolumeclaim-v1-core","-strong-write-operations-persistentvolumeclaim-v1-core-strong-","persistentvolumeclaim-v1-core","watch-list-all-namespaces-secret-v1-core","watch-list-secret-v1-core","watch-secret-v1-core","list-all-namespaces-secret-v1-core","list-secret-v1-core","read-secret-v1-core","-strong-read-operations-secret-v1-core-strong-","delete-collection-secret-v1-core","delete-secret-v1-core","replace-secret-v1-core","patch-secret-v1-core","create-secret-v1-core","-strong-write-operations-secret-v1-core-strong-","secret-v1-core","watch-list-csinode-v1-storage-k8s-io","watch-csinode-v1-storage-k8s-io","list-csinode-v1-storage-k8s-io","read-csinode-v1-storage-k8s-io","-strong-read-operations-csinode-v1-storage-k8s-io-strong-","delete-collection-csinode-v1-storage-k8s-io","delete-csinode-v1-storage-k8s-io","replace-csinode-v1-storage-k8s-io","patch-csinode-v1-storage-k8s-io","create-csinode-v1-storage-k8s-io","-strong-write-operations-csinode-v1-storage-k8s-io-strong-","csinode-v1-storage-k8s-io","watch-list-csidriver-v1-storage-k8s-io","watch-csidriver-v1-storage-k8s-io","list-csidriver-v1-storage-k8s-io","read-csidriver-v1-storage-k8s-io","-strong-read-operations-csidriver-v1-storage-k8s-io-strong-","delete-collection-csidriver-v1-storage-k8s-io","delete-csidriver-v1-storage-k8s-io","replace-csidriver-v1-storage-k8s-io","patch-csidriver-v1-storage-k8s-io","create-csidriver-v1-storage-k8s-io","-strong-write-operations-csidriver-v1-storage-k8s-io-strong-","csidriver-v1-storage-k8s-io","watch-list-all-namespaces-configmap-v1-core","watch-list-configmap-v1-core","watch-configmap-v1-core","list-all-namespaces-configmap-v1-core","list-configmap-v1-core","read-configmap-v1-core","-strong-read-operations-configmap-v1-core-strong-","delete-collection-configmap-v1-core","delete-configmap-v1-core","replace-configmap-v1-core","patch-configmap-v1-core","create-configmap-v1-core","-strong-write-operations-configmap-v1-core-strong-","configmap-v1-core","-strong-config-and-storage-apis-strong-","replace-connect-proxy-path-service-v1-core","replace-connect-proxy-service-v1-core","head-connect-proxy-path-service-v1-core","head-connect-proxy-service-v1-core","get-connect-proxy-path-service-v1-core","get-connect-proxy-service-v1-core","delete-connect-proxy-path-service-v1-core","delete-connect-proxy-service-v1-core","create-connect-proxy-path-service-v1-core","create-connect-proxy-service-v1-core","-strong-proxy-operations-service-v1-core-strong-","replace-status-service-v1-core","read-status-service-v1-core","patch-status-service-v1-core","-strong-status-operations-service-v1-core-strong-","watch-list-all-namespaces-service-v1-core","watch-list-service-v1-core","watch-service-v1-core","list-all-namespaces-service-v1-core","list-service-v1-core","read-service-v1-core","-strong-read-operations-service-v1-core-strong-","delete-collection-service-v1-core","delete-service-v1-core","replace-service-v1-core","patch-service-v1-core","create-service-v1-core","-strong-write-operations-service-v1-core-strong-","service-v1-core","watch-list-ingressclass-v1-networking-k8s-io","watch-ingressclass-v1-networking-k8s-io","list-ingressclass-v1-networking-k8s-io","read-ingressclass-v1-networking-k8s-io","-strong-read-operations-ingressclass-v1-networking-k8s-io-strong-","delete-collection-ingressclass-v1-networking-k8s-io","delete-ingressclass-v1-networking-k8s-io","replace-ingressclass-v1-networking-k8s-io","patch-ingressclass-v1-networking-k8s-io","create-ingressclass-v1-networking-k8s-io","-strong-write-operations-ingressclass-v1-networking-k8s-io-strong-","ingressclass-v1-networking-k8s-io","replace-status-ingress-v1-networking-k8s-io","read-status-ingress-v1-networking-k8s-io","patch-status-ingress-v1-networking-k8s-io","-strong-status-operations-ingress-v1-networking-k8s-io-strong-","watch-list-all-namespaces-ingress-v1-networking-k8s-io","watch-list-ingress-v1-networking-k8s-io","watch-ingress-v1-networking-k8s-io","list-all-namespaces-ingress-v1-networking-k8s-io","list-ingress-v1-networking-k8s-io","read-ingress-v1-networking-k8s-io","-strong-read-operations-ingress-v1-networking-k8s-io-strong-","delete-collection-ingress-v1-networking-k8s-io","delete-ingress-v1-networking-k8s-io","replace-ingress-v1-networking-k8s-io","patch-ingress-v1-networking-k8s-io","create-ingress-v1-networking-k8s-io","-strong-write-operations-ingress-v1-networking-k8s-io-strong-","ingress-v1-networking-k8s-io","watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io","watch-list-endpointslice-v1-discovery-k8s-io","watch-endpointslice-v1-discovery-k8s-io","list-all-namespaces-endpointslice-v1-discovery-k8s-io","list-endpointslice-v1-discovery-k8s-io","read-endpointslice-v1-discovery-k8s-io","-strong-read-operations-endpointslice-v1-discovery-k8s-io-strong-","delete-collection-endpointslice-v1-discovery-k8s-io","delete-endpointslice-v1-discovery-k8s-io","replace-endpointslice-v1-discovery-k8s-io","patch-endpointslice-v1-discovery-k8s-io","create-endpointslice-v1-discovery-k8s-io","-strong-write-operations-endpointslice-v1-discovery-k8s-io-strong-","endpointslice-v1-discovery-k8s-io","watch-list-all-namespaces-endpoints-v1-core","watch-list-endpoints-v1-core","watch-endpoints-v1-core","list-all-namespaces-endpoints-v1-core","list-endpoints-v1-core","read-endpoints-v1-core","-strong-read-operations-endpoints-v1-core-strong-","delete-collection-endpoints-v1-core","delete-endpoints-v1-core","replace-endpoints-v1-core","patch-endpoints-v1-core","create-endpoints-v1-core","-strong-write-operations-endpoints-v1-core-strong-","endpoints-v1-core","-strong-service-apis-strong-","patch-scale-statefulset-v1-apps","replace-scale-statefulset-v1-apps","read-scale-statefulset-v1-apps","-strong-misc-operations-statefulset-v1-apps-strong-","replace-status-statefulset-v1-apps","read-status-statefulset-v1-apps","patch-status-statefulset-v1-apps","-strong-status-operations-statefulset-v1-apps-strong-","watch-list-all-namespaces-statefulset-v1-apps","watch-list-statefulset-v1-apps","watch-statefulset-v1-apps","list-all-namespaces-statefulset-v1-apps","list-statefulset-v1-apps","read-statefulset-v1-apps","-strong-read-operations-statefulset-v1-apps-strong-","delete-collection-statefulset-v1-apps","delete-statefulset-v1-apps","replace-statefulset-v1-apps","patch-statefulset-v1-apps","create-statefulset-v1-apps","-strong-write-operations-statefulset-v1-apps-strong-","statefulset-v1-apps","patch-scale-replicationcontroller-v1-core","replace-scale-replicationcontroller-v1-core","read-scale-replicationcontroller-v1-core","-strong-misc-operations-replicationcontroller-v1-core-strong-","replace-status-replicationcontroller-v1-core","read-status-replicationcontroller-v1-core","patch-status-replicationcontroller-v1-core","-strong-status-operations-replicationcontroller-v1-core-strong-","watch-list-all-namespaces-replicationcontroller-v1-core","watch-list-replicationcontroller-v1-core","watch-replicationcontroller-v1-core","list-all-namespaces-replicationcontroller-v1-core","list-replicationcontroller-v1-core","read-replicationcontroller-v1-core","-strong-read-operations-replicationcontroller-v1-core-strong-","delete-collection-replicationcontroller-v1-core","delete-replicationcontroller-v1-core","replace-replicationcontroller-v1-core","patch-replicationcontroller-v1-core","create-replicationcontroller-v1-core","-strong-write-operations-replicationcontroller-v1-core-strong-","replicationcontroller-v1-core","patch-scale-replicaset-v1-apps","replace-scale-replicaset-v1-apps","read-scale-replicaset-v1-apps","-strong-misc-operations-replicaset-v1-apps-strong-","replace-status-replicaset-v1-apps","read-status-replicaset-v1-apps","patch-status-replicaset-v1-apps","-strong-status-operations-replicaset-v1-apps-strong-","watch-list-all-namespaces-replicaset-v1-apps","watch-list-replicaset-v1-apps","watch-replicaset-v1-apps","list-all-namespaces-replicaset-v1-apps","list-replicaset-v1-apps","read-replicaset-v1-apps","-strong-read-operations-replicaset-v1-apps-strong-","delete-collection-replicaset-v1-apps","delete-replicaset-v1-apps","replace-replicaset-v1-apps","patch-replicaset-v1-apps","create-replicaset-v1-apps","-strong-write-operations-replicaset-v1-apps-strong-","replicaset-v1-apps","read-log-pod-v1-core","-strong-misc-operations-pod-v1-core-strong-","replace-connect-proxy-path-pod-v1-core","replace-connect-proxy-pod-v1-core","head-connect-proxy-path-pod-v1-core","head-connect-proxy-pod-v1-core","get-connect-proxy-path-pod-v1-core","get-connect-proxy-pod-v1-core","get-connect-portforward-pod-v1-core","delete-connect-proxy-path-pod-v1-core","delete-connect-proxy-pod-v1-core","create-connect-proxy-path-pod-v1-core","create-connect-proxy-pod-v1-core","create-connect-portforward-pod-v1-core","-strong-proxy-operations-pod-v1-core-strong-","replace-ephemeralcontainers-pod-v1-core","read-ephemeralcontainers-pod-v1-core","patch-ephemeralcontainers-pod-v1-core","-strong-ephemeralcontainers-operations-pod-v1-core-strong-","replace-status-pod-v1-core","read-status-pod-v1-core","patch-status-pod-v1-core","-strong-status-operations-pod-v1-core-strong-","watch-list-all-namespaces-pod-v1-core","watch-list-pod-v1-core","watch-pod-v1-core","list-all-namespaces-pod-v1-core","list-pod-v1-core","read-pod-v1-core","-strong-read-operations-pod-v1-core-strong-","delete-collection-pod-v1-core","delete-pod-v1-core","replace-pod-v1-core","patch-pod-v1-core","create-eviction-pod-v1-core","create-pod-v1-core","-strong-write-operations-pod-v1-core-strong-","pod-v1-core","replace-status-job-v1-batch","read-status-job-v1-batch","patch-status-job-v1-batch","-strong-status-operations-job-v1-batch-strong-","watch-list-all-namespaces-job-v1-batch","watch-list-job-v1-batch","watch-job-v1-batch","list-all-namespaces-job-v1-batch","list-job-v1-batch","read-job-v1-batch","-strong-read-operations-job-v1-batch-strong-","delete-collection-job-v1-batch","delete-job-v1-batch","replace-job-v1-batch","patch-job-v1-batch","create-job-v1-batch","-strong-write-operations-job-v1-batch-strong-","job-v1-batch","patch-scale-deployment-v1-apps","replace-scale-deployment-v1-apps","read-scale-deployment-v1-apps","-strong-misc-operations-deployment-v1-apps-strong-","replace-status-deployment-v1-apps","read-status-deployment-v1-apps","patch-status-deployment-v1-apps","-strong-status-operations-deployment-v1-apps-strong-","watch-list-all-namespaces-deployment-v1-apps","watch-list-deployment-v1-apps","watch-deployment-v1-apps","list-all-namespaces-deployment-v1-apps","list-deployment-v1-apps","read-deployment-v1-apps","-strong-read-operations-deployment-v1-apps-strong-","delete-collection-deployment-v1-apps","delete-deployment-v1-apps","replace-deployment-v1-apps","patch-deployment-v1-apps","create-deployment-v1-apps","-strong-write-operations-deployment-v1-apps-strong-","deployment-v1-apps","replace-status-daemonset-v1-apps","read-status-daemonset-v1-apps","patch-status-daemonset-v1-apps","-strong-status-operations-daemonset-v1-apps-strong-","watch-list-all-namespaces-daemonset-v1-apps","watch-list-daemonset-v1-apps","watch-daemonset-v1-apps","list-all-namespaces-daemonset-v1-apps","list-daemonset-v1-apps","read-daemonset-v1-apps","-strong-read-operations-daemonset-v1-apps-strong-","delete-collection-daemonset-v1-apps","delete-daemonset-v1-apps","replace-daemonset-v1-apps","patch-daemonset-v1-apps","create-daemonset-v1-apps","-strong-write-operations-daemonset-v1-apps-strong-","daemonset-v1-apps","replace-status-cronjob-v1-batch","read-status-cronjob-v1-batch","patch-status-cronjob-v1-batch","-strong-status-operations-cronjob-v1-batch-strong-","watch-list-all-namespaces-cronjob-v1-batch","watch-list-cronjob-v1-batch","watch-cronjob-v1-batch","list-all-namespaces-cronjob-v1-batch","list-cronjob-v1-batch","read-cronjob-v1-batch","-strong-read-operations-cronjob-v1-batch-strong-","delete-collection-cronjob-v1-batch","delete-cronjob-v1-batch","replace-cronjob-v1-batch","patch-cronjob-v1-batch","create-cronjob-v1-batch","-strong-write-operations-cronjob-v1-batch-strong-","cronjob-v1-batch","container-v1-core","-strong-workloads-apis-strong-","-strong-api-groups-strong-","-strong-api-overview-strong-"]};})();
\ No newline at end of file